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

Resolved Problem with 1-click installation on Plesk

Émerson Felinto

Regular Pleskian
I have the following problem.
I installed Plesk using the 1-click installer available in the Plesk documentation. When I first logged in I was asked for some information, something I found strange was the IP that Plesk did not detect the public IP but the private IP of the machine. I continued the installation and configured this IP manually as shared IP.
I created a site in Plesk, I added WordPress, I checked the files, but when I open the page, Error 404 only appears.
Any idea how to solve it?
 
The problem remains the same.
I also noticed that when accessing the main IP of my VPS simply the browser gives no response. Do you know what's happening?
 
A lot of different reasons may be - firewall rules, not started web server, etc. Have you tried to troubleshoot it?
 
I decided!
Forgive me for the silly mistake ...
In "Hosting Settings", I marked "301 Redirect SEO Permanent HTTP Secure for HTTPS".
So even after his tip on NAT I was not able to solve. Problem solved.
Thank you!
 
If your Plesk server is behind NAT, you can match private IP addresses on the server to the corresponding public IP addresses via the Plesk interface. More details you can find here Running Plesk Behind a Router with NAT
Hello Igor,

my Plesk installation is running behind a NAT on a private IP.

After installation I can reach the Plesk Login. So is there any way to do those settings from the CLI ?
 
Back
Top