When setting SITE_URL to something like https://myhost.domain.com/infisical the gui still tries to load ressources from https://myhost.domain.com e.g. https://myhost.domain.com/images/loading/loading.gif.
My nginx is passing everything to http://localhost:3000 (that's where infisical runs):
Access infisical by subdirectory. Also expect some kind of documentation for using reverse proxies. No info on custom headers (if needed) or anything else.
I feel the same way. The apps on localhost work, but when I try to expose them using nginx, they only show "loading resources" or "loading configuration" and get stuck.
Describe the bug
When setting
SITE_URL
to something likehttps://myhost.domain.com/infisical
the gui still tries to load ressources fromhttps://myhost.domain.com
e.g.https://myhost.domain.com/images/loading/loading.gif
.My nginx is passing everything to http://localhost:3000 (that's where infisical runs):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Access infisical by subdirectory. Also expect some kind of documentation for using reverse proxies. No info on custom headers (if needed) or anything else.