This is an extra certificate check introduced in socat version 1.7.3 which is probably the version installed in the clients showing the error. We take care of this in epoptes-client 0.5.8 and later.
Please add our stable PPA to your sources and upgrade epoptes-client on your clients to 0.5.8 https://launchpad.net/~epoptes/+archive/ubuntu/ppa ** Changed in: epoptes Importance: Undecided => Medium ** Changed in: epoptes Status: New => Fix Released -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1518915 Title: E certificate is valid but its commonName does not match hostname Status in Epoptes: Fix Released Bug description: I'm using epoptes-client on a lot of my client machines which are identical. I have successfully received the server certificate. Some of my machines are executing correctly epoptes-client while in other machines I get "E certificate is valid but its commonName does not match hostname" upon epoptes-client execution. All the machines have almost identical network settings (successive static IPs & hostnames and customized /etc/default/epoptes-client file). To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1518915/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
