Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Setup your database - 'The port number ____ is not valid.'

James Bloggs September 21, 2021

I'm trying to set up confluence with a MS SQL Server database - both in docker containers(Ubuntu images provided by Atlassian and MS).

Both containers are running, with my database created and the various environment variables set as directed.

In browser, at 'Setup your database' I get the following:

 

Problem connecting to your database

com.microsoft.sqlserver.jdbc.SQLServerException: The port number sqlserver://db:1433 is not valid.

 

This is refering to my entry in 'Hostname:' which is 'jdbc:sqlserver://db:1433;databaseName=confluence'. All other fields are filled in correctly as far as i can tell. Apologies for the lack of pictures.

 

Any help appreciated!

2 answers

0 votes
Kishan Sharma
Community Champion
September 22, 2021

Hi @James Bloggs Welcome to the Atlassian Community! Please check if you have configured MS SQL to allow connection to port 1433 for SQL to communicate. Refer comment on this article, which is relevant here too.

James Bloggs September 22, 2021

@Kishan Sharmathanks for your help, the real issue was an incorrectly installed driver. Thank you for your time!

Kishan Sharma
Community Champion
September 22, 2021

you are welcome James, glad you got it working now!

Like James Bloggs likes this
James Bloggs September 22, 2021

Me too :D

0 votes
Alan Stephenson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 21, 2021

Try to telnet to the server using port 1433. Like

telnet servername 1433

if you get a response then the port is listening. If you get a waiting message make sure port 1433 is listening or enabled on both sides (source and destination)

James Bloggs September 22, 2021

Thanks to you as well Alan! Sorry about the time wasting.

Alan Stephenson
Community Champion
September 22, 2021

No worries. I am glad you got it working. These type of errors sometimes are hard to find. I suggested that one because from my experience with SFTP processes and port numbers. If the port isn't "listening" the connection won't happen.

Like James Bloggs likes this
James Bloggs September 23, 2021

Ok, also of note was the Hostname at set up needed to be different to the format in the docs... for me '<hostname>:<port_number>' worked by fluke, instead of the longer format given in the docs.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events