getting route error

irs_spryker
irs_spryker Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

I had created front page in yves to show data from tables. I had created client to connect yves call with zed to fetch the data but while calling i got route error

this is the url "http://yves.eu.spryker.local/training/antelope/Oskar"

and below is the error. I had done entry in yves/router/routerdependencyprovider but still got the route error.

image.png

Can anyone help me out please

Answers

  • Hidran Arias
    Hidran Arias Senior Technical Trainer Sprykee Posts: 95 πŸ› - Council (mod)

    The error is related to not accessing the gateway via https.
    Could you open yves with https protocol and give it a try again?
    Also: Verify you have executed docker/sdk console c:e, to clean the routerΒ΄s cache

  • irs_spryker
    irs_spryker Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    Thanks Hidran for the reply

    I had already executed the cache clean command . let me try by using secure connection in local.

  • irs_spryker
    irs_spryker Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    Hidran can you please let me know how to set the secure connection (https) in docker? I mean to say that spryker project is running in docker environment and i didnt see any vhost container. can you help me out for the same.

  • Hidran Arias
    Hidran Arias Senior Technical Trainer Sprykee Posts: 95 πŸ› - Council (mod)

    I usually open https://spryker.local and accept the certificate warning . After that, all urls open in https

    Another thing you have to control, as the https error sometimes is shown when you have a backend error, is that the Antelope Oskar exists in the Database but it should show a not found error.
    You can also add a breakpoint on the Antelope Client and debug to what the backend error is

  • irs_spryker
    irs_spryker Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    "I usually open https://spryker.local and accept the certificate warning . After that, all urls open in https"β€”β€”β€”β€”β€”ok, but this doesn't worked for me

    This sounds strange that sometimes for backend error also we get route error.

    Let me put breakpoint on the Antelope client and debug.