First-class way to handle running trilium out of a subdirectory behind a reverse proxy

[tbeckley]

Describe feature

Add support for disabling remote access when sitting behind a reverse proxy, and add TRILIUM_SUBPATH field to config to change URL path

Additional Information

Trilium user here who runs the server it behind a reverse proxy so I can access my note remotely. I run other apps on this machine so I'd like to run out of a sub-path, /trilium/ and for all links to be shifted. To better support reverse proxies, I have 2 feature requests:

1. Add an option under [network] to include TRILIUM_SUBPATH= (deafult blank). Adding a path (e.g. "/trilium") would add that section in between the base URL and any path. I found this issue that gives a workaround at the proxy level but it's not extensible to future new paths, doesn't handle conflicts well with other apps that use the /api/ path and also I don't think was ever added to the wiki.

2) Add a config option to disable remote access (i.e. bind to 127.0.0.1 instead of 0.0.0.0). Or perhaps one could change the "trustedReverseProxy" option so that "only" disables remote access and only permits through the proxies? Not sure the best way to handle this w/r/t backwards compatibility. I'm dumb, this is literally in the options. Ignore this.

If these both look good in principle I'm happy to take a stab at implementation, but don't want to throw time at something that isn't acceptable to the maintainers. Thanks for all your hard work!

[hulmgulm]

Trilium already works behind a reverse proxy with a different path. I didn't check the Apache documentation, but the nginx reverse proxy documentation explains how to do this: https://github.com/TriliumNext/Trilium/tree/main/docs/User%20Guide/User%20Guide/Installation%20%26%20Setup/Server%20Installation/2.%20Reverse%20proxy

[neagix]

Logout does not seem to work: it redirects to root /login and stays logged in.

[hulmgulm]

Btw, I already run my Trilum instance at https://www.example.com/notes and it works without any issues.

[tbeckley]

Oh you're right. It's not in the apache2 documentation and I didn't think to check the nginx docs, whoops. Closing since this is already resolved..