This just started happening, but the convert location widget is causing CORS issues. This happening for anyone else?
Everything was fine this morning, but then all of a sudden...
Solved! Go to Solution.
I just got off the phone with Esri. This appears to be a bug. They are investigating now. Essentially, the convert widget is sending reverse geocoding requests with mouse movement, which is triggering DDOS protections which results in the errors. This behaviour is of course not intended.
EDIT: I will post any additional info the provide here. However, short-term fix was simply "remove convert widget". Also, please be aware that reverse geocoding is an expensive operation, and sending this may requests isn't advised (this may impact AGO users more).
That looks like the Network tab, if you go over to the console you probably have some messages there that have additional information that might help making sense of what exactly needs reconfigured.
(You might also click on a request and see its HTTP Request and HTTP Response for some additional visibility as well)
I just got off the phone with Esri. This appears to be a bug. They are investigating now. Essentially, the convert widget is sending reverse geocoding requests with mouse movement, which is triggering DDOS protections which results in the errors. This behaviour is of course not intended.
EDIT: I will post any additional info the provide here. However, short-term fix was simply "remove convert widget". Also, please be aware that reverse geocoding is an expensive operation, and sending this may requests isn't advised (this may impact AGO users more).