Closed feldorn closed 1 year ago
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/
The behavior is with the slash. The NGINX proxy rules will rewrite the URL with the trailing slash. I can force it without a slash using the port address (bypassing the reverse proxy), but as stated elsewhere, that gives an error. I'll update the original post to show the slash.
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)
location ^~ /websockify {
# enable the next two lines for http auth
#auth_basic "Restricted";
#auth_basic_user_file /config/nginx/.htpasswd;
# enable for ldap auth (requires ldap-server.conf in the server block)
#include /config/nginx/ldap-location.conf;
# enable for Authelia (requires authelia-server.conf in the server block)
#include /config/nginx/authelia-location.conf;
# enable for Authentik (requires authentik-server.conf in the server block)
#include /config/nginx/authentik-location.conf;
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app calibre;
set $upstream_port 6901;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
proxy_buffering off;
}
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:
location ^~ /calibre-websockify {
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