how to modify default starting up port(8080)

[mintisan]

Trilium Version

2.1

What operating system are you using?

Ubuntu

What is your setup?

Server access only

Operating System Version

Linux raspberrypi 6.1.0-rpi4-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (2023-10-05) aarch64 GNU/Linux

Description

I already use 8080 as my other web service port. So I can't use 8080 port any more.

So I installed trilium with command as below:[And I also export TRILIUM_PORT=8081]

docker run -d --name trilium -p 5050:5050 -e TRILIUM_PORT=8081 -v ~/trilium-data:/home/node/trilium-data zadam/trilium

But not works, docker ps as below:

➜  trilium-data dodocker ps                                                                                                             
CONTAINER ID   IMAGE                                            COMMAND                  CREATED          STATUS                          PORTS                                                 NAMES
5b524929ba4d   zadam/trilium                                    "docker-entrypoint.s…"   13 minutes ago   Up 13 minutes (healthy)         0.0.0.0:5050->5050/tcp, :::5050->5050/tcp, 8080/tcp   trilium

If I missed something,,,

Error logs

log

11:52:46.106 Generated session secret
11:52:46.628 DB not initialized, please visit setup page - http://[your-server-host]:8080 to see instructions on how to initialize Trilium.
11:52:46.628 DB size: 4 KB
11:52:47.350 {
  "appVersion": "0.62.2",
  "dbVersion": 227,
  "syncVersion": 31,
  "buildDate": "2023-11-21T20:49:24+01:00",
  "buildRevision": "e2b1421bf3d764ffe444a103c118e67d8c563673",
  "dataDirectory": "/home/node/trilium-data",
  "clipperProtocolVersion": "1.0",
  "utcDateTime": "2023-11-27T11:52:46.423Z"
}
11:52:47.350 CPU model: Cortex-A76, logical cores: 4 freq: 2400 Mhz
11:52:47.351 Trusted reverse proxy: false
11:52:47.352 App HTTP server starting up at port 8080
11:52:47.357 Listening on port 8080
11:53:16.090 200 GET /api/health-check with 15 bytes took 6ms
11:53:46.292 200 GET /api/health-check with 15 bytes took 1ms
11:54:16.512 200 GET /api/health-check with 15 bytes took 1ms
11:54:46.719 200 GET /api/health-check with 15 bytes took 1ms
11:55:16.927 200 GET /api/health-check with 15 bytes took 1ms
11:55:47.136 200 GET /api/health-check with 15 bytes took 2ms
11:56:17.334 200 GET /api/health-check with 15 bytes took 1ms
11:56:47.540 200 GET /api/health-check with 15 bytes took 2ms
11:57:17.737 200 GET /api/health-check with 15 bytes took 2ms
11:57:47.931 200 GET /api/health-check with 15 bytes took 1ms
11:57:53.711 DB not initialized, please visit setup page - http://[your-server-host]:8080 to see instructions on how to initialize Trilium.
11:57:53.712 DB size: 4 KB
11:57:54.413 {
  "appVersion": "0.62.2",
  "dbVersion": 227,
  "syncVersion": 31,
  "buildDate": "2023-11-21T20:49:24+01:00",
  "buildRevision": "e2b1421bf3d764ffe444a103c118e67d8c563673",
  "dataDirectory": "/home/node/trilium-data",
  "clipperProtocolVersion": "1.0",
  "utcDateTime": "2023-11-27T11:57:53.514Z"
}
11:57:54.414 CPU model: Cortex-A76, logical cores: 4 freq: 2400 Mhz
11:57:54.414 Trusted reverse proxy: false
11:57:54.415 App HTTP server starting up at port 8080
11:57:54.421 Listening on port 8080
11:58:23.174 200 GET /api/health-check with 15 bytes took 6ms
11:58:53.378 200 GET /api/health-check with 15 bytes took 1ms
11:59:23.576 200 GET /api/health-check with 15 bytes took 1ms
11:59:53.784 200 GET /api/health-check with 15 bytes took 1ms
12:00:23.989 200 GET /api/health-check with 15 bytes took 1ms
12:00:54.176 200 GET /api/health-check with 15 bytes took 1ms
12:01:24.345 200 GET /api/health-check with 15 bytes took 1ms
12:01:54.554 200 GET /api/health-check with 15 bytes took 2ms
12:02:24.747 200 GET /api/health-check with 15 bytes took 2ms
12:02:54.944 200 GET /api/health-check with 15 bytes took 1ms
12:03:25.136 200 GET /api/health-check with 15 bytes took 1ms
12:04:27.203 DB not initialized, please visit setup page - http://[your-server-host]:8080 to see instructions on how to initialize Trilium.
12:04:27.205 DB size: 4 KB
12:04:27.894 {
  "appVersion": "0.62.2",
  "dbVersion": 227,
  "syncVersion": 31,
  "buildDate": "2023-11-21T20:49:24+01:00",
  "buildRevision": "e2b1421bf3d764ffe444a103c118e67d8c563673",
  "dataDirectory": "/home/node/trilium-data",
  "clipperProtocolVersion": "1.0",
  "utcDateTime": "2023-11-27T12:04:27.019Z"
}
12:04:27.895 CPU model: Cortex-A76, logical cores: 4 freq: 2400 Mhz
12:04:27.895 Trusted reverse proxy: false

[henrikx]

Hi!
Since you are using Docker, it does not matter which port Trilium itself is running at as it will only run at that port inside the container. In the -p 5050:5050 argument you are telling Docker which port inside the container you want to forward outside of it and which port it should forward to.

To put it concretely this is what you need to do:

1. Remove the -e TRILIUM_PORT argument as you do not need it.
2. Change the -p 5050:5050 argument to -p 8081:8080 which will forward port 8080 inside the container to 8081 on your actual network.
3. Restart the container.

You can read more about Docker networking here https://docs.docker.com/network/

[deajan]

Just adding my grain of salt. @henrikx is right about the docker command which can just replace the mapped port from docker to localhost.
When not using docker, one can change the used port in config.ini as stated here

[meichthys]

Closing as there are multiple working solutions here.