• 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.

Server behind firewall / NAT

T

tvengel

Guest
Hello,

Our servers are placed behind a firewall and working okay. We want to upgrade / transform one of our servers to Plesk.
I'll explain the current configuration (btw : the are examples) :
* WAN IP : x.x.x.46
* LAN IP : 172.16.10.46
Between the WAN ip and the LAN ip is a NAT table; which forwards the used ports.

Now, when we create a domain, everything seems to be configured fine, but some parts don't work okay. For example, in the ftp-server, there are 2 domains configured. The WAN ip and the LAN ip. Every user is added to the LAN ip, but will not be able to connect.

Maybe someone did this configuration before and can help me with this.

Regards,
Tim Van Engeland
 
You have three ways to to resolve problem:
1. Add as much IP to NAT as your Plesk server has. And configure redirection on it - one IP on NAT to one IP on Plesk server :
e.g.:
x.x.x.1 (public IP) 21 -> 172.16.0.1:21
x.x.x.2 21 -> 172.16.0.2:21
and so on
2. Use different ports
x.x.x1 21 ->172.16.0.1:21
x.x.x.1 2021 ->172.16..0.2 21
and so on
(users need to connect using ports configured on NAT)
3. Use one IP on Plesk server, and all users will be on one IP , in this case you'll need one redirection on NAT
public IP 21-> private IP 21

John S.G.
 
Hello,

My opinion goes to the third method. When I configure plesk for this, and change the default DNS table, everything seems to work fine, except, when I create a subdomain, it takes the internal ip.

Current config :
WAN IP xxx.xxx.xxx. 46
LAN IP 172.16.10.46
Forwarded all needed ports from the WAN IP to the LAN IP.
Configured 172.16.10.46 as the shared ip in Plesk and modified the default DNS template.

Any advice? Or do I need to do it otherwise?

Regards,
Tim Van Engeland
 
DNS Server behind firewall / NAT problem

hi
i have above problem too.
on my server every thing work fine but when i create a subdomain ip of that is invalid ip on my server.
 
Back
Top