I recently setup a Cloudflare domain with subdomains, and I’d like to access my Komga instance through Panels for iOS via OPDS this way. I have HTTPS setup properly, have LetsEncrypt providing my certificate, and I’m using nginx-reverse-proxy manager.
The Komga instance is accessible by the web. The OPDS catalog is even accessible by other apps with the HTTPS address. But Panels won’t behave. I either get that “the request timed out” or “too many HTTP redirects” or (I think the closest I’ve come) simply “Realm”. I also have no idea what to be using for my Port number in this example. I know what port from home is exposed to the Internet for Komga, but I don’t think that’s the one that corresponds with Cloudflare’s address.
The formatting I’m using for my OPDS catalog is “https://subdomain.domain.org/opds/v1.2/catalog”. And again, this does load in a web browser.
Can anyone help point me in the right direction here?
I was able to fix this only by uninstalling and reinstalling the Panels for iOS app. Resetting from within the app did not work. Deleting the server and re-adding the settings did not work. But uninstalling the app and reinstalling allowed me to add my Cloudflare address for OPDS. Problem solved.
For future Internet’ers - the way I added my details was that I put in my OPDS https:// address for the host, left the port blank (intentionally), and pre-entered my credentials. That worked.
I’m disappointed that no staff has acknowledged this issue. This is clearly a bug. And I was able to find a work-around, luckily enough. Is anyone here listening?
Our main support channel is our support@panels.app email. If you need assistance, reach out to us by email so we can respond quicker.
About what you described: Panels does not store information about any previous connections, so it’s very strange that only deleting and reinstalling the app would solve the problem.
To investigate an issue like this, we need a way to reproduce it. The best approach is to contact us and provide us with a test account so we can try to reproduce the problem and see what’s going on.
The errors you mentioned are system-level ones. So I assume something was wrong with the network setup.
Let us know if this happens again so we can look into smoothing the configuration process out.
Thanks for responding, it’s much appreciated. I’ll be sure to use the email in the future. And I’ll let you know if the problem re-presents. Although now that it’s working, I don’t think it will.