• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk working on nat

D

dc06

Guest
Does any one know if you can use plesk on a nat router?
I think its possible if i forward the correct ports but im not sure of all the ports i need to forward? Can anyone help?
 
On the router, or behind the router ? If you want to run plesk directly on nat machine than basically no modifications are required. But i just will not recommend you to do this. :rolleyes:

What you asking is more similar to work behind nat (forwarding ports, etc).

If you want to run plesk behind the firewall you maybe want also to read some extra literature before very beginning of that.
Basically anything is easy - you forward http, mail, dns, directly from nat to plesk in DMZ, or just in internal network, and you modify dns template to use hardcoded exteraml ip of your nat machine.
Devil as usual in details.

Only thing i can say to you is that for http/https probability of painless success is very good, but when you deal with mail or, specially ftp than you can get a rid of troubles just as soon as you begin. Dns also may offer some extra headache to you...

Also maybe it's reasonable for you to pass http thru so called reverse proxy, not directly pass traffic to Plesk. But that is loooots of devil, i've noted before :p

In other words you getting what you run from - instead of good automation you have to deal with tones of routine tasks.

Well, for well experienced system administrator it's possible to configure Plesk behind firewall to work during one, or two workdays, depend on your network configuration. After this mostly anything will work continuously. Or before you change something in your net :rolleyes:.

Also there is good practice of not placing all the eggs int one basket, so notice - when something breaks up in your net you got complete disaster if your web server is also there. :D
 
thanks for the advice, been working flat out on trying to sort this out.
got plesk working fine for 3 hours, then it died. again
ftp working ok, dns is saying everything is fine but not gaining access again.
 
Back
Top