Remote GPX files no longer loads

[pfbreton-perso]

Describe the bug This URL points to a GPX file it can no longer be loaded as a remote data layer:

https://ridebdr.com/download/8338/

To Reproduce Steps to reproduce the behavior:

1. Create a new layer
2. Under remote data, set the URL to " https://ridebdr.com/download/8338/"
3. Set the format to GPX
4. Enable Dynamic
5. Enable Proxy Request
6. Save the edits
7. Try to display the layer.

SEE: an error will occur

Here is a screenshot of the settings:

Expected behavior The GPX data should be dowloaded in the background and displayed on the map

Screenshots

Error:

Desktop (please complete the following information):

• OS: Windows 10
• Browser : Chrome
• Version: Version 116.0.5845.188

Additional context This was working correctly about 3 weeks ago (around sept 1st)

[davidbgk]

Which map is it?

[yohanboniface]

Works for me:

So we need more info to be able to investigate. Have you tried from another browser ? Have you tried downloading and importing the data ?

Also, as stated in the issue template, giving the map URL makes our developer lives much much easier…

Site note: you don't need to check "Dynamic" in this case, given the returned data will be the same whatever the map view. Using "Dynamic" only makes sense when the URL contains a parameter that takes the map bounds or center.

[pfbreton-perso]

Thanks for the fast reply!

Here is what I see from here:

Here is a test map that shows the issue I see here - its publicly editable:

https://umap.openstreetmap.fr/en/map/test-lab_712945#7/40.389/-76.383

[yohanboniface]

Thanks for the URL, it helps a lot.

Sounds like an SSL issue in the remote server that nginx cannot work around, while the browser can.

Here is a good summary: https://www.claudiokuenzler.com/blog/1120/nginx-reverse-proxy-ssl-alert-number-40-while-ssl-handshaking-upstream

Unfortunately, the fix suggested in this post does not work in our case. Sounds like a tricky one to fix.

[pfbreton-perso]

Thanks for the information! No big deal - i worked around it by uploading the gpx in a layer manually.

This is beyond my expertise - i don't know what changed recently so that it fails on my end, but not on yours. I will leave it up to you to decide to close this as won't fix or not.

[yohanboniface]

It's not just you :)

I'd like to fix it, but it's tricky!

[did1979]

Hy,

I have the same issue. Did you find how to fix it ? I have also a Nginx Proxy Manager behind my apache2 files server. a direct request on the https://server/file.csv works, but in the remote data I get the same server error. Thanks. Here is my map : https://umap.openstreetmap.fr/fr/map/actions-pic-et-pric-en-normandie_544448#8/49.203/0.483

Thanks.

[yohanboniface]

If you control the server behind the data, you can allow CORS request on it, and then no use the uMap proxy.