The place for all your openrouteservice enquiries. If you are having issues getting something to work or not sure how to get something out of the API, then here is a good place to start.
Before asking a question, please do a quick search to make sure that it hasn’t been asked and answered before by someone else.
Not sure what you mean. Matrix is still active of course.
Can you post your URL and request body? You don’t have to use the POST endpoint, you can still request the exact same way as before (with the old URL and POST body).
Sorry, I meant you can still use the old endpoint. Which offers GET and POST. Look for the small API version dropdown in the lower left and change to V1.
I am trying to save up time and RAM resources while running the engine for spain-latets.osm.pbf. I need only matrix and isochrones for foot-walk and driving-car profiles. In app.config I restrict routes to enabled: false .
I also restrict at the isochrones section the maximum_range_time and maxim_range_distance, by using only the profiles I need and removing the section:
{
“profiles”:“any”
}
And yet I see whenever I do docker-compose up that all the graphs for all the profiles are built. In this order: Vehicle-car, Vehicle-hgv, bike, pedestrian-walk
I checked the documentation for app.config and does not mention this issue. What is happening? How can I strip down the graphs so that I build only what I need? Thanks!
Both fail identically with the same headers and body.
What I’ve ruled out:
The root domain loads instantly and correctly (200 OK, full HTML landing page), so DNS, TLS, and basic connectivity to your infrastructure are working fine.
Verbose curl output (curl -v) shows the TCP/TLS handshake completing and the request being sent successfully; the failure happens only while waiting on the response from the routing backend.
Tested from curl directly (not just Postman) to rule out a client library issue.
Tested on two different networks to rule out a local firewall/proxy/VPN issue.
This suggests the issue is on the routing backend behind nginx, rather than my request, my key, or my network.
Could you please check whether there’s a known issue with the Directions service right now, and let me know if there’s anything on my side I should change? Happy to send full curl -v logs or a HAR file if useful.