I have the following setup for my komga server:
The server is running locally with the default config (that is on IP:25600 locally), but because I have other services running on my homelab, and I only want port 80 and 443 exposed to the outside, I cannot reach it directly using my public ip address. Instead I have caddy set up to redirect the komga.host.ddns.net subdomain to the correct internal IP, so I can reach it from everywhere. This works as expected when using the web interface, but with the current 0.18.5 version on android, I get issues with most requests to the server.
I can log in as usual (using the komga.host.ddns.net domain), and komelia does correctly load my list of libraries in the sidebar. But if I try to actually load a library I always get an error Permanent Redirect and instead of showing anything, the app simply shows the error
Unhandled redirect: POST url Status 308 Permanent Redirect Text: ""
I'm running komga on 1.24.4 and caddy 2.11.2. There also should not be any issues with the caddy configuration as all other services, as well as komga when not using the komelia app, are working
I have the following setup for my komga server:
The server is running locally with the default config (that is on IP:25600 locally), but because I have other services running on my homelab, and I only want port 80 and 443 exposed to the outside, I cannot reach it directly using my public ip address. Instead I have caddy set up to redirect the
komga.host.ddns.netsubdomain to the correct internal IP, so I can reach it from everywhere. This works as expected when using the web interface, but with the current 0.18.5 version on android, I get issues with most requests to the server.I can log in as usual (using the
komga.host.ddns.netdomain), and komelia does correctly load my list of libraries in the sidebar. But if I try to actually load a library I always get an errorPermanent Redirectand instead of showing anything, the app simply shows the errorUnhandled redirect: POST url Status 308 Permanent Redirect Text: ""I'm running komga on 1.24.4 and caddy 2.11.2. There also should not be any issues with the caddy configuration as all other services, as well as komga when not using the komelia app, are working