New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Routing error - HTTP request failed: [object ProgressEvent] #280
Comments
After some research I found that the problem is not from LRM but from the OSRM's demo server that comes without guarantees , and not advised for production use ... Apparently it's not the first time that happens , I spent a lot of time setting the leaflet routing map in the project and I can't deliver a work to my client that can be broken at any time , unfortunately I have to simply switch to Google map API . |
+1 Is there any update about this ? Even here, the route doesn't work. |
@LailaMai There are cheap alternatives for using OSRM or other backends compatible with LRM, but not entirely free. On the other hand, Google Maps isn't free if your solution uses a login or is a paid service, and depending on how you see it not really free otherwise either - your users are paying by delivering data to Google. Bottom line: if you want something to work, it will have to be paid, one way or another. |
@perliedman Actually I made my solution with GoogleMap Api and yeah it's not free , especially that Google has restriction on 10 waypoints per route , if you want more you have to pay for premium account . |
Hi @Zacaria , how did you know it was a CORS issue? I'm currently experiencing this with an ASP.NET Web API app and I have been unable to figure out why I'm getting the issue. |
Hello guys,
Since two days ago , the map doesn't show correctly and there is an error shown in console : Routing error: Object { status=-1, message="HTTP request failed: [object ProgressEvent]"} , when I check the website http://www.liedman.net/leaflet-routing-machine , I saw the same thing, so it's certainly from the API server , is there any solution for that ?
The text was updated successfully, but these errors were encountered: