Revision history [back]

I have been using dukgo.com XMPP-server for about a year now without big problems. I haven’t had "ignore SSL errors" checked before. Now I have to have it checked for my account to connect. I tested it using mc-tool on terminal.

The current certificate for duck.co seems to have been issued on December 2nd. That’s about the same time when my problems started.

The question is: Is the new certificate untrusted on Jolla and why?

Sorry. I’m a newbie when it comes to SSL certificates.

Are there some workarounds for adding that certificate myself? I feel that it’s unsecure to ignore all SSL errors.

I have been using dukgo.com XMPP-server for about a year now without big problems. I haven’t had "ignore SSL errors" checked before. Now I have to have it checked for my account to connect. I tested it using mc-tool on terminal.

The current certificate for duck.co seems to have been issued on December 2nd. That’s about the same time when my problems started.

The question is: Is the new certificate untrusted on Jolla and why?

Sorry. I’m a newbie when it comes to SSL certificates.

Are there some workarounds for adding that certificate myself? I feel that it’s unsecure to ignore all SSL errors.

I have been using dukgo.com XMPP-server for about a year now without big problems. I haven’t had "ignore SSL errors" checked before. Now I have to have it checked for my account to connect. I tested it using mc-tool on terminal.terminal. More about that here.

The current certificate for duck.co seems to have been issued on December 2nd. That’s about the same time when my problems started.

The question is: Is the new certificate untrusted on Jolla and why?

Sorry. I’m a newbie when it comes to SSL certificates.

Are there some workarounds for adding that certificate myself? I feel that it’s unsecure to ignore all SSL errors.

The same account works without any problems on my PC with KDE Telepathy.