We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ef29a73 created the issue
Dear Dkocher,
Thank you for your email on 3rd November 2011.
Regarding problem for Cyberduck login. I cant not access login cyberduck because it say "Login failed 530 Authentication failed, sorry".
I try double click FTP 213.171.193.5 but show above problem.
Last year, it was work, but it wont work now. I use Apple Mac and and can not access password. I have told my administrator so they cant remember.
Regarding previous email 3rd November,
1)How can I click Status changed from new to closed?
I look at Cyberduck, cant find status, what would I do? Click Cyberduck then preference?
I would be grateful if you could advise.
Kind regards,
Brijesh
Attachments
Login.doc
The text was updated successfully, but these errors were encountered:
@dkocher commented
Please contact your web hosting service provider for assistance.
Sorry, something went wrong.
No branches or pull requests
Dear Dkocher,
Thank you for your email on 3rd November 2011.
Regarding problem for Cyberduck login. I cant not access login cyberduck because it say "Login failed 530 Authentication failed, sorry".
I try double click FTP 213.171.193.5 but show above problem.
Last year, it was work, but it wont work now. I use Apple Mac and and can not access password. I have told my administrator so they cant remember.
Regarding previous email 3rd November,
1)How can I click Status changed from new to closed?
I look at Cyberduck, cant find status, what would I do? Click Cyberduck then preference?
I would be grateful if you could advise.
Kind regards,
Brijesh
Attachments
Login.doc
(31.0 KiB)The text was updated successfully, but these errors were encountered: