Problem in the response when enter in a map

[Pierreiozzo]

trafficstars

Hello,

I created a map recently but now, when I enter it, a red banner appears with the message "Problem in the response". No more data appears on the map now. How can I get through it ? Is there any solution to retrieve the data? The map link : http://u.osmfr.org/m/750000/

Thanks a lot,

Pierre

[Filou70]

Hi Pierre, I have the same problem. did you resolve the issue ? thanks Philippe

[Pierreiozzo]

Hello, I didn't... I just recreate a new map. But now I make a local save every weeks to be sure to not loose any data.

Regards

Le mer. 20 juil. 2022 à 14:22, Filou70 @.***> a écrit :

Hi Pierre, I have the same problem. did you resolve the issue ? thanks Philippe

— Reply to this email directly, view it on GitHub https://github.com/umap-project/umap/issues/1010#issuecomment-1190219203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZX27BDVH3KE43EWFMY5VBDVU7VPXANCNFSM5ZPB2Y3A . You are receiving this because you authored the thread.Message ID: @.***>

[philstephenrichards]

This seems to be the case when your map is too large. The first time I experienced this the map was just under 500MB (file size after downloading it). However I have got the same issue with one just under 100MB.

So I am not sure what the limit is as obviously with the first map it was allowed to grow in stages up to 500MB.

Hello

I created a map recently but now, when I enter it, a red banner appears with the message "Problem in the response". No more data appears on the map now. How can I get through it ? Is there any solution to retrieve the data? The map link : http://u.osmfr.org/m/750000/

Thanks a lot,

Pierre

[tanquist]

I have a map which I updated successfully this morning. I changed the color and description of three polygons. I just tried to make another change to the description and got the red "Problem in the response" message. I do not understand why this is happening. I have maintained this map without issue for several years. link: https://umap.openstreetmap.fr/en/map/minnesota-restricted-routes_571411

[tech62]

Same thing for me, with this error in the console log from browser. Umap is setup with Nginx and uwsgi following this documentation : https://github.com/umap-project/umap/blob/master/docs/ubuntu.md

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Deprecated include of L.Mixin.Events: this property will be removed in future releases, please inherit from L.Evented instead. checkDeprecatedMixinEvents@http://carto.myserver/static/CACHE/js/output.d63600704f39.js:35:264 Class.extend@http://carto.myserver/static/CACHE/js/output.d63600704f39.js:30:46

I obtain an xhr response ‹IâHdÿ1_1682498121994.geojson5Ì; …0Fá­\þ:mZáV‚‘QGÆLÌqï*bû8Ò—*ÂCšÕÁz-Â6­A—òú'Þtœ£ÚkW)°)d6èƒn‘zá-Ï¿$Y3ÿ œçºr ît

[tech62]

Problem disappeared when removingUMAP_XSENDFILE_HEADER = 'X-Accel-Redirect' from /etc/umap/umap.conf. Any idea how to get this working ?

[davidbgk]

I'll close that one as a solution has been provided in #1070

[Filou70]

thank you so much!

sorry for the question but I am not a geek... Where precisely do I need to remove what you mentioned in your message?

Thanks

Philippe

Le mer. 26 avr. 2023 à 14:05, tech62 @.***> a écrit :

Problem disappear when remove UMAP_XSENDFILE_HEADER = 'X-Accel-Redirect' from /etc/umap/umap.conf

— Reply to this email directly, view it on GitHub https://github.com/umap-project/umap/issues/1010#issuecomment-1523304268, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2EW4BVPFILD2CI74F3BTN3XDEFQDANCNFSM5ZPB2Y3A . You are receiving this because you commented.Message ID: @.***>

[tech62]

If you add this line when following the installation docs, you can remove it in the Umap configuration file : /etc/umap/umap.conf

[yohanboniface]

I think there is a confusion here: the initial bug report was not on a custom uMap install, AFAIK. So I think it's unrelated to the XSENDFILE thing.

@Filou70 do you still have the issue, and if yes can you provide the link to the map ?

It can be either a map "too big", or that the server was under load at this very moment.

[tech62]

Sorry for the confusion, but with the XSENDFILE directive in umap configuration, i'm encountered the same error message on a fresh map / fresh install :/