• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue FTP to store Plesk server backup

zakaria

Basic Pleskian
Server operating system version
debian 10
Plesk version and microupdate number
Version 18.0.42 Update #1
Hi, hope everyone is doing well;
I set up an FTP server with IIS to store backups, it worked fine but not when it's behind pfSense firewall
even with port 21 forwarded, I needed to also forward the range for passive mode for it to work
but then it stopped working for no apparent reason, I get Curl error: (28) Timeout was reached
I set the range for now to 5000-10000, but I want to make it smaller if possible
I also wanted to move to FTPS, I certified it and when tried to use it, it didn't work with and without the firewall
do I need to do something other than ticking the use FTPS option?
 
I managed to solve the issue

turns out, IIS didn't use the range I specified, it's a problem with IIS needing to restart ftpsvc service from services restart in IIS doesn't work
the one time that worked was just a coincidence, IIS probably used a port within the range open in pfSense
this solved FTP through pfSense, but to make FTPS work I needed to also allow port 990

now I can make the range as small as I need, even down to one port, but I wouldn't recommend it just in case some other application take that port
 
After more testing, it seems forwarding port 990 doesn't make a difference, so I'm not sure what was stopping FTPS from working
 
Back
Top