• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Plesk 7.5.5 Domain Problem

S

Shojaee

Guest
Hi all,

I'm facing a strange problem in my Plesk installation.

I'm unsing 7.5.5 on Windows 2003 Web Edition. I've created a domain using Plesk but,

- Microsoft Frontpage 2003 can not open the site. The error message is "The folder isn't accessible blah blah blah". I've double checked that "Microsoft Frontpage support" and "Remote Microsoft Frontpage authoring" are enabled.

- Locally (at the server) I'm seeing "Domain Default Page" which is normal, but remotely (from another computer) I'm seeing "Default Plesk Page". What's wrong with it? DNS resolves correclty, everything seems normal but I can't see correct page.

- "Site Preview" displays the page correctly.

- "FP Web Admin" displays "The page can not be found" error.

- If I enable "SSL support" and "Frontpage over SSL" options, I don't have any problem.

I've used reconfigurator to check the permissions. It didn't find any problem. Also I've checked the settings in IIS manager. It looks normal.


Any ideas?
 
We've just had a similar problem with a client. They are intermitently reporting that they are getting the default server page instead of their site. I got them to ping and it went to the correct adress. After that it seemed to work again so maybe it needed a new DNS lookup. The customer had the issue on 3 computers on their network so I don't think it is just one PC doing this.

As I understand it for Apache to show the defulat Plesk page instead of their site it requires their dns to send thew browser to look for x.com at x.x.x.2 instead of x.x.x.1. I do beleieve our customer may have been setup with us previously with another IP address so somewhere along the line someone is reporting the old IP address to their DNS. This would have been over 10 months ago though. Any one have any ideas.

Shojee did you change your customers IP address recently?
 
Back
Top