Installation issue - KnexTimeoutError #75

New Issue

OVERLORD · 2026-02-04T17:00:58+03:00

OVERLORD commented

2026-02-04 17:00:58 +03:00

Originally created by @AndyYangUK on GitHub (Mar 10, 2021).

Hi

I'm trying to install Planka via the provided docker-compose file but running into an error that I cannot figure out.

In the docker-compose file, I updated the domain to https://test.mydomain.com and updated the secret key, as per the instructions.

After doing docker-compose up, I check the logs and see the following message on the planka container

today at 4:01 PM  /app/node_modules/knex/lib/client.js:348
today at 4:01 PM          convertedError = new KnexTimeoutError(
today at 4:01 PM                           ^
today at 4:01 PM  
today at 4:01 PM  KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
today at 4:01 PM      at Client_PG.acquireConnection (/app/node_modules/knex/lib/client.js:348:26)
today at 4:01 PM      at async /app/db/init.js:7:22 {
today at 4:01 PM    sql: undefined,
today at 4:01 PM    bindings: undefined
today at 4:01 PM  }
today at 4:01 PM  Tried 5 times. Waiting 5 seconds...

For context, here's my setup

Ubuntu 20.04 LTS
Kernel 5.6.0
Server: Kimsufi KS-1

Originally created by @AndyYangUK on GitHub (Mar 10, 2021). Hi I'm trying to install Planka via the provided docker-compose file but running into an error that I cannot figure out. In the docker-compose file, I updated the domain to https://test.mydomain.com and updated the secret key, as per the instructions. After doing `docker-compose up`, I check the logs and see the following message on the planka container ``` today at 4:01 PM /app/node_modules/knex/lib/client.js:348 today at 4:01 PM convertedError = new KnexTimeoutError( today at 4:01 PM ^ today at 4:01 PM today at 4:01 PM KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? today at 4:01 PM at Client_PG.acquireConnection (/app/node_modules/knex/lib/client.js:348:26) today at 4:01 PM at async /app/db/init.js:7:22 { today at 4:01 PM sql: undefined, today at 4:01 PM bindings: undefined today at 4:01 PM } today at 4:01 PM Tried 5 times. Waiting 5 seconds... ``` For context, here's my setup * Ubuntu 20.04 LTS * Kernel 5.6.0 * Server: [Kimsufi KS-1](https://www.kimsufi.com/en/servers.xml)

OVERLORD closed this issue

2026-02-04 17:01:04 +03:00

OVERLORD commented

2026-02-04 17:01:14 +03:00

@VozDeOuro commented on GitHub (Jul 14, 2022):

did you fix it ?

@VozDeOuro commented on GitHub (Jul 14, 2022): did you fix it ?

OVERLORD commented

2026-02-04 17:01:21 +03:00

@amitjethani commented on GitHub (Oct 12, 2022):

I realize this is a year+ old issue, but I'm having the exact same problem with a Synology NAS when deploying using Portainer. Everything worked well the first time around, but a reboot has left things in a broken state.

@amitjethani commented on GitHub (Oct 12, 2022): I realize this is a year+ old issue, but I'm having the exact same problem with a Synology NAS when deploying using Portainer. Everything worked well the first time around, but a reboot has left things in a broken state.

OVERLORD commented

2026-02-04 17:01:32 +03:00

@amitjethani commented on GitHub (Oct 13, 2022):

Edit: this is solved. Turned out to be a firewall issue.

@amitjethani commented on GitHub (Oct 13, 2022): Edit: this is solved. Turned out to be a firewall issue.

OVERLORD commented

2026-02-04 17:01:37 +03:00

@jamesutter commented on GitHub (May 10, 2024):

@amitjethani I had a similar issue with the Synology firewall. I'm adding my solution, as I solved my issue by adding a firewall rule for the planka_default docker bridge network as follows:

In Container Manager > Network, expand the planka_default docker bridge network and take note of the subnet (e.g. 172..21.0.0/16)
In Control Panel > Security > Firewall: Firewall Profile, click "Edit Rules".
Create the following firewall rule, and click OK:

Ports: All
Source IP: Specific IP with the subnet from above in the IP address field (e.g. 172..21.0.0), and the subnet mask (e.g. /16 becomes 255.255.0.0).
Action: Allow

Move the rule prior to the final Deny All rule, click OK, and apply the firewall settings.

The docker containers will now be able to communicate with each other. They will also be able to access the internet.

@jamesutter commented on GitHub (May 10, 2024): @amitjethani I had a similar issue with the Synology firewall. I'm adding my solution, as I solved my issue by adding a firewall rule for the _planka_default_ docker bridge network as follows: 1. In **Container Manager > Network**, expand the _planka_default_ docker bridge network and take note of the subnet (e.g. 172..21.0.0/16) 2. In **Control Panel > Security > Firewall**: Firewall Profile, click "Edit Rules". 3. Create the following firewall rule, and click OK: - _Ports: All_ - _Source IP: Specific IP_ with the subnet from above in the IP address field (e.g. 172..21.0.0), and the subnet mask (e.g. /16 becomes 255.255.0.0). - _Action: Allow_ 4. Move the rule prior to the final Deny All rule, click OK, and apply the firewall settings. The docker containers will now be able to communicate with each other. They will also be able to access the internet.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#75