Trilium Next
-
|
Hi all, As a precursor, I'm not a dev, and don't play one on television. I'm a retired electro-mechanic engineer wanting to stand up some tools. I've got a homelab setup comprising 2 HP Elitedesk machines with Ubuntu server and docker installed on both. The primary machine has been initialized as the primary swarm device, with the other a secondary. Portainer has been installed on the primary machine and all is well. The primary machine is set up at 192.168.10.16, with the secondary at 192.168.10.17. A cloudflare account has been setup, and my base URL is mydomain.com (not really....) Traefik has been setup as a Portainer stack. The config file looks like this: `version: "3.7" services: whoami: networks: volumes: Using the docs here, I've set up a treafik.yml file that looks like:
This works just fine with the dashboard available at traefik.mydomain.com Per the docs. my Trilium stack looks like: `version: "3.7" services: networks: Everything runs, and the service log shows this:
But, that's as far as I can get. https://trilium.mydomain.com gives a 404 error, and trying to do a 192.168.10.16:8080 just says the site can't be reached. According to Portainer trilium is on the Primary machine. I've even tried to do 192.168.10.17:8080, and it says its not secure, but then goes to a 404 error. Any light you can shine on this would be greatly appreciated. I'm pulling out what little hair I have left. chris |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 15 replies
-
|
Sorry for the formatting. |
Beta Was this translation helpful? Give feedback.
-
|
No worries about the formatting! Here’s what’s most likely causing the 404s and access issues with Trilium behind Traefik:
If you make changes, clear your browser cache or use an incognito window to avoid cached errors. The latest Traefik setup docs for Trilium are here. If you need a step-by-step checklist or want to share your updated compose files, let me know! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
Ok. All done. Same result. What does this mean? http://[your-server-host]:8080 Thanks |
Beta Was this translation helpful? Give feedback.
-
|
That message is a placeholder—Trilium is telling you to visit the setup page at the actual address of the machine running Trilium, on port 8080. So you should replace If you can't reach that address, it usually means Trilium isn't accessible on the network, the container isn't healthy, or the proxy/network setup is blocking access. Double-check that the container is running and healthy, port 8080 is open, and your Docker network and Traefik routing are correct. If you still get a 404 or can't connect, check Trilium and Traefik logs for errors and confirm your network setup. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, Fewer hairs left.... Logs all look ok: Traefik: docker service logs -f traefik_traefik Trilium: docker service logs -f trilium_trilium But still no connection: Would someone please review my yml files? Traefik tls.yml: Trilium: Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Your YAML files have a couple of key issues that will prevent Traefik from routing to Trilium: 1. Network name mismatch: and make sure both Traefik and Trilium are attached to this network in their 2. Traefik encoded character settings: entryPoints:
web:
address: :80
http:
encodedCharacters:
allowEncodedSlash: true
allowEncodedBackSlash: true
allowEncodedNullCharacter: true
allowEncodedSemicolon: true
allowEncodedPercent: true
allowEncodedQuestionMark: true
allowEncodedHash: true
websecure:
address: :443
http:
encodedCharacters:
allowEncodedSlash: true
allowEncodedBackSlash: true
allowEncodedNullCharacter: true
allowEncodedSemicolon: true
allowEncodedPercent: true
allowEncodedQuestionMark: true
allowEncodedHash: trueThis is required for Trilium to work behind Traefik source. 3. Traefik labels and environment variables:
4. Runtime checks:
5. Browser cache: If you fix the network name and encoded character settings, Trilium should be accessible via Traefik. More details and examples are in the setup docs and recent user reports. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
Ok. Everything updated per comments. I was using Portainer, and decided to do straight docker stack commands. From the primary (192.168.10.16), docker network ls docker service ps trilium_trilium (This indicates Trilium is running on 192.168.10.17) docker service inspect trilium_trilium curl http://192.168.10.17:8080 and from the secondary (192.168.10.17): curl http://192.168.10.16:8080 Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Yee ha. Going through the process again and opening http://192.168.10.17:8080/ from Brave, the initialization screen shows up. It synced and my desktop client can sync to it. I removed the port stuff from the docker file and redeployed, but https://trilium.mydomain.com is not available, and trilium doesn't show up in the Traefik dashboard. Thank you for the amazing progress. Chris |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I've included the port stuff back and redeployed and opened 192.168.10.17:8080 in a private window. I'm looking at the browser console. In the console tab, I've got: The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header. The network tab doesn't show any errors. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Those Cross-Origin-Opener-Policy and Origin-Agent-Cluster warnings are expected when you access Trilium over plain HTTP from a non-localhost address. Trilium sets strict security headers by default, and browsers ignore them unless the site is served over HTTPS or localhost. These warnings don’t block Trilium’s core features—they just mean some advanced browser isolation features are unavailable over HTTP, which is fine for setup and testing. You don’t need to worry about them unless you’re building integrations that require those features or want to eliminate the warnings for a production setup. For full browser security and to get rid of those warnings, access Trilium through HTTPS (e.g., https://trilium.mydomain.com) via Traefik. If you’re still having trouble with HTTPS access or Traefik not routing to Trilium, double-check that:
If you see a blank screen or missing UI elements, check the browser dev tools for missing static assets (fonts, CSS, JS) or failed requests—these are usually signs of proxy misconfiguration or asset loading issues. You can safely ignore those specific console warnings when using HTTP for setup or debugging—they don’t indicate a problem with Trilium itself. For production, use HTTPS to avoid them and get full browser feature support. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
The network is defined as traefik_proxy (with traefik_traefik_proxy in the Swarm network) in the in the Traefik setup, whilst it's defined as traefik_treafik_proxy in the trilium setup. I tried making them all traefik_proxy, but that doesn't work. I don't understand this. The entrypoints are defined as such: entryPoints: Trilium does not show up in the Traefik dashboard. I'm accessing both http://192.168.10.17:8080 and https://trilium.mydomain.com from a fresh private window. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
The network name must match exactly—case, spelling, and underscores—in every place: the Docker network definition, the To fix this, pick one name (for example,
If Trilium still doesn’t show up in the Traefik dashboard, check that the Trilium container is marked healthy—Traefik ignores unhealthy containers. If you upgraded Trilium recently, you may need to remove and recreate the container to refresh the healthcheck metadata source. Once the network name matches everywhere and Trilium is healthy, Traefik should discover it and route traffic as expected source. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
My head hurts. I created an attachable overlay external network: traefik_proxy. I referenced it in traefik stack: services: API & DashboardDeploy the Whoami applicationwhoami: Define the overlay network for Swarmnetworks: I've got a tls file that defines the endpoints: tls: entryPoints: Fired it up, this works fine. No errors in the logs. Set the network the same in the Trilium stack: services: networks: Fires up fine, There is now one network, traefik_proxy NETWORK ID NAME DRIVER SCOPE I can access Trilium from http:192.168.10.17:8080, but not from trilium.mydomain.com. There is no reference to Trilium in Traefik. Looking in Portainer both Traefik and Trilium are using traefik_proxy which is at 10.0.0.0/24 locally Save me.... |
Beta Was this translation helpful? Give feedback.
-
|
You're extremely close—your network and label setup is almost correct, but there are a few subtle things that can prevent Traefik from discovering Trilium in Swarm mode:
Checklist:
If Trilium still doesn't show up, paste the output of References: To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
Okay @dosu. This is my last gasp. I need to get my life back.... It's obvious that Traefik isn't recognizing Trilium.
docker network inspect traefik_proxy docker service inspect traefik_traefik docker service inspect trilium_trilium |
Beta Was this translation helpful? Give feedback.
-
|
Ok I give up. Trilium (and Mealie) refuse to work in Docker Swarm mode. |
Beta Was this translation helpful? Give feedback.
Ok I give up.
Trilium (and Mealie) refuse to work in Docker Swarm mode.