I just installed PostgreSQL 10.4, and noticed that the pgAdmin 4 v3.0 interface packaged with that version uses a local web server and browser interface. By default, the application appears to use an ephemeral port (49152 to 65535) assigned by the OS (Windows 10 in my case). However, I'm working in an environment where the firewall is setup to block HTTP connections, which prevents connecting to the pgAdmin website. Is there a way to fix the port number, instead of using an OS-assigned ephemeral port?
I have looked through the pgAdmin 4 v3.0 documentation, but couldn't find anything about this type of configuration. As a work-around, I know that I can install pgAdmin 4 v2.1 using the stand-alone installer, but I hate the idea that we will never be able to upgrade if we use that approach.
BEGIN EDIT
The error I am getting in the web browser (IE11 on Windows Server 2016) is:
Unauthorized
The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to suply the credentials required.
When I searched for this issue, I found the following question on StackOverflow: pg4admin 401 Unauthorized Error
That question describes my problem exactly. However, none of those answers resolved my issue. The tray application appears to be successfully binding to the correct ports (netstat -a -n
appears to be correct), and there is nothing in the pgAdmin log file that looks suspicious. I will leave this question open, since fixing the port number seems like a reasonable thing to do, while I try to determine why pgAdmin isn't working.
http://127.0.0.1:port
. I know that a request to our IT department to open up ports on the system in question requires that we specify both a port number and protocol. Given that knowledge, and the fact it wasn't working, I made an educated guess that the firewall was to blame. Tomorrow, I'll add the text of the error message being displayed in the browser, and try to confirm what is going wrong by inspecting the log files.