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

Bonjour list doesn't use advertised name and path for SFTP #6975

Closed
cyberduck opened this issue Nov 29, 2012 · 4 comments
Closed

Bonjour list doesn't use advertised name and path for SFTP #6975

cyberduck opened this issue Nov 29, 2012 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Nov 29, 2012

Craig McQueen created the issue

I have an SFTP server that is advertising on Zeroconf. It advertises a particular path on the server. I can connect to the server, but it doesn't use the advertised path. It tries to connect to /home/ instead.

Also, the server is advertised multiple times, with different Zeroconf names and paths (e.g. "Server WWW" with path /var/www, and "Server" with path /). The Bonjour list doesn't show the names or the paths, so it looks as though the same server is just showing up multiple times in the list.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 29, 2012

Craig McQueen commented

Actually I just realised it's displaying the URL as sftp://hostname/System.Byte[]. I guess that's a bug.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 29, 2012

@dkocher commented

Can you verify the the TXT record included is correct. You can also enable debug logging in Cyberduck which will print the TXT record to the system.log.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 29, 2012

@dkocher commented

Please specify the operating system you run Cyberduck on Platform.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 11, 2012

@ylangisc commented

In a115526.

@cyberduck cyberduck closed this Dec 11, 2012
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants