-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forward proxy setup #520
Comments
@den5o It would be ideal to watch the actual app error log to understand what error is actually occurring. I have not tested it, but I think for this kind of compose setup the logs could usually be read via: docker compose exec bookstack tail -f /var/www/bookstack/storage/logs/laravel.log Not sure about podman though. |
@ssddanbrown thanks for the suggestion. Here is the output of
|
Could it be my use of podman secrets that is causing those cipher errors? The database env vars also use secrets and boostack establishes a connection to it.
|
I tried it without secrets and the log remains the same |
So I got it working. I made a few mistakes in my compose. It should have worked the first time I tried it without secrets but I may have missed a step in resetting the config.
Is there any chance of adding support for secrets in the future? |
I have traefik running on a VPS listening on
mydomain.tld
and managing all certs. The VPS and a VM running on my home server are connected via NetBird. The VPS forward proxies all incoming requests tosubdomain.mydomain.tld
and*.subdomain.mydomain.tld
to the VMs NetBird IP where NPM reverse proxies them to the correct service.I have a few services running on the VM being served this way.
books.subdomain.mydomain.tld
files.subdomain.mydomain.tld
baikal.subdomain.mydomain.tld
music.subdomain.mydomain.tld
SFTPgo, Baikal, and Navidrome work without issue. Bookstack results in status code 500
strict-origin-when-cross-origin
As you can see in the compose file below I've included
- APP_PROXIES=*
. I also tried the VPS NetBird IP with the same result. I've also experimented with traefik headers with no success for a few days now. The config below does not include any of those as I've scrapped them.I thought I'd post this issue here instead of traefik because I believe the
APP_PROXIES
environment variable should have taken care of this. Let me know if this would be more appropriate for traefik support.Boockstack podman-compose.yml:
Traefik labels:
Traefik static config:
NPM:
Screenshot:
Status code:
Bookstack log:
The text was updated successfully, but these errors were encountered: