You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Hello,
I tried to set up the 3DCityDB and WFS Docker container and the WFS container does not seem to be able to connect to the PostgreSQL of the 3DCityDB container. I checked the port, DB name and user name and password and it seems all correct. I also tried to connect via Navicat and I can see the citydb DB. This is the error I get:
[localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSourceProxy.getPool Error during connection pool creation. org.postgresql.util.PSQLException: Connection to localhost:5435 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Any ideas`? Is there a need to adjust pg_hba.conf maybe? I do not know, though, how to do this within the 3DCityDB container. Thanks in advance.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I tried to set up the 3DCityDB and WFS Docker container and the WFS container does not seem to be able to connect to the PostgreSQL of the 3DCityDB container. I checked the port, DB name and user name and password and it seems all correct. I also tried to connect via Navicat and I can see the citydb DB. This is the error I get:
[localhost-startStop-1] org.apache.tomcat.jdbc.pool.DataSourceProxy.getPool Error during connection pool creation. org.postgresql.util.PSQLException: Connection to localhost:5435 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Any ideas`? Is there a need to adjust pg_hba.conf maybe? I do not know, though, how to do this within the 3DCityDB container. Thanks in advance.
The text was updated successfully, but these errors were encountered: