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

nginx dosen t start on adding other IP addresses

pdsolutions1

Basic Pleskian
Hello,

I have the latest plesk version 12.5 with centos7, on adding a new IPV4 and IPV6 adresses on Tools&settings -> Ip ... add new -> xx.xx.xx.xx/32 for dedicated IV4 and xx.xx.xx.xx.xx/64 for IPV6
Restarting the server, nginx dosen t start with error: "nginx emerg bind() to 443 failed (99 cannot assign requested address)" the error includes the NEW IP6 wich i checked with the provider support team and is correct.
So, searching for similar issues, i fond this: http://kb.odin.com/en/114245 "Nginx does not start after IP change" -> In my case, i don't need an IP change, i just want to add some other Ip's in order to set different Ip's on webpages i host. BUT, the fix is working till a new reboot. So after the fix, if i reboot the machine ngnix will fail again with same error.

How can i fix this?

Thanks
 
Back
Top