Pangolin Configuration

[chocology]

Hi Everyone,

As Pangolin is now becoming a popular alternative to Traefik, I was wondering if we could get some official documentation on how to set it up please? I have it running but been observing some weird behaviours where I cannot write any text. I think we need to have some paths allowed. It would be documented on this page for example https://docs.pangolin.net/manage/access-control/rules#rules-for-specific-apps and I think it is a win for TriliumNext.

So far I have /share and /assets allowed but it is still behaving odd as when I create a new note, I can only type in the title and nothing else. I am running it on Truenas Scale by the way. Thank you for your help in advance

[dosubot[bot]]

Hi @chocology! I'm Dosu and I’m helping the Trilium team.

To get Trilium fully working behind Pangolin, you need to allow more than just /share and /assets. Trilium’s web app relies on a wide set of API endpoints under /api for editing, saving, and interacting with notes. If these are blocked, you’ll see issues like being unable to type in notes or save changes.

Here’s what you should allow in Pangolin for Trilium:

• /api/*
• /assets/*
• /share/*
• /share/assets/*
• /assets/v*/src/*
• /assets/v*/stylesheets/*
• /assets/v*/fonts/*
• /assets/v*/translations/*
• /assets/v*/images/*
• /assets/v*/doc_notes/*
• /node_modules/* (if you see missing JS/CSS in the UI)

A minimal Pangolin rule set (using their docs’ style) might look like:

access_control:
  rules:
    - allow: ["/api/*", "/assets/*", "/share/*", "/share/assets/*", "/node_modules/*"]

Make sure Pangolin is not rewriting or stripping these paths—requests must reach Trilium unchanged. Also, ensure all HTTP methods (GET, POST, PUT, DELETE, PATCH) are allowed for these paths.

Other important reverse proxy tips:

• Forward headers: Upgrade, Connection, Host, X-Real-IP, X-Forwarded-For, X-Forwarded-Proto.
• Use HTTP/1.1 for API/WebSocket support.
• Set trustedReverseProxy=true in Trilium’s config.ini under [Network] or as the env var TRILIUM_NETWORK_TRUSTEDREVERSEPROXY=true for correct HTTPS/redirect handling.
• If you see 502 errors or asset fetch failures, increase proxy buffer sizes if Pangolin supports it.
• After changing proxy rules, do a hard refresh in your browser to clear cached JS files.

If you’re still having issues, try accessing /api/setup/status and a static asset (like a JS file under /assets/) directly—if you get an HTML error page, the proxy is still blocking something it shouldn’t. For more details, see this discussion and Trilium’s reverse proxy examples.

Let me know if you need a more specific Pangolin config example or run into any other issues!

To reply, just mention @dosu.

---

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

   

[chocology]

Wow, thank you so much @dosu !!! I love the app and been pulling my hair out to figure it out. My sincere gratitude and compliments for the fast and through response.

[dosubot[bot]]

You're very welcome! I'm really glad I could help. If you run into any more issues or have questions about Trilium or your setup, just let me know—I'm always here to help. Enjoy using Trilium!

To reply, just mention @dosu.

---

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

   

[chocology]

@dosu I have added the paths mentioned but the issue is this the same. When I add the env variable TRILIUM_NETWORK_TRUSTEDREVERSEPROXY=true it just does not load up

[dosubot[bot]]

The 400 Bad Request errors and loading issues happen because TRILIUM_NETWORK_TRUSTEDREVERSEPROXY must be set to the actual IP address of your Pangolin proxy, not just true. Setting it to true only works if your proxy is forwarding all the correct headers in the expected format—otherwise, Express (the web server Trilium uses) will reject requests with 400 errors if the headers are missing or malformed. This is a common pitfall with reverse proxy setups for Trilium and is documented in several places (example, example).

To fix this:

1. Find the IP address of your Pangolin proxy (the internal IP from which it connects to Trilium).
2. Set TRILIUM_NETWORK_TRUSTEDREVERSEPROXY=<that IP address> in your environment or config.
3. Make sure Pangolin is forwarding these headers to Trilium: Host, X-Real-IP, X-Forwarded-For, X-Forwarded-Proto, Upgrade, and Connection.
4. Do a hard refresh in your browser after making changes.

If you’re not sure what IP to use, check your Trilium logs after a request—look for the remote address of incoming connections from Pangolin.

If you still have issues, please share your Pangolin config (especially header forwarding rules) and any relevant Trilium logs. This will help pinpoint any remaining proxy or header issues.

To reply, just mention @dosu.

---

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