SQLState - 08S01 Error Setup Confluence Server with MSQL on Synology Docker

[Van Tor]

I saw online that some users successfully installed confluence server on DSM 6.2.3 synology. Here is my trial:

• confluence-server.lastest installed on the nas
• MSSQL (14.0.3048.4) running docker on the same synology (running with other app fine) - it has no connection issues for various apps.

After completing the installation on docker, In browser, run setup fine (after enter license key) then database setup, the error coming out all times:

Can't reach database server or port

SQLState - 08S01
com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the host localhost, named instance MSSQLSERVER failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host.

 Very likely the cause is "For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host."   SQL Server Browser Service status in container can be viewed? any possible solution?

Anyone can help to resolve this issue?

Thank you.

[Van Tor · Accepted solution]

Resolved for Postgres, not MSSQLSERVER: share with other who use DSM Synology - once you get inside, a very great tool!

Read one article in the site talking about creating a docker net that should be the solution. I am not building it yet.  So far working now.

Installed in Synology Docker:

openJKD (hotspot supported) not sure it is being used by related confluence and db or not:

Postgres10 (supported by confluence)

Confluence: latest

Conventionally failed connecting this way:

You look postgre:

Successfully connected using 172.17.0.1

This caused me a couple of days to try many options to find out a solution. Likely guru may provide NAS public user a guide - how to setup a docker net bridging simply confluence and database (at least workable on postgres).

At this step no need to change (no changes on pg_hba.conf nor postgresql.conf).  I am not sure after reboot, the 172.17.0.1 would be changed or not. At least, Synology DSM users can save a lot of time very smoothly pass the connection troubles.

After digging into confluence from scratch, it is a wonderful world of confluence! Thank mediawiki upgrade crashed on DSM my base (over 1000 pages I cannot retrieve) and forced me move into confluence.

Environment settings for each container should be very helpful for none-tech users like me to make life simple.

Hope the shares help to some NAS users.

[Van Tor]

Just found out the posted reference by Rafael on March 18 2019.  Cheers!

[Moses Thomas · Accepted solution]

@Van Tor 

There  few  things  here that could be the reason

• The  host name might not be  localhost  even better use  "IP address" instead of local host 
• The port,  you need to verify  that database server is running  on "1433" 

  If  you have access to database as admin(Microsoft SQL sever installed) you  need to find the right port.

• Next is to make sure that no fire wall is blocking TCP  connection  to  that port

Kind regards,

Moses

[Van Tor]

Thanks Moses. Indeed it is localhost, also IP tried too. MSSQL Studio works fine with 1433 as well as many nodejs app access to the MSSQL without any problem. For sore no firewall block those ports.  Today I followed your guide, setup PostgreSQL 9.18 but failed too. 

Can't reach database server or port

SQLState - 08001
org.postgresql.util.PSQLException: Connection to localhost:5433 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

Failed too many times by simply setup db connections. 

Thank you.

[Van Tor]

For PostgreSQL: now turned to the error: 

Can't reach database server or port

SQLState - 08001
org.postgresql.util.PSQLException: The connection attempt failed.

The login user has been temporally fully granted as a super user still failed.

[Moses Thomas]

@Van Tor 

You need to look for the configuration file in the postgres installation folder in Windows the file should be

"postgresql.conf"

Listen address would be listen_addresses = '::' most likely

Change it to listen_addresses = 'localhost' or IP address of the server

Regarding MS SQL server something must be blocking it for sure.

It should also work check whether or not TCP/IP is enabled see here on how.

Enable Named Pipes and TCP/IP Connections 

There is also similar issue here Bitbucket with MS SQL named server 

Try and give feed back.

Kind regards,

Mo

[Van Tor]

Thanks Moses!  I am using MSSQL container and it seems no way that I can find out any where to enable the browser service. It's totally strange why my nodejs apps can use the similar syntax to connect the exact docker MSSQL on my nas? Best

[Van Tor]

I did change "postgresql.conf" tried both MSSQL and postgres but no luck. 

[Moses Thomas]

@Van Tor 

Remember to restart the postgresql server and check again if no progress  then

please show what is in the Configuration file  of Postgre  there could be some configuration issue.

Kind regards,

Mo

[Van Tor]

postgres works fine and the above shared screenshots should be helpful for those Synology NASers. Thank you Mo!