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

Website just redirects to the IP default

T

thedust2010

Guest
I have about 50 sites set up on my Plesk box. I recently set up a new domain, configured the domain's DNS records to point to my server, but when you call upon the domain it just brings up the default website for the IP address that it is on. The website doesn't come up at all! Here is how the DNS is configured on my Plesk box (default):

mydomainnamehere.com. NS ns1.mydomainnamehere.us.
mydomainnamehere.com. NS ns2.mydomainnamehere.us.
mydomainnamehere.com. A xxx.xxx.xxx..235
mail.mydomainnamehere.com. A xxx.xxx.xxx..235
webmail.mydomainnamehere.com. A xxx.xxx.xxx..235
ns1.mydomainnamehere.com. A xxx.xxx.xxx..234
ns2.mydomainnamehere.com. A xxx.xxx.xxx..235
ftp.mydomainnamehere.com. CNAME mydomainnamehere.com.
lists.mydomainnamehere.com. CNAME mydomainnamehere.com.
www.mydomainnamehere.com. CNAME mydomainnamehere.com.
mydomainnamehere.com. MX (10) mail.mydomainnamehere.com.
xxx.xxx.xxx..235 / 24 PTR mydomainnamehere.com.

Any idea what might be wrong here? This is really strange. Never had this problem before...
 
Occasionally, apache wants to be a .... Plesk, by default, reloads apache every 300 seconds. Or is it 900? Ahh, anyway. The problem you're having directly relates to apache not having the new configuration loaded yet. You can forcably reload this information by issuing a "service apache reload", by going to the Admin Control Panel -> Server -> Services -> Apache (Reload), or by merely waiting 5-15 minutes for the system to do this automatically. In this case, as it's been more than a day, your site should be active by now.
 
And so the site IS working now. Brilliant. Thanks for the info!
 
Back
Top