About an issue in Docker Installation Guide (localhost is needed to be replaced with the name of db container in config.conf), resolution is included.

10 views
Skip to first unread message

Yang Lei

unread,
Jul 30, 2025, 5:23:33 AMJul 30
to Tinode General
### About an issue in Docker Installation Guide (localhost is needed to be replaced with the name of db container in config.conf), resolution is included in the end.

When install in docker way, an error about "connection refused" will be shown, tinode docker failed to connect to db (in my case, postgres, haven't tried other databases, but i guess it should be the same problem), so that it cannot start up.

### Your environment
#### Server-side
- [ ] Your own setup:
  * platform (Mac)
  * version of Tinode server, 0.24.2
  * database backend: postgresql
  * standalone

#### Client-side
- [ ] TinodeWeb/tinodejs: javascript client
  * Browser make and version.


### Steps to reproduce
Follow the installation guide will reproduce the issue

### Expected behaviour
Tinode should work with postgres as expected, it should be able to connect to postgres and start up normally.

### Actual behaviour
"connection refused" will be shown, tinode docker failed to connect to db

### Server-side log
"connection refused" will be shown, tinode docker failed to connect to db

### Client-side log
N/A


### Resolution
Update the installation guide, replace "localhost" with actual database container name in config.conf under corresponding adapter section (in my case, it is postgres), and use this configuration file when starting up tinode container, then tinode is able to connect to the real database other than "localhost"

Gene

unread,
Jul 30, 2025, 10:21:44 AMJul 30
to Tinode General

Yang Lei

unread,
Jul 31, 2025, 12:04:30 AMJul 31
to Tinode General
The config.conf should be tinode.conf, I mistakenly typed

I just want you know that if you follow the installation guide, you will have trouble to start up tinode, as it by default to connect to "localhost" for database. What I have done is replacing the "localhost" with real database container name in tinode.conf,and run tinode container with this tinode.conf. 

Reply all
Reply to author
Forward
0 new messages