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

4.1 - cannot edit site - redirects to error page

M

m.r.davies

Guest
I've just downloaded and install sitebuilder 4.1
However, when in the wizard and i click edit site, it redirects to an error page

and says

The page at http://xxx/Sites/6f7d967a-020c-4631-8122-ea73819b35f6/ is unavailable. Please contact your Sitebuilder provider to resolve this problem.

Return to editing the site

All i did was install sitebuilder and try and edit the site
i've not got any further

If i try on the local URL
http://localhost:2006/Admin/DashBoard.aspx
it works fine

I've added my host header entry on IIS for my domain on port 80 and it doesn't seem to work on that.

HELP!
 
actually the release notes states its an issue, so i followed the fix on there
 
1. Try to follow up url from the error page:
http://xxx/Sites/6f7d967a-020c-4631-8122-ea73819b35f6/
2. If site is available and you see site's error screen - go to the web.config, find there customErrors attribute and set it's value to "Off".
3. Try to follow up url from the error page again (don't just press "Refresh" in the browser, enter site url again).

You should see site's detailed error then. It'll help to understand the problem.
 
Back
Top