New iPad - Komga Connection Issue

Hi, I got a new iPad Mini today and I’m having some issues setting up my Komga library on it.

When I freshly install Panels and enter my Komga connection details it accepts the information and I can see the successful authentication from Panels (Panels/721 CFNetwork/1498.700.2 Darwin/23.6.0) in my Komga logs however, when I then try to browse the library in Panels I get a connection error. If I then try to edit the connection info in Panels and save it I get the below error.

If I then delete the connection and try to re-add it with the exact same information that was previously accepted I get the same error. The only way I can get it to re-accept that connection is to delete the app and reinstall it. Even doing the factory reset through settings doesn’t let me re-add it without getting that error.

In testing however, when I try the connection outside my network (tethering my phone) it all works fine.

The connection works fine on my iPad Pro and old Mini when on my network. The only difference with them is they are still on iOS 17.

Any help would be greatly appreciated I really don’t know what to do to get it working!

Thanks

I just updated my iPad Pro to test and now that no longer works and is acting exactly the same as my new mini. It seems to be an issue on iOS18.

Also tried Kavita and is exactly the same. Works fine on iOS17 devices but not on iOS18 devices.

Weird. It’s working fine for me on iOS 18 :thinking:

Can you share exactly what version of iOS 18 you have installed? I’ll try to reproduce that scenario.

Thanks. I’m running iPadOS 18.0.1.

I’ve done some more messing around this morning. I was previously using No-IP dyanmic DNS and their Dynamic Update Client to get around my lack of static IP.

To test today though I simplified it a bit and just pointed a subdomain to my current IP to test and still have the same issue.

I am using Caddy for the SSL cert and current address I am testing with is https://komga3.penguintri.co.uk/ which seems to work everywhere else.

Would you be open to creating a test account for us on your server?

If so, drop me a DM with the credentials. That would make the debugging much easier in case is related to your setup. Maybe there’s something we are missing or not handling correctly on our end, and it would be amazing if we could replicate your exact scenario.

We don’t need to have access to your content. If you create an account and simply authorize one comic/series so the feeds are not empty, that would be more than enough.

Yea sure, I’ll DM you on the details now.

Thanks for helping look into this might be difficult to troubleshoot as it all works fine when I connect remotely (tethering my phone) just doesn’t when on the same network as the server.

Ohhh interesting :thinking:

Yeah, that must be some NAT configuration or something like that.

I’ll try the credentials you sent me :pray: , but based on that information, it’s very likely I won’t have any problems connecting, because, obviously, I’m out of your local network.

I’m not an expert in networking. I’m unsure if I’ll be able to help much resolve that issue if the problem is in the NAT setup.
But I have a Komga server running on a mac mini in my network, and a Caddy server that handles the reverse proxy and SSL certificate renewal automatically.

I set it up using Komga’s guide Expose your server | Komga

Yep, I can access it with no problem. Using any of the two domains you sent me.

Probably there’s an issue in the local name resolution inside your local network, and it can’t access the server. I’m quite bad with this kind of stuff, sorry I can’t help much.
But I’m certain there’s no problem with your Komga server, or Panels. It’s a networking issue, most likely related to DNS resolution + NAT.

Thanks for looking. It seems that something has changed from iOS17 to iOS 18 that doesn’t agree with my network.

I just tried adding my Komga library to another OPDS reader I found (Yomu) and I’m experiencing the same issue on that. Works fine on iOS17 but on iOS18 the library will add ok but then fail to connect unless it’s remote.

I’ll try reading into DNS and NAT but getting way outside of my network understanding haha!

After all my troubleshooting in vain, it turns out it must have been an iOS bug. It’s all fixed and working fine in iOS 18.1, that’s just been released today.

Amazing! thanks for letting us know. I’m glad Apple fixed it.