-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
[BUG] Calibre in a SubFolder w/ Reverse Proxy not working #129
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
does it work with the trailing slash entered ? IE http://www.domain.com/calibre/ |
So I have a solution, you can add the following to your reverse proxy conf: (this is just drop in see my notes below about collision with other apps)
This will work, but only for one GUI app, so if you are running anything else off of this base would need a unique path like:
If the path is modified from that websockify path then on your client need to modify the connection settings in the sidebar: I'll get a PR for our example proxy confs with the drop in so people in the future don't run into this. |
I can confirm this solution works. I also include authentication (Organizr) w/in the Reverse Proxy configuration and that isn't causing any issues either. I don't have another GUI in the container, so I've not tested modifying the path.
I appreciate the fast turn around on this! |
Is there an existing issue for this?
Current Behavior
Calibre is configured to use a subfolder and is sitting behind SWAG/NGINX. The configuration worked on the prior version, but with KasmVNC produces the error message below.
Configurations Tested:
I can launch the URL for /calibre/vnc/dist/main.bundle.js and it is visible to the browser.
Swag NGINX Reverse Proxy is configured per the latest SWAG sample file.
Expected Behavior
Ability to Launch Calibre using an url with a subfolder:
Example: https://www.domain.com/calibre/
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: