Re: Problem getting https working
Hi Yogesh, Thanks for your reply - I've been busy with other things, but did try disabling all browser extensions and still got the same error message. Then I started double checking things and found the permissions on the SSL cert were incorrect. I fixed that up and now it's all working perfectly :-) Cheers, Ian On Sat, 10 Oct 2020 at 00:24, Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hi, > > I could not reproduce the issue reported but I am not using apache to host. > However PR_CONNECT_RESET_ERROR is caused due to some browser extensions.( > Reference <https://support.mozilla.org/en-US/questions/1280856>) > Could you please try launching a server in private window and share a > screenshot & browser name if error still persists? > > Thanks, > Yogesh Mahajan > EnterpriseDB Corporation > > Phone: +91-9741705709 > > > On Thu, Oct 8, 2020 at 6:34 PM Ian Moore > wrote: > >> HI, >> I've been trying to get pgAdmin 4 4.26 working with https and not having >> any success. If I don't use https, it all works perfectly. >> >> I've followed the instructions at >> https://www.pgadmin.org/docs/pgadmin4/development/container_deployment.html# >> and also found some info on this list in the thread >> https://www.postgresql.org/message-id/1b4bba2d-910d-3017-bc5d-6b45dcac31d0%40empirica-systeme.de >> >> I've used this config, which the same as that given in the above thread >> as a known working config: >> docker run -p 554:443 -v >> '/etc/apache2/ssl.crt/server.crt:/certs/server.cert' -v >> '/etc/apache2/ssl.key/server.key:/certs/server.key' -e >> 'PGADMIN_DEFAULT_EMAIL=pgad...@server.com' -e >> 'PGADMIN_DEFAULT_PASSWORD=mysecurepassword' -e 'PGADMIN_ENABLE_TLS=True' -e >> 'PGADMIN_SERVER_NAME=myserver.com' -d dpage/pgadmin4 >> >> The ssl cert & key are used on the host server to host run a website with >> apache on ports 80 & 443 (hence the docker port 443 is re-directed to 554), >> so they are valid and I've confirmed that the docker is picking them up >> correctly by copying them from the running docker back to the host machine >> & comparing them with the originals and they are exactly the same. >> >> The output of docker ps is: >> CONTAINER IDIMAGE COMMAND CREATED >> STATUS PORTS NAMES >> c2c4cc713c3adpage/pgadmin4 "/entrypoint.sh"17 minutes >> ago Up 17 minutes 80/tcp, 0.0.0.0:554->443/tcp >> youthful_ptolemy >> >> When I try to access pgAdmin in my browser using https://myserver.com:554 >> or https://myserverip:554 or https://127.0.0.1:554, I get this response: >> Secure Connection Failed >> >> An error occurred during a connection to intranet.threedradio.com:8443. >> PR_CONNECT_RESET_ERROR >> >> If I telnet to the server on port 554, it connects briefly and then >> closes the connection, so it's definitely listening on the correct port. >> >> I also tried redirecting port 80 to another port in case that was causing >> a conflict with apache, but that didn't seem to help at all. >> >> Hoping someone can help! >> >> Cheers, >> Ian >> >
Re: Problem getting https working
Hi Yogesh, Thanks for your reply, been a bit busy with other things but I tried *Ian Moore* *Technician* *Three D Radio 93.7fm* *m 0401 121 167* *e ian.mo...@threedradio.com * On Sat, 10 Oct 2020 at 00:24, Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hi, > > I could not reproduce the issue reported but I am not using apache to host. > However PR_CONNECT_RESET_ERROR is caused due to some browser extensions.( > Reference <https://support.mozilla.org/en-US/questions/1280856>) > Could you please try launching a server in private window and share a > screenshot & browser name if error still persists? > > Thanks, > Yogesh Mahajan > EnterpriseDB Corporation > > Phone: +91-9741705709 > > > On Thu, Oct 8, 2020 at 6:34 PM Ian Moore > wrote: > >> HI, >> I've been trying to get pgAdmin 4 4.26 working with https and not having >> any success. If I don't use https, it all works perfectly. >> >> I've followed the instructions at >> https://www.pgadmin.org/docs/pgadmin4/development/container_deployment.html# >> and also found some info on this list in the thread >> https://www.postgresql.org/message-id/1b4bba2d-910d-3017-bc5d-6b45dcac31d0%40empirica-systeme.de >> >> I've used this config, which the same as that given in the above thread >> as a known working config: >> docker run -p 554:443 -v >> '/etc/apache2/ssl.crt/server.crt:/certs/server.cert' -v >> '/etc/apache2/ssl.key/server.key:/certs/server.key' -e >> 'PGADMIN_DEFAULT_EMAIL=pgad...@server.com' -e >> 'PGADMIN_DEFAULT_PASSWORD=mysecurepassword' -e 'PGADMIN_ENABLE_TLS=True' -e >> 'PGADMIN_SERVER_NAME=myserver.com' -d dpage/pgadmin4 >> >> The ssl cert & key are used on the host server to host run a website with >> apache on ports 80 & 443 (hence the docker port 443 is re-directed to 554), >> so they are valid and I've confirmed that the docker is picking them up >> correctly by copying them from the running docker back to the host machine >> & comparing them with the originals and they are exactly the same. >> >> The output of docker ps is: >> CONTAINER IDIMAGE COMMAND CREATED >> STATUS PORTS NAMES >> c2c4cc713c3adpage/pgadmin4 "/entrypoint.sh"17 minutes >> ago Up 17 minutes 80/tcp, 0.0.0.0:554->443/tcp >> youthful_ptolemy >> >> When I try to access pgAdmin in my browser using https://myserver.com:554 >> or https://myserverip:554 or https://127.0.0.1:554, I get this response: >> Secure Connection Failed >> >> An error occurred during a connection to intranet.threedradio.com:8443. >> PR_CONNECT_RESET_ERROR >> >> If I telnet to the server on port 554, it connects briefly and then >> closes the connection, so it's definitely listening on the correct port. >> >> I also tried redirecting port 80 to another port in case that was causing >> a conflict with apache, but that didn't seem to help at all. >> >> Hoping someone can help! >> >> Cheers, >> Ian >> >
Problem getting https working
HI, I've been trying to get pgAdmin 4 4.26 working with https and not having any success. If I don't use https, it all works perfectly. I've followed the instructions at https://www.pgadmin.org/docs/pgadmin4/development/container_deployment.html# and also found some info on this list in the thread https://www.postgresql.org/message-id/1b4bba2d-910d-3017-bc5d-6b45dcac31d0%40empirica-systeme.de I've used this config, which the same as that given in the above thread as a known working config: docker run -p 554:443 -v '/etc/apache2/ssl.crt/server.crt:/certs/server.cert' -v '/etc/apache2/ssl.key/server.key:/certs/server.key' -e 'PGADMIN_DEFAULT_EMAIL=pgad...@server.com' -e 'PGADMIN_DEFAULT_PASSWORD=mysecurepassword' -e 'PGADMIN_ENABLE_TLS=True' -e 'PGADMIN_SERVER_NAME=myserver.com' -d dpage/pgadmin4 The ssl cert & key are used on the host server to host run a website with apache on ports 80 & 443 (hence the docker port 443 is re-directed to 554), so they are valid and I've confirmed that the docker is picking them up correctly by copying them from the running docker back to the host machine & comparing them with the originals and they are exactly the same. The output of docker ps is: CONTAINER IDIMAGE COMMAND CREATED STATUS PORTS NAMES c2c4cc713c3adpage/pgadmin4 "/entrypoint.sh"17 minutes ago Up 17 minutes 80/tcp, 0.0.0.0:554->443/tcp youthful_ptolemy When I try to access pgAdmin in my browser using https://myserver.com:554 or https://myserverip:554 or https://127.0.0.1:554, I get this response: Secure Connection Failed An error occurred during a connection to intranet.threedradio.com:8443. PR_CONNECT_RESET_ERROR If I telnet to the server on port 554, it connects briefly and then closes the connection, so it's definitely listening on the correct port. I also tried redirecting port 80 to another port in case that was causing a conflict with apache, but that didn't seem to help at all. Hoping someone can help! Cheers, Ian