The message “No saved credentials found” comes when the map tries to find user-entered credentials saved from an earlier opening of the map. Is that how you have setup things, to have the user enter username and password for certain layers?
/Mathias
I just remembered that someone reported issues with the proxy in a cloud hosted environment. Then it turned out that they had set up the web server to be a little bit too restricted and the map could not access the proxy. The proxy lives under:
You can open the proxy in your web browser. If it turns out it cannot be accessed, then that might be the reason it does not work (on the other hand, I think there should have been another error message, but give it a try anyway).
Tried, and the proxy from the web browser gives this error:
{“error”: {“code”:400,”details”: dThis proxy does not support empty parameters. “], “message”: “400 - This proxy does not support empty parameters.”}}
Strange since it’s the same config as in the on premise server...
This is a stupid question but I must ask. Did you check the Use Proxy checkbox? It should be the same in the new environment as the old one, but perhaps someone changed it by mistake.
Hi again,
One last tip, since it looks like the proxy is at least running. You can test it "manually" in this way:
Concatenate the full URL to the proxy, add a question mark, and then the URL to the metadata for a layer. Here is an example (which does not work right now because our IT dept has a faulty configured firewall):
If you get to the metadata page for that feature layer using a URL like above, it means the username and password is working and that the proxy is setup correctly. It should look something like this:
If not, then it is not setup correctly Or it has not been updated as it should (you could try again by doing some dummy modification it in the settings screen).
For the future, if you want to know if the proxy is alive or not, you can "ping" it like this: