MobileRead Forums - View Single Post - Problems with nginx reverse proxy and calibre

dalibran · 05-07-2025, 01:23 AM

Commenting to close the loop on this for anyone struggling in the future. I was having the same problem, and others were right about the websockets being the issue. In my scenario, I was using caddy as a reverse proxy with the path /calibre/

If you enter the calibre docker container, navigate to app/dist/main.bundle.js. Open the file, search for websockify, and there is some line that sets the default path, looks something like (path, 'websockify'). Change it to (path, 'calibre/websockify') and you won't have to reenter the correct path every time you navigate to the page.

I didn't test, but if your reverse proxy path is different, I imagine you'd have to update that websockify line to whatever you path name is. Also to clarify, this is an issue with KasmVNC and not with calibre server.

05-07-2025, 01:23 AM	#8
dalibran Junior Member Posts: 1 Karma: 10 Join Date: May 2025 Device: Kobo Libra 2	Commenting to close the loop on this for anyone struggling in the future. I was having the same problem, and others were right about the websockets being the issue. In my scenario, I was using caddy as a reverse proxy with the path /calibre/ If you enter the calibre docker container, navigate to app/dist/main.bundle.js. Open the file, search for websockify, and there is some line that sets the default path, looks something like (path, 'websockify'). Change it to (path, 'calibre/websockify') and you won't have to reenter the correct path every time you navigate to the page. I didn't test, but if your reverse proxy path is different, I imagine you'd have to update that websockify line to whatever you path name is. Also to clarify, this is an issue with KasmVNC and not with calibre server.