Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interoperability failure unrecoginzed_name when connecting to Synology Webdav server #9575

Closed
cyberduck opened this issue Jun 1, 2016 · 5 comments
Assignees
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

ce8af5d created the issue

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 and

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

@cyberduck
Copy link
Collaborator Author

ce8af5d commented

Updated to CyberDuck 5.0 and have the same problem

@cyberduck
Copy link
Collaborator Author

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

ce8af5d commented

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>

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:6 fjanvier]:

Thanks for adding the sample configuration!

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants