(SOLVED) Can no longer connect for ftp transfer

Help Fairphone 4
1

I don’t do it often, but now and then transfer files between my FP4 and my laptop. Previously this ahs worked perfectly, using FileManager+ on my phone and filezilla on my laptop (running slackware linux).

However, I can no longer set up a connection, just getting a ‘connection failed - no route to host’ message. Tried various ftp server apps on the phone, and various clients on my laptop (also trying to connect via terminal). Cleared filezilla’s cache and config, no difference

Since the FileManager+/filezilla route works fine with a samsung tablet, I presume that the cause lies with my FP. Maybe the latest system upgrade (20250703)?

Is there a setting hidden somewhere for allowing ftp transfer?

2

“no route to host” in principle means that the overall network setup is such that your laptop doesn’t know how to reach the FP4 over the network at all, independent of the protocol (i.e. the same would happen for HTTP).

Do you use IPs or DNS names in Filezilla in order to connect?

If it is via IP, maybe for some reason the FP4 had a different IP in the past (still used in Filezilla)?

3

IP adress.

FileManager+ gives me the IP address, port, username and password which I enter in filezilla.

Exactly the same with my samsung tablet, which connects without issues. Also, this has worked in the past with my FP4.

4

The IP shown in FileManager+ on the FP4 is the same that your router shows for the FP4?

Edit: do you use some kind of VPN based ad blocker on your FP4 that you don’t use on the tablet?

Edit2: do the IP addresses of the FP4 and Samsung look similar, i.e. only differ in the last number of the tuple? Are those IPv4 or IPv6 adresses?

5

IP addresses are the same (I guess that FileManager picks it from the router).

No ad blocker.

IP addresses on FP and tablet the same, except last digit (and different ports).

6

I’m a bit out of ideas at the moment. :frowning:

7

Switched both FP and laptop to router’s 5GHz band (which gave a new IP address). Connected without issues.

Switched back to the 2.4 GHz band (same IP address as for the previous failed attempts) and … connected without issues.

One of those mysterious experiences… anyway, problem solved (at least for now).

1 Like