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

Jump to bottom

Attempt to set invalid working directory after failed connection attempt #7923

Closed
cyberduck opened this issue May 1, 2014 · 5 comments
Closed

Attempt to set invalid working directory after failed connection attempt #7923

cyberduck opened this issue May 1, 2014 · 5 comments
Assignees
@ylangisc
Labels
bug core worksforme
Milestone
4.4.5

Comments

@cyberduck
Copy link
Collaborator

f411c1e created the issue

I was on an original ftp site, in a folder called /missionbeach, where everything worked fine.

I then used the Bookmarks button to change to a different ftp site. This authenticated and tried to open, but then gave me an error alert, complaining that /missionbeach was not a valid folder name on the new site.

After I accepted the error alert, then the proper ftp site opened uneventfully, at its root level as it should.

I haven't seen this before, often enough switching ftp sites this way, so probably you have a regression here.

Other things have cleaned up without being listed, so I think you are on a good path for another release version here. I enjoy CyberDuck a lot, not least for its name ;)

This is actually on 4.5, just downloaded, so I noted as Nightly Build in your form here, since 4.5 hasn't made it into the dropdown.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot replicate this problem.

@cyberduck
Copy link
Collaborator Author

f411c1e commented

Ok, I lost my message in attaching a picture of the problem, so once again briefly:

  • at first I could not duplicate either. But it happened.
  • it may be significant that I have different kinds of secure ftp between the two sites: one is sftp, and the other ftps - FTP-SSL, and I think explicit.
  • I got Cyberduck pretty confused switching between sites and testing, when one of the sites wouldn't answer because of a CloudFlare DNS change.
  • finally it recovered, and I looked at the ftps site, where the /missionbeach directory exists
  • then I clicked the tiny icon to see bookmarks, and double-clicked on the sftp site.
  • in the attached png, you can see the fail alert with its details.
  • accepting the alert, then everything proceeds and works fine as far as I know.

it's late here, so hope I am clear, and grüss...

@cyberduck
Copy link
Collaborator Author

f411c1e commented

Yes, actually it's Windows 8.1, all latest updates.

Sorry if I missed where to say that...

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Added test in 2da65b1.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We have been unable to replicate this issue.

@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.
Assignees

@ylangisc ylangisc

Labels
bug core worksforme
Projects
None yet
Milestone
4.4.5
Development

No branches or pull requests
2 participants
@ylangisc @cyberduck