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

Incompatibility with Akamai Content Storage #5185

Closed
cyberduck opened this issue Sep 13, 2010 · 6 comments
Closed

Incompatibility with Akamai Content Storage #5185

cyberduck opened this issue Sep 13, 2010 · 6 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 13, 2010

ee41874 created the issue

I'm unable to upload or download files since upgrading to 3.6.1. I can see all my files and folders, but I get transfer incomplete messages when trying to use them. I've never had a problem before and used the last version without issue. HELP! I use cyberduck everyday!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 14, 2010

99a4d6b commented

I am having the same issue. Can anyone help out? I am falling behind by not being able to download files. Thank you for your help!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 14, 2010

@dkocher commented

Post the transcript from the log drawer.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 15, 2010

cdcf58d commented

Replying to [comment:2 dkocher]:

Post the transcript from the log drawer.

I have similar problems in that my transfers intermittently fail. My log drawer remains empty even when there is an error. Cyberduck also disconnects after each successful or unsuccessful transfer unless I set the preferences to transfer files using a new connection, which is much slower. Disconnection occurs after a brief color wheel. Cyberduck 3.6.1 is also slow in recognizing drag-and-drop events from CD to Finder, but not the other way around.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 15, 2010

99a4d6b commented

Replying to [comment:2 dkocher]:

Post the transcript from the log drawer.

220 Akamai Content Storage FTP Server
AUTH TLS
234 AUTH TLS successful
USER maxpreps_intern
331 Password required for maxpreps_intern.
PASS ********
230 User maxpreps_intern logged in.
PBSZ 0
200 PBSZ 0 successful
PROT P
200 Protection set to Private
FEAT
211-Features:
 MDTM
 REST STREAM
 SIZE
 AUTH TLS
 PBSZ
 PROT
211 End
CWD /shardy
250 CWD command successful.
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (72,246,193,25,219,127).
PORT 129,228,208,112,223,232
200 PORT command successful
RETR charonpeake.mov
QUIT
220 Akamai Content Storage FTP Server
AUTH TLS
234 AUTH TLS successful
USER maxpreps_intern
331 Password required for maxpreps_intern.
PASS ********
230 User maxpreps_intern logged in.
PBSZ 0
200 PBSZ 0 successful
PROT P
200 Protection set to Private
FEAT
211-Features:
 MDTM
 REST STREAM
 SIZE
 AUTH TLS
 PBSZ
 PROT
211 End
CWD /shardy
250 CWD command successful.
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (72,246,193,16,211,145).
PORT 129,228,208,112,224,0
200 PORT command successful
RETR charonpeake.mov
QUIT

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 16, 2010

@dkocher commented

Replying to [comment:4 https://www.google.com/accounts/o8/id?id=aitoawnzxrg0ismiev-pzjlxzx0xuq51y0jgiqm]:

Replying to [comment:2 dkocher]:
PASV
227 Entering Passive Mode (72,246,193,25,219,127).
PORT 129,228,208,112,223,232
200 PORT command successful
RETR charonpeake.mov
QUIT
}}}

From the transcript it looks like there was an error connecting to 72.246.193.16 on port 54161. I then falls back to active connect mode but that fails, too.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 26, 2010

@dkocher commented

The original issue is possibly a duplicate for #5087. But the transcript from connecting to Akamai looks like another issue.

@cyberduck cyberduck closed this Nov 19, 2010
@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
1 participant