F5F Stay Refreshed Software Operating Systems Raspbian SFTP received a passive response from the server that had an unreachable address.

Raspbian SFTP received a passive response from the server that had an unreachable address.

Raspbian SFTP received a passive response from the server that had an unreachable address.

B
BlueStar_LH
Posting Freak
842
10-05-2016, 07:53 AM
#1
I'm just starting out with Linux and needed a server for handling my photography files. I set up a Raspberry Pi and can reach it on my local network, but when accessing the internet I encounter this error: "Server sent reply with unroutable address." I've tried adjusting FileZilla's settings online, but haven't found a solution. Someone with more experience would be really helpful here.
B
BlueStar_LH
10-05-2016, 07:53 AM #1

I'm just starting out with Linux and needed a server for handling my photography files. I set up a Raspberry Pi and can reach it on my local network, but when accessing the internet I encounter this error: "Server sent reply with unroutable address." I've tried adjusting FileZilla's settings online, but haven't found a solution. Someone with more experience would be really helpful here.

K
KlayDog1
Senior Member
685
10-10-2016, 01:00 PM
#2
I'm using FTP to access those files. For connecting to my own network, I set up DynDNS and PublicIP. A VPN was also configured for secure access. Port forwarding was enabled in the router settings. I haven't attached screenshots yet, but I can share the configuration details if needed. Your PI should be able to reach the internet as well; you can test with the ping commands provided. Running "ifconfig" on your Pi will show the current network interface and IP address.
K
KlayDog1
10-10-2016, 01:00 PM #2

I'm using FTP to access those files. For connecting to my own network, I set up DynDNS and PublicIP. A VPN was also configured for secure access. Port forwarding was enabled in the router settings. I haven't attached screenshots yet, but I can share the configuration details if needed. Your PI should be able to reach the internet as well; you can test with the ping commands provided. Running "ifconfig" on your Pi will show the current network interface and IP address.

C
Chiller9592
Senior Member
670
10-12-2016, 09:56 AM
#3
1. I have a fixed IP address and connect via VPN for secure file transfers.
2. I configured a static IP on my router.
3. I installed PF on my router.
4. Using proFTPd, I verified the IP address on the router.
5. The IP was confirmed in the router settings.
C
Chiller9592
10-12-2016, 09:56 AM #3

1. I have a fixed IP address and connect via VPN for secure file transfers.
2. I configured a static IP on my router.
3. I installed PF on my router.
4. Using proFTPd, I verified the IP address on the router.
5. The IP was confirmed in the router settings.

M
maxxam2000
Junior Member
10
10-14-2016, 06:10 AM
#4
I'm a bit puzzled about your configuration. Using a VPN often lets most routers connect directly to their local network, which means port forwarding might not be required. Since SFTP is already secure, relying solely on a VPN for file transfers isn't essential. The port you're using isn't the standard 22 for SFTP; it's likely 7493 for your SSH service. You can verify active services with commands like "sudo netstat -ltpn" or "sudo ss -ltpn." I also examined your error message more closely—it suggested you're using FTP instead of SFTP, which are fundamentally different protocols. The passive/active mode needs to be enabled on the server side as well. You'll need to set up the FTP server settings, which depends on the software you're running (the commands above might reveal what's installed). With VPN in place, this should generally work fine, though it looks like the FTP connection isn't routed through the tunnel.
M
maxxam2000
10-14-2016, 06:10 AM #4

I'm a bit puzzled about your configuration. Using a VPN often lets most routers connect directly to their local network, which means port forwarding might not be required. Since SFTP is already secure, relying solely on a VPN for file transfers isn't essential. The port you're using isn't the standard 22 for SFTP; it's likely 7493 for your SSH service. You can verify active services with commands like "sudo netstat -ltpn" or "sudo ss -ltpn." I also examined your error message more closely—it suggested you're using FTP instead of SFTP, which are fundamentally different protocols. The passive/active mode needs to be enabled on the server side as well. You'll need to set up the FTP server settings, which depends on the software you're running (the commands above might reveal what's installed). With VPN in place, this should generally work fine, though it looks like the FTP connection isn't routed through the tunnel.

H
Hamparen
Junior Member
9
10-14-2016, 10:08 AM
#5
I rely on a VPN for everyday tasks, not for direct connections to my home network. Here’s the general approach I took when setting up my server: https://ryanfitton.co.uk/blog/quick-and-...pberry-pi/ I’m focusing on the port issue and hope it resolves. Thanks for your time and support.
H
Hamparen
10-14-2016, 10:08 AM #5

I rely on a VPN for everyday tasks, not for direct connections to my home network. Here’s the general approach I took when setting up my server: https://ryanfitton.co.uk/blog/quick-and-...pberry-pi/ I’m focusing on the port issue and hope it resolves. Thanks for your time and support.

L
LucasandClaus
Senior Member
438
10-19-2016, 08:12 AM
#6
The port configuration in the proFTPD files is correct, but you're having trouble locating the SFTP file in the terminal to modify it.
L
LucasandClaus
10-19-2016, 08:12 AM #6

The port configuration in the proFTPD files is correct, but you're having trouble locating the SFTP file in the terminal to modify it.