How to Fix the pgAdmin 4 v3.0+ Port Number
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.
postgresql pgadmin
add a comment |
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.
postgresql pgadmin
Does your firewall actually block connections to localhost? That is rather unusual.
– grawity
May 12 '18 at 13:36
I haven't confirmed that the firewall is blocking the connection. All I know is that the pgAdmin web interface isn't working due to an inability to connect tohttp://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.
– Jeff G
May 13 '18 at 15:25
add a comment |
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.
postgresql pgadmin
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.
postgresql pgadmin
postgresql pgadmin
edited May 14 '18 at 16:52
Jeff G
asked May 12 '18 at 12:58
Jeff GJeff G
178211
178211
Does your firewall actually block connections to localhost? That is rather unusual.
– grawity
May 12 '18 at 13:36
I haven't confirmed that the firewall is blocking the connection. All I know is that the pgAdmin web interface isn't working due to an inability to connect tohttp://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.
– Jeff G
May 13 '18 at 15:25
add a comment |
Does your firewall actually block connections to localhost? That is rather unusual.
– grawity
May 12 '18 at 13:36
I haven't confirmed that the firewall is blocking the connection. All I know is that the pgAdmin web interface isn't working due to an inability to connect tohttp://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.
– Jeff G
May 13 '18 at 15:25
Does your firewall actually block connections to localhost? That is rather unusual.
– grawity
May 12 '18 at 13:36
Does your firewall actually block connections to localhost? That is rather unusual.
– grawity
May 12 '18 at 13:36
I haven't confirmed that the firewall is blocking the connection. All I know is that the pgAdmin web interface isn't working due to an inability to connect to
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.– Jeff G
May 13 '18 at 15:25
I haven't confirmed that the firewall is blocking the connection. All I know is that the pgAdmin web interface isn't working due to an inability to connect to
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.– Jeff G
May 13 '18 at 15:25
add a comment |
6 Answers
6
active
oldest
votes
Ran into this problem on Windows Server 2016 with pgAdmin4 v3.5 - resolved it by setting "IE Enhanced Security Configuration" to OFF - can then immediately access the management pages (note - 'run as Administrator' was not required).
add a comment |
I found that you can't just open that address in a browser (at least not for the first time).
You have to open it from the pgAdmin tray icon -> New pgAdmin4 window...
.
If it's not there and you have problem with running pgAdmin4 at all then try to find psql.exe
inside the installation directory:
C:Program Files (x86)pgAdmin 4v3runtime
and run psql.exe
before running pgAdmin4.exe
.
If that still doesn't help, try to set different default browser in your system.
add a comment |
The Unauthorized
message indicates a successful HTTP connection as it is read from the HTTP server. It appears when you don’t have the right authorization cookie.
When pgAdmin 4 is run in desktop mode, you have to right-click on its tray icon and select New pgAdmin 4 window. Make sure you have cookies enabled. If you use a whitelist, you have to set a permission for the used port which changes every time pgAdmin starts.
Update: pgAdmin 4 3.2 is released. You can now copy the URL including the key for using any browser (profile) you like which has the required cookie permissions. You can also set a fixed port number so you can create a cookie permission exception rule in your default browser (profile).
Unfortunately, enabling cookies and addinghttp://127.0.0.1
to the "Trusted sites" list didn't work for me.
– Jeff G
Jul 18 '18 at 22:31
@JeffG Addinghttp://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example forhttp://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.
– Martin
Jul 19 '18 at 8:09
add a comment |
I had the same issue and solved it by installing a different browser.
In my case it was "Google Chrome" and set them as "default".
Steps:
- stop pgadmin4
- install Google Chrome
- set Google Chrome to default
- start pgadmin4
add a comment |
Had the same issue in the following setup:
Kubuntu 18, Firefox 64.0
What worked for me:
Context menu > Copy server URL. That will give us an url of form:
http://127.0.0.1:1234/?key=18ef03ff-d16a-43bc-af30-b20c66fbf452
Navigate to that URL via browser (in my case Firefox worked well)
The following did not help:
Context menu > New pgAdmin 4 window...
Uninstall & install pgAdmin 4
Clear cookies for 127.0.0.1
Restart pgAdmin4
Hope this helps someone.
add a comment |
delete the cookies from the browser settings, if you are going to reinstall pgadmin.
example: Firefox --> Options --> Privacy & Security --> Cookies and Site data --Clear Data
Find 127.0.0.1 and clean or find localhost and clean
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1322086%2fhow-to-fix-the-pgadmin-4-v3-0-port-number%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ran into this problem on Windows Server 2016 with pgAdmin4 v3.5 - resolved it by setting "IE Enhanced Security Configuration" to OFF - can then immediately access the management pages (note - 'run as Administrator' was not required).
add a comment |
Ran into this problem on Windows Server 2016 with pgAdmin4 v3.5 - resolved it by setting "IE Enhanced Security Configuration" to OFF - can then immediately access the management pages (note - 'run as Administrator' was not required).
add a comment |
Ran into this problem on Windows Server 2016 with pgAdmin4 v3.5 - resolved it by setting "IE Enhanced Security Configuration" to OFF - can then immediately access the management pages (note - 'run as Administrator' was not required).
Ran into this problem on Windows Server 2016 with pgAdmin4 v3.5 - resolved it by setting "IE Enhanced Security Configuration" to OFF - can then immediately access the management pages (note - 'run as Administrator' was not required).
edited Nov 13 '18 at 19:39
GabrielaGarcia
692415
692415
answered Nov 13 '18 at 16:33
Alex PietruszkaAlex Pietruszka
462
462
add a comment |
add a comment |
I found that you can't just open that address in a browser (at least not for the first time).
You have to open it from the pgAdmin tray icon -> New pgAdmin4 window...
.
If it's not there and you have problem with running pgAdmin4 at all then try to find psql.exe
inside the installation directory:
C:Program Files (x86)pgAdmin 4v3runtime
and run psql.exe
before running pgAdmin4.exe
.
If that still doesn't help, try to set different default browser in your system.
add a comment |
I found that you can't just open that address in a browser (at least not for the first time).
You have to open it from the pgAdmin tray icon -> New pgAdmin4 window...
.
If it's not there and you have problem with running pgAdmin4 at all then try to find psql.exe
inside the installation directory:
C:Program Files (x86)pgAdmin 4v3runtime
and run psql.exe
before running pgAdmin4.exe
.
If that still doesn't help, try to set different default browser in your system.
add a comment |
I found that you can't just open that address in a browser (at least not for the first time).
You have to open it from the pgAdmin tray icon -> New pgAdmin4 window...
.
If it's not there and you have problem with running pgAdmin4 at all then try to find psql.exe
inside the installation directory:
C:Program Files (x86)pgAdmin 4v3runtime
and run psql.exe
before running pgAdmin4.exe
.
If that still doesn't help, try to set different default browser in your system.
I found that you can't just open that address in a browser (at least not for the first time).
You have to open it from the pgAdmin tray icon -> New pgAdmin4 window...
.
If it's not there and you have problem with running pgAdmin4 at all then try to find psql.exe
inside the installation directory:
C:Program Files (x86)pgAdmin 4v3runtime
and run psql.exe
before running pgAdmin4.exe
.
If that still doesn't help, try to set different default browser in your system.
edited Jun 7 '18 at 10:18
answered Jun 7 '18 at 10:05
WiktorWiktor
11
11
add a comment |
add a comment |
The Unauthorized
message indicates a successful HTTP connection as it is read from the HTTP server. It appears when you don’t have the right authorization cookie.
When pgAdmin 4 is run in desktop mode, you have to right-click on its tray icon and select New pgAdmin 4 window. Make sure you have cookies enabled. If you use a whitelist, you have to set a permission for the used port which changes every time pgAdmin starts.
Update: pgAdmin 4 3.2 is released. You can now copy the URL including the key for using any browser (profile) you like which has the required cookie permissions. You can also set a fixed port number so you can create a cookie permission exception rule in your default browser (profile).
Unfortunately, enabling cookies and addinghttp://127.0.0.1
to the "Trusted sites" list didn't work for me.
– Jeff G
Jul 18 '18 at 22:31
@JeffG Addinghttp://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example forhttp://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.
– Martin
Jul 19 '18 at 8:09
add a comment |
The Unauthorized
message indicates a successful HTTP connection as it is read from the HTTP server. It appears when you don’t have the right authorization cookie.
When pgAdmin 4 is run in desktop mode, you have to right-click on its tray icon and select New pgAdmin 4 window. Make sure you have cookies enabled. If you use a whitelist, you have to set a permission for the used port which changes every time pgAdmin starts.
Update: pgAdmin 4 3.2 is released. You can now copy the URL including the key for using any browser (profile) you like which has the required cookie permissions. You can also set a fixed port number so you can create a cookie permission exception rule in your default browser (profile).
Unfortunately, enabling cookies and addinghttp://127.0.0.1
to the "Trusted sites" list didn't work for me.
– Jeff G
Jul 18 '18 at 22:31
@JeffG Addinghttp://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example forhttp://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.
– Martin
Jul 19 '18 at 8:09
add a comment |
The Unauthorized
message indicates a successful HTTP connection as it is read from the HTTP server. It appears when you don’t have the right authorization cookie.
When pgAdmin 4 is run in desktop mode, you have to right-click on its tray icon and select New pgAdmin 4 window. Make sure you have cookies enabled. If you use a whitelist, you have to set a permission for the used port which changes every time pgAdmin starts.
Update: pgAdmin 4 3.2 is released. You can now copy the URL including the key for using any browser (profile) you like which has the required cookie permissions. You can also set a fixed port number so you can create a cookie permission exception rule in your default browser (profile).
The Unauthorized
message indicates a successful HTTP connection as it is read from the HTTP server. It appears when you don’t have the right authorization cookie.
When pgAdmin 4 is run in desktop mode, you have to right-click on its tray icon and select New pgAdmin 4 window. Make sure you have cookies enabled. If you use a whitelist, you have to set a permission for the used port which changes every time pgAdmin starts.
Update: pgAdmin 4 3.2 is released. You can now copy the URL including the key for using any browser (profile) you like which has the required cookie permissions. You can also set a fixed port number so you can create a cookie permission exception rule in your default browser (profile).
edited Aug 23 '18 at 11:27
answered Jul 17 '18 at 12:43
MartinMartin
1236
1236
Unfortunately, enabling cookies and addinghttp://127.0.0.1
to the "Trusted sites" list didn't work for me.
– Jeff G
Jul 18 '18 at 22:31
@JeffG Addinghttp://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example forhttp://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.
– Martin
Jul 19 '18 at 8:09
add a comment |
Unfortunately, enabling cookies and addinghttp://127.0.0.1
to the "Trusted sites" list didn't work for me.
– Jeff G
Jul 18 '18 at 22:31
@JeffG Addinghttp://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example forhttp://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.
– Martin
Jul 19 '18 at 8:09
Unfortunately, enabling cookies and adding
http://127.0.0.1
to the "Trusted sites" list didn't work for me.– Jeff G
Jul 18 '18 at 22:31
Unfortunately, enabling cookies and adding
http://127.0.0.1
to the "Trusted sites" list didn't work for me.– Jeff G
Jul 18 '18 at 22:31
@JeffG Adding
http://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example for http://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.– Martin
Jul 19 '18 at 8:09
@JeffG Adding
http://127.0.0.1
only creates an exception for port 80 (the default port for HTTP). You have to select New pgAdmin 4 window, check which port it actually uses (in the private/dynamic range 49152–65535), create a matching exception (for example for http://127.0.0.1:53529
), then select New pgAdmin 4 window again (because this opens a URL which tries to set an authentication cookie and then redirects to another URL which doesn’t, so reloading the latter doesn’t help). When you start pgAdmin the next time, you have to repeat this because it very likely uses a different port.– Martin
Jul 19 '18 at 8:09
add a comment |
I had the same issue and solved it by installing a different browser.
In my case it was "Google Chrome" and set them as "default".
Steps:
- stop pgadmin4
- install Google Chrome
- set Google Chrome to default
- start pgadmin4
add a comment |
I had the same issue and solved it by installing a different browser.
In my case it was "Google Chrome" and set them as "default".
Steps:
- stop pgadmin4
- install Google Chrome
- set Google Chrome to default
- start pgadmin4
add a comment |
I had the same issue and solved it by installing a different browser.
In my case it was "Google Chrome" and set them as "default".
Steps:
- stop pgadmin4
- install Google Chrome
- set Google Chrome to default
- start pgadmin4
I had the same issue and solved it by installing a different browser.
In my case it was "Google Chrome" and set them as "default".
Steps:
- stop pgadmin4
- install Google Chrome
- set Google Chrome to default
- start pgadmin4
edited Oct 7 '18 at 11:25
Scott
15.7k113990
15.7k113990
answered Oct 7 '18 at 11:04
Jan W.Jan W.
1
1
add a comment |
add a comment |
Had the same issue in the following setup:
Kubuntu 18, Firefox 64.0
What worked for me:
Context menu > Copy server URL. That will give us an url of form:
http://127.0.0.1:1234/?key=18ef03ff-d16a-43bc-af30-b20c66fbf452
Navigate to that URL via browser (in my case Firefox worked well)
The following did not help:
Context menu > New pgAdmin 4 window...
Uninstall & install pgAdmin 4
Clear cookies for 127.0.0.1
Restart pgAdmin4
Hope this helps someone.
add a comment |
Had the same issue in the following setup:
Kubuntu 18, Firefox 64.0
What worked for me:
Context menu > Copy server URL. That will give us an url of form:
http://127.0.0.1:1234/?key=18ef03ff-d16a-43bc-af30-b20c66fbf452
Navigate to that URL via browser (in my case Firefox worked well)
The following did not help:
Context menu > New pgAdmin 4 window...
Uninstall & install pgAdmin 4
Clear cookies for 127.0.0.1
Restart pgAdmin4
Hope this helps someone.
add a comment |
Had the same issue in the following setup:
Kubuntu 18, Firefox 64.0
What worked for me:
Context menu > Copy server URL. That will give us an url of form:
http://127.0.0.1:1234/?key=18ef03ff-d16a-43bc-af30-b20c66fbf452
Navigate to that URL via browser (in my case Firefox worked well)
The following did not help:
Context menu > New pgAdmin 4 window...
Uninstall & install pgAdmin 4
Clear cookies for 127.0.0.1
Restart pgAdmin4
Hope this helps someone.
Had the same issue in the following setup:
Kubuntu 18, Firefox 64.0
What worked for me:
Context menu > Copy server URL. That will give us an url of form:
http://127.0.0.1:1234/?key=18ef03ff-d16a-43bc-af30-b20c66fbf452
Navigate to that URL via browser (in my case Firefox worked well)
The following did not help:
Context menu > New pgAdmin 4 window...
Uninstall & install pgAdmin 4
Clear cookies for 127.0.0.1
Restart pgAdmin4
Hope this helps someone.
answered Jan 7 at 9:40
Siroj MatchanovSiroj Matchanov
1
1
add a comment |
add a comment |
delete the cookies from the browser settings, if you are going to reinstall pgadmin.
example: Firefox --> Options --> Privacy & Security --> Cookies and Site data --Clear Data
Find 127.0.0.1 and clean or find localhost and clean
add a comment |
delete the cookies from the browser settings, if you are going to reinstall pgadmin.
example: Firefox --> Options --> Privacy & Security --> Cookies and Site data --Clear Data
Find 127.0.0.1 and clean or find localhost and clean
add a comment |
delete the cookies from the browser settings, if you are going to reinstall pgadmin.
example: Firefox --> Options --> Privacy & Security --> Cookies and Site data --Clear Data
Find 127.0.0.1 and clean or find localhost and clean
delete the cookies from the browser settings, if you are going to reinstall pgadmin.
example: Firefox --> Options --> Privacy & Security --> Cookies and Site data --Clear Data
Find 127.0.0.1 and clean or find localhost and clean
answered Jan 3 at 15:36
Levent AksunLevent Aksun
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1322086%2fhow-to-fix-the-pgadmin-4-v3-0-port-number%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does your firewall actually block connections to localhost? That is rather unusual.
– grawity
May 12 '18 at 13:36
I haven't confirmed that the firewall is blocking the connection. All I know is that the pgAdmin web interface isn't working due to an inability to connect to
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.– Jeff G
May 13 '18 at 15:25