Pangolin Docker Container permanently restarting #141

New Issue

2025-11-13T11:51:14-06:00

GiteaMirror commented

2025-11-13 11:51:14 -06:00

Originally created by @TheRealSaeba on GitHub (Mar 12, 2025).

Ubuntu 24.02. on VPS
After running the installation script, the installation finishes with "container unhealthy".

After restarting the VPS, executing "docker ps" command shows that the pangolin container is permanently restarting.

After executing "docker logs pangolin" command, I get hundreds of similar entries like this:

> @fosrl/pangolin@0.0.0 start
> NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'

Running migrations...
Migrations completed successfully.
/app/server/lib/config.ts:170
                    throw new Error(
                          ^


Error: Error loading configuration file: unknown escape sequence (49:40)

 46 |  ...
 47 |  ... r_admin:
 48 |  ... mail: "admin@XXXXXX.site"   <---- Mail obfuscated by me
 49 |  ... assword: "*****************AF\,~*****************************"  <--- Pasword obfuscated by me
-----------------------------------------^
 50 |  ...
 51 |  ...
    at loadConfig (/app/server/lib/config.ts:170:27)
    at Config.loadConfig (/app/server/lib/config.ts:180:27)
    at new Config (/app/server/lib/config.ts:159:14)
    at <anonymous> (/app/server/lib/config.ts:256:23)

Node.js v20.18.3

It seems like the password I entered during installation contained characters ( the backslash?) which are not correctly handled or interpreted as escape sequence and not as the character itself.

The installation guide states that at least one "special character" should be used for the password. It does not exclude certain characters.

I will try deinstalling all docker containers and running the installation script with a password that does not contain the backslash.

Originally created by @TheRealSaeba on GitHub (Mar 12, 2025). Ubuntu 24.02. on VPS After running the installation script, the installation finishes with "container unhealthy". After restarting the VPS, executing "docker ps" command shows that the pangolin container is permanently restarting. After executing "docker logs pangolin" command, I get hundreds of similar entries like this: ``` > @fosrl/pangolin@0.0.0 start > NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' Running migrations... Migrations completed successfully. /app/server/lib/config.ts:170 throw new Error( ^ Error: Error loading configuration file: unknown escape sequence (49:40) 46 | ... 47 | ... r_admin: 48 | ... mail: "admin@XXXXXX.site" <---- Mail obfuscated by me 49 | ... assword: "*****************AF\,~*****************************" <--- Pasword obfuscated by me -----------------------------------------^ 50 | ... 51 | ... at loadConfig (/app/server/lib/config.ts:170:27) at Config.loadConfig (/app/server/lib/config.ts:180:27) at new Config (/app/server/lib/config.ts:159:14) at <anonymous> (/app/server/lib/config.ts:256:23) Node.js v20.18.3 ``` It seems like the password I entered during installation contained characters ( the backslash?) which are not correctly handled or interpreted as escape sequence and not as the character itself. The installation guide states that at least one "special character" should be used for the password. It does not exclude certain characters. I will try deinstalling all docker containers and running the installation script with a password that does not contain the backslash.

GiteaMirror closed this issue

2025-11-13 11:51:14 -06:00

GiteaMirror commented

2025-11-13 11:51:15 -06:00

@miloschwartz commented on GitHub (Mar 12, 2025):

Ah okay yeah I can see how the backslash would cause an issue here. You don't have to re run the installer to fix this. Instead you can edit the config file and change the password since the installer already set everything up for you.

@miloschwartz commented on GitHub (Mar 12, 2025): Ah okay yeah I can see how the backslash would cause an issue here. You don't have to re run the installer to fix this. Instead you can edit the config file and change the password since the installer already set everything up for you.

GiteaMirror commented

2025-11-13 11:51:15 -06:00

@TheRealSaeba commented on GitHub (Mar 12, 2025):

Thank you for the quick response. I will figure out how to do this :)

@TheRealSaeba commented on GitHub (Mar 12, 2025): Thank you for the quick response. I will figure out how to do this :)