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
Cannot connect to Eucalyptus Community Cloud - I/O Error : Connection Failed #6207
Comments
I can replicate the issue here. I haven't looked into it closely yet but it looks like a SSL negogiation issue. |
Replying to [comment:2 dkocher]:
Sorry, that information is wrong. I was attempting to connect to port |
Keep in mind that the Eucalyptus Cloud Web Interface is often run on port 8443, but the Eucalyptus Walrus server is often on port 8773. One "enhancement" I saw to make in CyberDuck is that when you create a new Walrus endpoint, Cyberduck uses a default port of 8443, which is actually confusing since it should be 8773 since that's the usual default port for Eucalyptus Walrus. |
Replying to [comment:5 chimpeenuts]:
Default port changed in 9bc8a19. |
A new snapshot build with the fix included will be available in a few minutes. |
Trying to connect to Eucalyptus' community cloud Walrus service.
Community URL: (https://ecc.eucalyptus.com:8443/)
Was able to connect with JetS3t's Cockpit (same system), upload a file, and create the following public URL for an item: (http://ecc.eucalyptus.com:8773/services/Walrus/chimpeenuts-bucket/Argentina.gif)
UPDATE: Can get CloudBerry Explorer LITE on Windows to connect to community cloud.
See attached screenshot for connection settings and specified Query ID and Secret Key.
When I try to connect I get error: 'I/O Error: Connection failed - Unrecognized SSL message, plaintext connection?" with an option to Cancel or Try Again. Clicking Try Again brings up the same error message. (see attached screenshot)
When I click on the URL (with no username or secret key) inside the connection window, I get an error message indicating 'no such user' but this is expected (since I'm not supplying any user credentials) and GOOD because means I'm reaching the service and it does indeed exist:
Attachments
Screen shot 2011-09-07 at 10.21.02 AM.png
(59.8 KiB)Screen shot 2011-09-07 at 10.21.24 AM.png
(40.4 KiB)Screen shot 2011-09-07 at 10.21.29 AM.png
(27.0 KiB)The text was updated successfully, but these errors were encountered: