You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Cyberduck with WebDAV (HTTP/SSL) protocol. Our server's hostname is "webdav.data.donders.ru.nl", and it has a valid certificate issued by a trusted CA. It has been working properly with Cyberduck 4.7.3, but since we upgrade to version 4.8.3, we encountered a failure during certificate trust verification. After some tests, we noticed that the same issue has been presented since version 4.8.
The error says that I might connect to a server pretending to be "data.donders.ru.nl". This is weird because we do connect to server "webdav.data.donders.ru.nl", and the server is totally independent to "data.donders.ru.nl" (in terms of DNS registry, in Web server configuration, and in certificate chain). We don't understand from where the "data.donders.ru.nl" is determined by the verification.
With a bit search in the existing tickets, I guess it might be something related to the fix of the ticket #3813.
Attached please find the screenshot of the error. Could you please help? Thank you very much in advance.
Dear developers,
We are using Cyberduck with WebDAV (HTTP/SSL) protocol. Our server's hostname is "webdav.data.donders.ru.nl", and it has a valid certificate issued by a trusted CA. It has been working properly with Cyberduck 4.7.3, but since we upgrade to version 4.8.3, we encountered a failure during certificate trust verification. After some tests, we noticed that the same issue has been presented since version 4.8.
The error says that I might connect to a server pretending to be "data.donders.ru.nl". This is weird because we do connect to server "webdav.data.donders.ru.nl", and the server is totally independent to "data.donders.ru.nl" (in terms of DNS registry, in Web server configuration, and in certificate chain). We don't understand from where the "data.donders.ru.nl" is determined by the verification.
With a bit search in the existing tickets, I guess it might be something related to the fix of the ticket #3813.
Attached please find the screenshot of the error. Could you please help? Thank you very much in advance.
Cheers, Hong
Attachments
Screen Shot 2016-03-10 at 09.10.03.png
(366.3 KiB)The text was updated successfully, but these errors were encountered: