I have an issue that is preventing me from using Portal for development. When I click Sign In from a browser on a different machine than the Portal Server I get a Bad Gateway error. If I am connected through Remote Desktop I can login just fine. Is this by design or is something wrong?
Something is wrong.
What's the exact error message?
What URL are you trying to open?
Can you connect by bypassing the webadapter and going through the port?
More info on your setup will help. Is there a federated server, a data store, on different servers or the same one? etc...
Is this an HTTPS only setup?
When you connect locally (from RDC'd onto the server), is it going to local host or?
i.e. what's the URL that is connecting locally.
Depending on various things, it might be as simple as needing https at the front of your URL.
I removed my site from Azure and recreated it. What I've found is that the issue seems to revolve around the certificates being imported correctly into the portal admin page. The Cloud Builder did not successfully configure the https for the site. Have you used the cloud builder program?
Sorry Richard, I have not.
We're on a VMware sphere setup on our own blades, etc...
But I would think that you are on the right track. I am dealing with some similar issues related to upgrading 10.4 to 10.4.1 and it seems to be CA cert related. or intermixing signed certs with self-signed etc...
I don't if you've looked at the Chef cookbooks from Esri but they can really simplify and standardize the installation.
I am pretty sure they have a cookbook and a sample json install file for AWS setups.
Good luck !
Adding to Paul's questions,
Are the web server (hosting Web Adaptor), the Portal Server (hosting Portal for ArcGIS) and the client machine (where you are trying to access) in the same domain? If not, does the web server has public access (Try accessing the Web Server IIS using its hostname from the client machine)?