Route not provided when start and end address provided

Question

Route not provided when start and end address provided

ubalaji opened this issue 5 years ago · comments

I have installed latest dcoker images of both osrm-frontend and osrm-backend on Linux. When I type start address the location is showing. After typing end address the route is not showing. The is recognized when I type end address but route is not showing.

My docker port for frontend is 8080 and backend port is 80.

Also I have modified leaflet_options.js file to AS follows.

services: [{
label: 'Car (fastest)',
path: 'http://localhost:80/route/v1'
}],

Also I have env variable "OSRM_BACKEND=http://localhost:80"
When I use http://map.project-osrm.org url, use same start and end address would provide route.

I am not sure why I am not able to see route on local. Would any of you experienced similar issue and how did you resolve?

ukadmin · Answer 1 · Wed Nov 20 2019 06:00:50 GMT+0800 (China Standard Time)

Same issue here.. you could solve it?

boris-vanderbeken · Answer 2 · Sun Feb 02 2020 08:34:44 GMT+0800 (China Standard Time)

Hi,
I had similar issue and solved it by setting right env variables in the command when launchinf the container.
Problem was network Connectivity. The container could'nt connect to localhost or to 127.0.0.1. I had to specify IP of the docker server hosting the container. Here are the variables passed in the command :
docker run -p 9966:9966 -e OSRM_BACKEND='http://192.168.100.122:5000' -e OSRM_CENTER='48.859903,2.338919' -e OSRM_ZOOM='13' -e OSRM_LANGUAGE='fr' -e OSRM_LABEL='Car (fastest)' osrm/osrm-frontend

Hope it helps

kaislar · Answer 3 · Thu Feb 13 2020 06:58:56 GMT+0800 (China Standard Time)

Hello

I have the same issue here, both backend and front end are running in containers. I run the following command docker run -p 9966:9966 -e OSRM_BACKEND='http://172.0.0.2:5000' -e OSRM_CENTER='48.859903,2.338919' -e OSRM_ZOOM='13' -e OSRM_LANGUAGE='fr' -e OSRM_LABEL='Car (fastest)' osrm/osrm-frontend

http://172.0.0.2:5000 : Is the container ip running the backend
But still no routes generated in the Front.

I checked to src/leaflet_options.js and noticed that it got the ENV variable 172.0.0.2:5000
Also tried to curl 172.0.0.2:5000 from the container hosting the Front and it seems to respond.

Do you have any idea what could be the problem with the front and back?

Artem Tokarev · Answer 4 · Sat May 09 2020 02:31:42 GMT+0800 (China Standard Time)

Same issue, running on docker containers

kaislar · Answer 5 · Sat May 09 2020 02:44:03 GMT+0800 (China Standard Time)

I managed to get it working using the public ip instead of the container ip

Artem Tokarev · Answer 6 · Sat May 09 2020 02:52:17 GMT+0800 (China Standard Time)

Didn't help me, but I'm able to connect to the backend with curl :(

kaislar · Answer 7 · Sat May 09 2020 03:07:45 GMT+0800 (China Standard Time)

Try to use the server public ip when in backend export argument and then query it from the front container or the host machine. Le ven. 8 mai 2020 à 20:52, Artem Tokarev <notifications@github.com> a écrit :

…

Didn't help me, but I'm able to connect to the backend with curl :( — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#312 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACW6NBNB7AVCCYT253CJR63RQRIG5ANCNFSM4IW5QXIQ> .

Artem Tokarev · Answer 8 · Sat May 09 2020 03:15:45 GMT+0800 (China Standard Time)

docker run -p 9966:9966 -e OSRM_BACKEND='http://<MYPUBLIC_IP>:5000' -e OSRM_ZOOM='13' -e OSRM_LABEL='Car (fastest)' osrm/osrm-frontend

tried this way, is it was you meant?

Rowdy Beaver · Answer 9 · Tue Sep 08 2020 06:50:48 GMT+0800 (China Standard Time)

Since it is the user's browser making the call to the backend, the public IP (or localhost) needs to be used. The front-end does not call the back-end directly.

Hope this explains the trouble and why the solution is to use an IP address the browser can hit. I spent several hours on this, before I found this issue. It seems important to document the reason why this works, so others can benefit from our experience.