Cyberduck Mountain Duck CLI

#9575 closed defect (thirdparty)

Interoperability failure unrecoginzed_name when connecting to Synology Webdav server

Reported by: fjanvier Owned by: dkocher
Priority: normal Milestone:
Component: webdav Version: 4.9.3
Severity: normal Keywords:
Cc: Architecture: Intel
Platform: Windows 10

Description

Impossible to connect to our Webdav server using https and a dedicated port. I receive a Windows system error message : "Echec d'interoperabilité"

Related information :

  • Our certificate is a valid LetsEncrypt certificate.
  • Expandrive and NetDrive are connecting successfuly.
  • Also occurs on Windows 7

Extract from the MountainDuck log file. Note: I replaced login and server information by <MYLOGIN> and <MYSERVER>

2016-06-01 12:15:43,200 [Thread-1] INFO  ch.iterate.mountainduck.fs.PooledSessionFilesystem - Create new session for host Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs} in pool SessionPool{host=Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs}}
2016-06-01 12:15:43,209 [Thread-1] INFO  ch.iterate.mountainduck.fs.PooledSessionFilesystem - Borrow session Session{host=Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs}, state=closed} from pool GenericObjectPool{configuration=GenericObjectPoolConfig{maxTotal=2147483647, maxIdle=5}, numActive=1, numIdle=0}
2016-06-01 12:15:43,215 [Thread-1] INFO  ch.iterate.mountainduck.fs.PooledSessionFilesystem - Release session Session{host=Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs}, state=closed} to pool GenericObjectPool{configuration=GenericObjectPoolConfig{maxTotal=2147483647, maxIdle=5}, numActive=1, numIdle=0}
2016-06-01 12:15:43,215 [background-3] INFO  ch.iterate.mountainduck.fs.FilesystemMountRegistry - Mount bookmark Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs} with in Local{path='I:\'}
2016-06-01 12:15:43,351 [Thread-12] WARN  ch.iterate.mountainduck.fs.SessionFilesystem - Finalize file system callback SessionFilesystem{bookmark=Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs}, autoClose=false, controller=ch.iterate.mountainduck.fs.FilesystemController@24d63b}
2016-06-01 12:15:43,793 [background-3] INFO  ch.iterate.mountainduck.fs.FilesystemMountRegistry - Unmount bookmark Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs} in SessionFilesystem{bookmark=Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs}, autoClose=false, controller=ch.iterate.mountainduck.fs.FilesystemController@11f5d99}
2016-06-01 12:15:43,820 [background-3] WARN  ch.iterate.mountainduck.fs.FilesystemMountRegistry - Failed to remove Host{credentials=Credentials{user='<MYLOGIN>'}, hostname='<MYSERVER>', defaultpath='Users', port=5006, protocol=davs} from registry

Attachments (1)

2016-06-01 12_15_52-Erreur.png (6.1 KB) - added by fjanvier on Jun 1, 2016 at 10:30:01 AM.
Displayed error message

Download all attachments as: .zip

Change History (8)

Changed on Jun 1, 2016 at 10:30:01 AM by fjanvier

Displayed error message

comment:1 Changed on Jun 1, 2016 at 10:38:34 AM by fjanvier

  • Version changed from 5.0 to 4.9.3

comment:2 Changed on Jun 1, 2016 at 10:40:50 AM by fjanvier

Updated to CyberDuck 5.0 and have the same problem

comment:3 Changed on Jun 1, 2016 at 11:25:56 AM by dkocher

  • Summary changed from Cannot connect to our Synology Webdav server using CyberDuck nor MountainDuck to Interoperability failure unrecoginzed_name when connecting to Synology Webdav server

comment:5 Changed on Jun 1, 2016 at 11:28:24 AM by dkocher

  • Resolution set to thirdparty
  • Status changed from new to closed

Duplicate for #7908. Please fix the server configuration following the instructions in the above link.

comment:6 follow-up: Changed on Jun 1, 2016 at 2:37:43 PM by fjanvier

As Expandrive and NetDrive have found a workaround to handle the problem silently, I suggest you to either use a similar workaround or advise users.

For the FAQ : Synology WebDAV are "by default" configured without specifying any ServerAlias. To solve this issue : Edit file /var/packages/WebDAVServer/target/etc/httpd/conf/extra/httpd-ssl.conf-webdav

And add a ServerAlias my.certifdicate.name line using your domain certificate or a generic ServerAlias *

As an example, should look like :

<VirtualHost *:5006>
    ServerAlias my.certificate.name
    SSLEngine on

    <FilesMatch "\.(cgi|shtml|phtml|php)$">
        SSLOptions +StdEnvVars
    </FilesMatch>

    BrowserMatch ".*MSIE [2-5]\..*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
    CustomLog /dev/null "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</VirtualHost>

comment:7 in reply to: ↑ 6 Changed on Jun 1, 2016 at 2:43:27 PM by dkocher

Replying to fjanvier:

Thanks for adding the sample configuration!

Note: See TracTickets for help on using tickets.
swiss made software