• 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 New site pointing to another website

huge321

New Pleskian
I have our first site that is pointing to a dedicated IP address and the first website works fine. I have added another site and have utilize another dedicated IP address. When you go to the website, you get directed to the first website created in the system. However, webmail is working correctly.?.?

What might I have wrong here?

Should I be using a shared IP address or continue using dedicated IP address?
 
Hello,

The webmail interface is the same for all the domains in the server.
Regarding the domain issue, I would check the DNS and confirm that the secondary domain actually points to the secondary dedicated IP.

If that is correct, try rebuilding the apache config with: /usr/local/psa/admin/bin/httpdmng --reconfigure-all
 
Thanks for the input... I found the issue.

My Fortigate setup did not forward to the new shared IP address. Once I set that up, all was fine.
 
Back
Top