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

Multiple IP's & apache binding

CoreyC

New Pleskian
Does anyone know how to configure address binding for apache?

I have two IP addresses on this particular container. I was able to bind port 80 to a specified IP, but when I attempted to bind 443 to a specific IP, apache would not start.

For a temporary solution I configured SSL on port 444.

I only modified ports.conf - I did not want to go any further to avoid any downtime or loss of settings.

Thanks!
 
I wanted to bump this and expand on my issue in hopes someone has some insight.

When adding an account via WHMCS, Plesk restarts Apache. This leads to a blank page before the sign up process is complete, if you do not hit refresh you are unable to sign up.

Our solution was to use a second IP and run our WHMCS instance on the other IP under lighttpd. Since Apache is binding to all IP's by default, this left us unable to run SSL for our sign up process.

I was able to bind Apache to the primary IP for http only. This leaves Apache https conflicting with lighttpd - since we have no need for https for clients, I have set Apache's SSL port to 444.
 
Back
Top