Replies: 1 comment 1 reply
-
Thank you for opening an issue. Since this is a configuration problem on your end, I've converted it to a Q&A discussion. Please set |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Support guidelines
I've found a bug and checked that ...
Description
I'm trying to setup Firefly III to run in Docker behind an nginx instance running on the host.
This is the intended flow:
web browser <--- port 443, TLS ---> nginx <--- port 8051 on host, 8080 in container ---> Firefly III
Here's the pertinent info from the systemd service I created. NOTE: throughout I will use "https://my.url.com" as the intended external URL. This obviously isn't the actual URL I'm using. I don't wish to share that publicly, but it's a standard .com domain and I have a TLS certificate from LetsEncrypt. The DNS and TLS settings appear to work fine so I think are outside the scope of this issue.
I can browse to http://my.url.com:8051 and access the site over regular HTTP. (Eventually I will try to disable this so all requests must go through nginx, but it's useful for testing.) However, if I go to https://my.url.com, I see a website with no styles or javascript. Looking at the firefox console, I see that the website is trying to load stuff from http://my.url.com.
For example:
It should be loading it from "https://my.url.com/build/assets/dashboard-BZG_lvWP.js" but it's not. Presumably because the proxy connection is regular HTTP, the web service assumes all generated URLs should use that scheme as well, but that's not the case.
This could be a case of simply missing a configuration option, although I looked through the entire example .env file and didn't see anything like an external URL setting. The closest was APP_URL but I think that is only used in some contexts.
Is there a way for me to get Firefly III to generate URLs (ie for page assets, javascript + styles) using a specific protocol? Maybe a header I can set from nginx?
For completeness, here's the relevant nginx config. The nginx TLS config seems to work fine, and the right certificate is served when browsing there.
Debug information
Debug information generated at 2024-09-01 11:11:21 for Firefly III version v6.1.19.
en_US.UTF-8: ✅
Expected behaviour
No response
Steps to reproduce
No response
Additional info
No response
Beta Was this translation helpful? Give feedback.
All reactions