(Bug report) Today I can't open Trilium!

[StepHaze]

Trilium Version

0.63.3

What operating system are you using?

Ubuntu

What is your setup?

Local (no sync)

Operating System Version

Ubuntu 18.04

Description

Today I can't open Trilium. Here's what I get after I try to run it:

trilium
App db version is 228, while db version is 227. Migration needed.
DB size: 1966 KB
{
"appVersion": "0.63.3",
"dbVersion": 228,
"nodeVersion": "v18.15.0",
"syncVersion": 32,
"buildDate": "2024-03-03T06:58:18+01:00",
"buildRevision": "0ad337c8e806ba84d48d7b97aa46df52d9f236a8",
"dataDirectory": "/home/steepe/snap/trilium/18/.local/share/trilium-data",
"clipperProtocolVersion": "1.0",
"utcDateTime": "2024-03-15T11:27:10.449Z"
}
CPU model: Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz, logical cores: 8 freq: 4000 Mhz
Trusted reverse proxy: false
App HTTP server starting up at port 37840
Port 37840 is already in use. Most likely, another Trilium process is already running. You might try to find it, kill it, and try again.

No another Trilium process is running. Please help me, cause the data in Trilium is important

Error logs

No response

[Nriver]

Some other program is using the port, usually a reboot can solve this. Otherwise you need to find which process is using the port and kill it.

[yuminchao]

The port is occupied

[dosubot[bot]]

This error happens when something else on your system is using port 37840, not necessarily another Trilium process—apps like Thunderbird, Firefox, or system services (like goa-daemon) can grab it too. To find out what’s using the port, run:

sudo lsof -i :37840

or

sudo netstat -peanut | grep 37840

Look for the PID (process ID) in the output, then you can stop it with:

kill <PID>

(Replace <PID> with the actual number. Be careful not to kill critical system processes.)

If you can’t free up the port or don’t want to close the other app, you can start Trilium on a different port:

TRILIUM_PORT=37740 trilium

Or edit the config.ini in your Trilium data directory and set a different port= value. Note: the web clipper extension expects the default port, so changing it may affect that feature. There are some reports that the environment variable might not always work as expected, so editing config.ini is more reliable in some cases [source] [source] [source].

If you haven’t already, a reboot can sometimes clear up stuck ports. Let me know if you need help interpreting the output or editing the config!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[eat-correctly]

@dosu

37840 is an ephemeral client port on Linux (as it lies within the range 32768–60999) and should preferably not be used by server applications. Otherwise, clients on the same machine could receive this port randomly by the kernel and cause this conflict.

A possible solution would be to select a port based on the platform, and outside the ranges listed here.

My ~/.local/share/trilium-data/config.ini says port=8080, yet Trillium still likes to pick 37840 and complain about it.

[eliandoran]

37840 is an ephemeral client port on Linux (as it lies within the range 32768–60999) and should preferably not be used by server applications. Otherwise, clients on the same machine could receive this port randomly by the kernel and cause this conflict.

@eat-correctly , you are absolutely correct about that. Let's track that in #5298.