Closed skooj closed 7 months ago
Thanks for finding, reporting and the workaround.
I'll have a patch soon
I'm holding off doing another proper release just yet, though I'm sure there will be one within a week or so.
GitHub should build a new staging image for docker tonight which should resolve this.
Thank you for the quick fix!
Describe the bug I am, and have been, using an Apache2 reverse proxy to access this, following the configuration in the documentation. This worked fine prior to updating to 3.0.2, but now I'm getting a white screen. The app loads as expected when connecting to the port directly.
In dev tools, I am getting the errors:
This indicates that /assets/ is not being put behind /scanner/assets as expected. I believe this is a similar issue to #250 which looks like it was maybe fixed with #266
To Reproduce Steps to reproduce the behavior:
Expected behavior /assets/ would be proxied like everything else.
Client (please complete the following information):
Server (please complete the following information):
Logs
Additional context My apache config:
I have docker forwarding the port 8088 to 8080 instead, because I use 8080 for other things. I have temporarily moved it to 8080 (and updated the config) to see if this fixed the issue, but it did not. Again, this was functioning in the 2.x version, but not since updating to 3.x
Edit: adding the following inside allows it to work, but is likely not what is expected by the project: