Hi there,

first things first, I'm a newbie using unraid, so please take it easy on me. I'm shure I am missing something pretty obvious, but i can't get my head wrapped around what it could be. So I'm switching from my Synology NAS to Unraid. I activated the FTP service and added the user i whish to have access. When i use my unraid's LAN Ip, with the standard Port (21 as far as i know) everything works fine. After that i configured my Router to forward Port 77 on my WAN Address to 21 on the unraid servers LAN adress (I attached a picture of this) it doesn't work. I am always getting a weird error, saying it couldn't download some kind of a file (using firefox testing the ftp most of the time, filezilla doesn't work neither from WAN). There has to be some kind of Setting on unraid I'm missing, bc. the forwarding works (at least it did work with the Synology one, obviously with different Ip)

 

I have some things in mind, I'd like your opinion on:

-I am using static IP-addresses don't know if this affects it

-I don't have a DNS entry on our DNS Server for the unraid server yet, again, don't know if this is a problem

 

A comment to the attached image:

77 is unraid

21 and 22 is old synology

other ports forwarded aren't important, they are used for different servers and everything is working fine

pls ignore the german writing and my poor english

You shouldn't put your server on the internet without a VPN.

 

Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your NEXT post.

I know that a VPN would be more secure. I have to do it this way, at least if I want to use Unraid for my FTP. We are using a webbased tool which creates invoices (pdf format) . Those are saved to an FTP and I have to save them and keep them. So for convenience I did it directly to my NAS until now. 

naswern-diagnostics-20191203-2052.zip

On 12/3/2019 at 10:01 AM, trurl said:

You shouldn't put your server on the internet without a VPN.

Reiterating this point, if you need to expose FTP directly to the internet i would suggest trying to find an FTP Docker Container, rather than exposing the builtin service.

Is there a possibility, this solves my port forwarding Problem? And which Docker Container would you recommend?

Edited December 4, 20196 yr by welusa

On 12/4/2019 at 2:12 PM, welusa said:

Is there a possibility, this solves my port forwarding Problem? 

Hard to say, as I am not certain what your issue is. It does add another level of possible port forwarding (the docker port mapping essentially forwards a port from the unraid host to a port in the container). 

 

On 12/4/2019 at 2:12 PM, welusa said:

And which Docker Container would you recommend?

Unfortunately I dont really have one, as i dont use FTP myself. My recommendation was based purely on my philosophy for unRAID which is always use Docker, unless you cant. I would guess a search of Community Applications would turn up several options, though I am not in front of my server so i cant confirm. Looking at docker hub I see jlesage/filezilla, I have never used it but i have used other jlesage containers.