Where to change the base url for reverse proxies?

[bezko]

Hi, I recently upgraded to the develop version, had all sorts of trouble to make it work but now the server finally runs, unfortunately I can no longer log in since all assets are still pointing to localhost in the served html instead of the proxy URL:

`

<script src="http://localhost:4200/assets/v0.94.1/src/runtime.js" crossorigin type="module"></script> --   | <script src="http://localhost:4200/assets/v0.94.1/src/login.js" crossorigin type="module"></script> `

I didn't have this problem until after 0.93 and now there are so many config files not sure which one I need to edit to make this works.

Thanks in advance.

[dosubot[bot]]

Hi @bezko! I'm Dosu and I’m helping the Notes team.

You don't need to change any config file in Trilium itself for the base URL—this should be handled entirely in your reverse proxy (like Nginx or Apache). Trilium now uses relative paths, so the recommended approach is to configure your reverse proxy to rewrite and forward requests to the correct backend, ensuring asset URLs point to your proxy URL instead of localhost. There is no built-in BaseURL setting in Trilium for this purpose, and handling subpaths or mounting under a base URL must be done at the proxy level, not in Trilium's config reference.

If you’re using Nginx, you may need a location block like this to handle assets (example from a previous workaround):

location /assets/ {
  proxy_pass http://trilium;
  proxy_set_header Host $host;
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "Upgrade";
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header X-Forwarded-Proto $scheme;
  proxy_read_timeout 90;
  proxy_http_version 1.1;
}

source

If you’re running behind a reverse proxy, make sure the trustedReverseProxy setting in your config.ini is set appropriately so Trilium trusts the proxy headers, but this does not affect asset URLs or base path—just client IP and protocol handling source.

If you need to serve Trilium under a subpath (like /notes/), all rewriting and path handling must be done in your reverse proxy config. Trilium itself does not have a setting for this.

To reply, just mention @dosu.

---

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

[eliandoran]

@bezko , I believe you're running the server as pnpm nx server:serve. This is meant for development, not real use.
You can run pnpm nx server:start-prod if you need.

Nevertheless, it's generally not recommended to base your setups on development environments, you can use the [nightly builds] (https://github.com/TriliumNext/Notes/releases/tag/nightly)instead.