Hey all,
I've actually a feature layer hosted in our production organisation portal. The ArcGIS Server is federated with the portal. I'm trying to active the update option to allow the users to add, modifiying and delete the features but getting the following message error :
Unable to load https://portal_machine/portal/sharing/proxy?https://server_machine:6443/arcgis/rest/admin/services/H... status: 400
I've checked the portal logs and found this related to the error :
Server urls variations [portal_machine:443/server, portal_machine:80/server] were tested but not found to be matching incoming URL 'https://server_machine:6443/arcgis/rest/admin/services/Hosted/MyFeatureLayer/FeatureServer'. |
NB 1: I did this operation in our developpement environnement and it works fine
NB 2 : Our production environnement is publiclly accessible via internet but not the developpement environnement
Any help is very appreciated
Thanks all
Solved! Go to Solution.
My best guess at this point would be that there is a whitelist established on your portal proxy sharing rules:
I would also guess that the internal name of the server machine isn't listed there? Adding the server name to the existing list (no need for the :6443) will remedy the situation.
My best guess at this point would be that there is a whitelist established on your portal proxy sharing rules:
I would also guess that the internal name of the server machine isn't listed there? Adding the server name to the existing list (no need for the :6443) will remedy the situation.
Hello @Scott_Tansley
Im a colleague of @GISiste . I added the internal name of the server to the portal proxy sharing rules like this:
"allowedProxyHosts": "gisserver1.domain.com"
I even used a wildcard "allowedProxyHosts": "(.*).domain.com".
But still having the same issue.
My bad. It's resolved. I had cache on my brower.
Thanks @Scott_Tansley for the intel.
Great news. Don’t use the wildcard though. It opens up too many lines of attack. Needs to be individually specified machines.
Thanks @Scott_Tansley for your appreciated answers and advices. It works now fine