[BUG] Can’t connect to server on iOS 26.2

[dembala]

I fill in server name correctly with the port and it says “Invalid server information can’t connect to the server”. Same address works for WebGui from Safari on same device and also qbitcontrol works to same server from other Android devices. Here, I’m on iOS 26.2 with an iPhone14PM. Local network access is given in iOS settings.

[Michael-128]

Hi, I think the issue might be caused by the https:// part. Do you see any pop-ups, when opening qBittorrent's WebUI in Safari on your iPhone?

[dembala]

Hello I see others have the same issue on GitHub. In the android client there is an option to trust self signed cert. You are also suggesting this in other threads I see that this could be the root cause. This should be the issue. If I disable trusting self signed cert in the android client it doesn’t work either. So in your app you need to also implement trusting self signed cert. I have a self signed one and I can’t replace it. I believe this is the clue. Regards.

…

On 2025. Dec 30., Tue at 20:06, Michael ***@***.***> wrote: *Michael-128* left a comment (Michael-128/qBitControl#88) <#88 (comment)> Hi, I think the issue might be caused by the https:// part. Do you see any pop-ups, when opening qBittorrent's WebUI in Safari on your iPhone? — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5FBUOX3VIAAT2TRNILO4D4ELEKJAVCNFSM6AAAAACPAKNJZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBQGIYDKOJYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Michael-128]

I have already tried to make the app allow self-signed certificates, but so far I didn't find a solution. If you want to use SSL, you will have to use locally trusted certificate for now. I will release an update, when I find a solution to that problem. Sorry for the inconvenience!

[dembala]

Thanks for your effort appreciated. I think this is a well known issue as other clients have implemented the solution to trust the self signed cert. I hope you also find the clue and we can progress with it. I’ll give a try to avoid secure http and try simple one. Best regards

…

On 2025. Dec 30., Tue at 20:15, Michael ***@***.***> wrote: *Michael-128* left a comment (Michael-128/qBitControl#88) <#88 (comment)> I have already tried to make the app allow self-signed certificates, but so far I didn't find a solution. If you want to use SSL, you will have to use locally trusted certificate for now. I will release an update, when I find a solution to that problem. Sorry for the inconvenience! — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5FBUNIIISC5K2GSUUU2UD4ELFOTAVCNFSM6AAAAACPAKNJZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBQGIZDSMRWGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dembala]

Hello Checked, without https it works fine in plain http. So far it’s good enough for me. Thx.

…

On 2025. Dec 30., Tue at 20:18, Demeter Balazs ***@***.***> wrote: Thanks for your effort appreciated. I think this is a well known issue as other clients have implemented the solution to trust the self signed cert. I hope you also find the clue and we can progress with it. I’ll give a try to avoid secure http and try simple one. Best regards On 2025. Dec 30., Tue at 20:15, Michael ***@***.***> wrote: > *Michael-128* left a comment (Michael-128/qBitControl#88) > <#88 (comment)> > > I have already tried to make the app allow self-signed certificates, but > so far I didn't find a solution. If you want to use SSL, you will have to > use locally trusted certificate for now. I will release an update, when I > find a solution to that problem. Sorry for the inconvenience! > > — > Reply to this email directly, view it on GitHub > <#88 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AD5FBUNIIISC5K2GSUUU2UD4ELFOTAVCNFSM6AAAAACPAKNJZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBQGIZDSMRWGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >