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

FTP Connections not working through proxy when "Use system proxy settings" checked #9010

Closed
cyberduck opened this issue Sep 10, 2015 · 10 comments
Closed

FTP Connections not working through proxy when "Use system proxy settings" checked #9010

cyberduck opened this issue Sep 10, 2015 · 10 comments
Labels
bug core worksforme

Comments

@cyberduck
Copy link
Collaborator

a4e743b created the issue

In a proxied environment, checking "Use system proxy settings" causes FTP connections to fail. Unchecking the checkbox in a proxied environment, it connects just fine.

All of this is being observed on a MacBook Pro 15" running OS X 10.10.5, tested when I'm at work (proxied environment) and at home (no proxies needed). The proxies are set either via a PAC file or statically (no authentication required, PASV always enabled).

Screen Shot 2015-09-10 at 2.03.38 PM.png

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the error message and the transcript from View → Log Drawer.

@cyberduck
Copy link
Collaborator Author

a4e743b commented

When "Use system proxy settings" checkbox is checked, attempting to connect shows no log trace. Also, at the end, there is the "Try again" / "Cancel" / "Network Diagnostics" dialog. Clicking on "Network Diagnostics" dismisses the dialog but Network Diagnostics is not launched.

When "Use system proxy settings" checkbox is unchecked, attempting to connect shows the expected log trace.

Attached are 2 screen capture movies: one of a failure, and the other of a successful connection:

https://trac.cyberduck.io/attachment/ticket/9010/Cyberduck-use-system-proxies-checked-connection-failure.m4v
https://trac.cyberduck.io/attachment/ticket/9010/Cyberduck-use-system-proxies-unchecked-connection-success.m4v

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The error Read timed out indicates that the proxy server is not responding. Are you sure the proxy configuration is valid? Please post the settings from System Preferences → Network → Advanced… → Proxies.

@cyberduck
Copy link
Collaborator Author

a4e743b commented

It turns out that having an FTP proxy configured is no longer needed when on the HP Intranet. But having the "FTP" proxy checkbox in the Proxies tab of the network adapter's Advanced settings checked or unchecked, the behavior observed in Cyberduck is the same.

I did just try unchecking SOCKS, and when that is unchecked then Cyberduck will connect. So I guess Cyberduck is failing over to using SOCKS, and that is causing the issue.

I still don't understand why unchecking the Cyberduck preference for "Use system proxy settings" doesn't let me manually set proxy settings in Cyberduck. (I can file a separate ticket for this if needed.

@cyberduck
Copy link
Collaborator Author

a4e743b commented

That resolution is pretty disappointing.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:5 ducklips]:

It turns out that having an FTP proxy configured is no longer needed when on the HP Intranet. But having the "FTP" proxy checkbox in the Proxies tab of the network adapter's Advanced settings checked or unchecked, the behavior observed in Cyberduck is the same.

I did just try unchecking SOCKS, and when that is unchecked then Cyberduck will connect. So I guess Cyberduck is failing over to using SOCKS, and that is causing the issue.

I still don't understand why unchecking the Cyberduck preference for "Use system proxy settings" doesn't let me manually set proxy settings in Cyberduck. (I can file a separate ticket for this if needed.

Do you imply that we should ignore the SOCKS proxy setting for FTP connections?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:7 ducklips]:

That resolution is pretty disappointing.
We have closed this issue with the understanding that the proxy settings in System Preferences are no longer valid and should be updated.

@cyberduck
Copy link
Collaborator Author

a4e743b commented

Replying to [comment:8 dkocher]:

Replying to [comment:5 ducklips]:

It turns out that having an FTP proxy configured is no longer needed when on the HP Intranet. But having the "FTP" proxy checkbox in the Proxies tab of the network adapter's Advanced settings checked or unchecked, the behavior observed in Cyberduck is the same.

I did just try unchecking SOCKS, and when that is unchecked then Cyberduck will connect. So I guess Cyberduck is failing over to using SOCKS, and that is causing the issue.

I still don't understand why unchecking the Cyberduck preference for "Use system proxy settings" doesn't let me manually set proxy settings in Cyberduck. (I can file a separate ticket for this if needed.

Do you imply that we should ignore the SOCKS proxy setting for FTP connections?

I'm not sure how you might want to handle the condition where the FTP proxy is not enabled but the SOCKS proxy is configured and enabled. It seems like an odd and probably annoying corner case. I suppose you could try direct connection first and then try SOCKS or the other way around in any retries.

Perhaps I should let this one go. But I'm going to file a separate ticket for the issue that when "Use system proxy settings" is unchecked, there seems to be no UI presented by Cyberduck to locally configure its own proxy settings.

@cyberduck
Copy link
Collaborator Author

a4e743b commented

Replying to [comment:9 dkocher]:

Replying to [comment:7 ducklips]:

That resolution is pretty disappointing.
We have closed this issue with the understanding that the proxy settings in System Preferences are no longer valid and should be updated.

Actually the change in my own system settings is that FTP connections no longer require connecting through a proxy server (FTP or SOCKS) - direct connections are the IT supported connection method.

@cyberduck
Copy link
Collaborator Author

a4e743b commented

Replying to [comment:10 ducklips]:

Replying to [comment:8 dkocher]:

Replying to [comment:5 ducklips]:

It turns out that having an FTP proxy configured is no longer needed when on the HP Intranet. But having the "FTP" proxy checkbox in the Proxies tab of the network adapter's Advanced settings checked or unchecked, the behavior observed in Cyberduck is the same.

I did just try unchecking SOCKS, and when that is unchecked then Cyberduck will connect. So I guess Cyberduck is failing over to using SOCKS, and that is causing the issue.

I still don't understand why unchecking the Cyberduck preference for "Use system proxy settings" doesn't let me manually set proxy settings in Cyberduck. (I can file a separate ticket for this if needed.

Do you imply that we should ignore the SOCKS proxy setting for FTP connections?

I'm not sure how you might want to handle the condition where the FTP proxy is not enabled but the SOCKS proxy is configured and enabled. It seems like an odd and probably annoying corner case. I suppose you could try direct connection first and then try SOCKS or the other way around in any retries.

Perhaps I should let this one go. But I'm going to file a separate ticket for the issue that when "Use system proxy settings" is unchecked, there seems to be no UI presented by Cyberduck to locally configure its own proxy settings.

New ticket for Cyberduck native proxy settings UI issue: https://trac.cyberduck.io/ticket/9018

@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
No one assigned
Labels
bug core worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck