*Server overload - *free service worth every penny. Top candidate IMNSHO.
*Backend service crash - *less likely *Timeout fetching map data* Large maps & we have some - but not the ones causing the 502 which is random anyway.
*Reverse proxy issues (Nginx) -* ?
*Maintenance or updates -* rare
*External data source failure - *If map loads remote layers (not applicable in our case)
I posted on an old thread and was told to ask here. And they posited Nominatim. An NIH answer if I ever saw. But what is the mechanism that Nominatim causes 502? And how frequent.
The reference to Nominatim isn’t clear. Are you seeing some kind of error message reported from Nominatim? Or is this purely a UMap issue?
Perhaps you could give more detail on what is happening. Which UMap server are you using? Does this happen during editing, when saving, when viewing etc? Does the map include “live” queries of OSM data, or is it static data using an OSM-based map as a background?
Maybe you already posted this but if there is some prior history, it’s not easily findable for someone reading this. (Also, what is an NIH answer?)
502 Bad Gateway is the only symptom. AI is pretty clear that it is not a browser problem. I assume it found other reports on this. Broadband speeds don’t seem to be a factor.
I generate a targeted URL in a hyperlink eg (spaces to reveal the map & hash)
“- uMap - Online map creator ms-soc-ireland_1437718#14/53.939920/-6.921390”
Nominatim was suggested on another thread. But as that seems to be about searching data, I don’t see the relevance anyway. Other than that no clues during usage and no info to follow up on. Just asking to see if wiser users know anything.