Trilium Next is not installing correctly on UnRAID #7107
Replies: 2 comments 2 replies
-
Hi @ronsonntag54! I'm Dosu and I’m helping the Trilium team. The "connection refused" error with Trilium Next on UnRAID is usually caused by port mapping issues or the service not starting correctly. Trilium Next's Docker image defaults to listening on port 8080 inside the container, even if you want to access it on port 9999 externally. You need to map the ports explicitly in your UnRAID Docker setup—use If you're using a reverse proxy (like nginx), make sure your proxy config is correct and that buffer sizes are set high enough to avoid 502 errors during OAuth login. Also, check the container logs for any startup errors or missing environment variables, especially those related to OAuth/OpenID if you're using them. There are no known fundamental compatibility issues between Trilium Next and UnRAID, but careful Docker and proxy configuration is necessary for a successful install and login flow. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
@dosu, thank you for your help. I have things up and running and am pretty excited to port all my Keep notes over to Trilium. One question: Is TriliumDroid distributed via F-Droid / IzzyOnDroid repositories safe and are the features complete enough to effectively use or should I stick with running it from a browser on my Pixel 6 Pro?
-Ron
On Friday, September 26, 2025 at 03:18:48 PM PDT, dosubot[bot] ***@***.***> wrote:
Hi @ronsonntag54! I'm Dosu and I’m helping the Trilium team.
The "connection refused" error with Trilium Next on UnRAID is usually caused by port mapping issues or the service not starting correctly. Trilium Next's Docker image defaults to listening on port 8080 inside the container, even if you want to access it on port 9999 externally. You need to map the ports explicitly in your UnRAID Docker setup—use -p 9999:8080 to expose Trilium Next on host port 9999 if the container listens on 8080. If you map -p 9999:9999 but the app is listening on 8080, you'll get a connection refused error. Double-check your Docker port mapping and make sure the container is running and healthy.
If you're using a reverse proxy (like nginx), make sure your proxy config is correct and that buffer sizes are set high enough to avoid 502 errors during OAuth login. Also, check the container logs for any startup errors or missing environment variables, especially those related to OAuth/OpenID if you're using them. There are no known fundamental compatibility issues between Trilium Next and UnRAID, but careful Docker and proxy configuration is necessary for a successful install and login flow.
Reference
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Trilium installs correctly. But, if I try to install Trilium Next along with it (uses :9999 for Web), or, if I install it alone on UnRAID, I get a connection refused when I should get a new password prompt.
Beta Was this translation helpful? Give feedback.
All reactions