Possible reasons why cobby cannot establish a secure connection to the service

In rare cases, cobby may not be able to establish a secure connection to the service. Due to specific errors that are not caused by cobby itself, product maintenance can thus be held up.

In this case, you will receive the following message: "Connection to the service failed! No trust relationship could be established for the secure SSL/TLS channel. Possible cause is that you are trying to decrypt the https connection."

Here you can find out what the causes could be.

1. Antivirus program

Check whether an antivirus program is installed and running on your computer. If this is the case, disabling this program may solve the problem. If the message does not appear after that, try to create an exception rule for cobby in the antivirus program using the antivirus user manual or the manufacturer.

2. Firewall

If you use a firewall like Bitdefender or similar, try disabling it and see if the problem persists. If the message does not appear after that, try to create an exception rule for cobby in the firewall using the user manual or the manufacturer.

3. Proxy

If your proxy also handles https connections, this will act as a "man in the middle" attack. Create an exception for *.mash2.com and *.cobby.io domains.

4. Possible “Man in the Middle”

If none of the measures mentioned so far are successful, it is possible that your computer has been infected by an attacker / Trojan. This is also known as "Man in the Middle". In the following article you will learn more about this topic. If you were able to solve your problem, we would be happy to hear from you at info@cobby.io. We may be able to contact the manufacturer directly to have cobby added to a so-called whitelist. This will prevent other users from encountering this problem.