FTP not connecting via cellular hotspot

[Kirk Baker]

Jenny,

No settings changed from last FTP session, I used the hotspot and everything worked ok. 29 photos uploaded, no errors.

- I guess the passive setting does the trick. Originally Alamy would only work with active FTP. But uploading was flakey then, I guess they fixed their server.
- Now that I’ve verified the hotspot works, it’s all about the VPN. If Alamy used SFTP it wouldn’t be a problem.

So, what would be the best way to further test this?

We're going to run a trial version of Tunnel Bear and see if we can find out why PM can't create the socket at the IP/port that the server tells PM to connect to.

-Kirk

[Kirk Baker]

Jenny,

We installed and activated TunnelBear on one of our development systems and then proceeded to upload to one of our FTP servers without issue.

Have you tried changing which "tunnel" that TunnelBear uses to provide your VPN?  We left the setting as "Closest Tunnel" and it ended up choosing a server in Mexico.

If changing tunnels doesn't make any difference, then we'd like to see some logs from the other FTP client software you mentioned that was able to send files to Alamy over the TunnelBear VPN.

We would like to see the FTP commands and responses between that client and the server to see how and if they differ from PM.

Thanks,

-Kirk

[Jen Mack]

Ok, it might be few days.

[Jen Mack]

Ok, so it’s still acting up. After a failed upload, I checked my Tunnelbear settings and had TCP override & Ghostbear checked. I turned those off, so the only thing active was Vigilant. Still no upload. I tried closest tunnel and UK.

While the upload was stalled, I opened terminal and checked that manual FTP worked. It did. Here’s the session:
$ ftp upload.alamy.com
Connected to upload.alamy.com.
220 Microsoft FTP Service
Name (upload.alamy.com:jenn): email@isp.com
331 Password required for email@isp.com.
Password: ****
230 User logged in.
Remote system type is Windows_NT.
ftp> cd Stock
250 CWD command successful.
ftp> pwd
Remote directory: /Stock
ftp> exit
221 Goodbye.

This was from my home wifi. I’ve sent the log.

[Kirk Baker]

Ok, so it’s still acting up. After a failed upload, I checked my Tunnelbear settings and had TCP override & Ghostbear checked. I turned those off, so the only thing active was Vigilant. Still no upload. I tried closest tunnel and UK.

While the upload was stalled, I opened terminal and checked that manual FTP worked. It did. Here’s the session:
$ ftp upload.alamy.com
Connected to upload.alamy.com.
220 Microsoft FTP Service
Name (upload.alamy.com:jenn): email@isp.com
331 Password required for email@isp.com.
Password: ****
230 User logged in.
Remote system type is Windows_NT.
ftp> cd Stock
250 CWD command successful.
ftp> pwd
Remote directory: /Stock
ftp> exit
221 Goodbye.

This was from my home wifi. I’ve sent the log.

PM can get that far too.  But the problem occurs when PM tries to contact the socket that the server created and specified prior to uploading a file.  So to have a conclusive test with the FTP command line client you would have to then try and upload a file.  Are you able to do this?

-Kirk

[Jen Mack]

I’ll try the next upload via terminal with vpn up.