Returning a forwarded Plesk subdomain to website hosting

Locate a verified backup or deployment package for the intended site. Record the existing redirect destination, DNS and certificate settings. Check whether the redirect was configured as Plesk forwarding, an application rule, a proxy rule or a web-server directive.

1. Open the subdomain Hosting Settings. If its type is Forwarding, use the available change control and select Website hosting.
2. Review the document root and available system-user settings. Save the change without assuming the old directory contents still exist.
3. Deploy or restore the intended website files and database through an approved recovery workflow. Configure the application hostname and required runtime.
4. Review remaining redirects in the application, web-server configuration and any external proxy. Remove only the obsolete rule that sends visitors away.
5. Confirm valid TLS coverage and test the website before announcing the return. Where practical, use a controlled preview while the public transition is being prepared.

Check that a request reaches the restored site and returns the expected content instead of a redirect. Test login, forms and database reads and writes. Use a fresh browser session because a previous permanent redirect can be cached.

If a default page appears, inspect document root and deployment contents. If forwarding persists, inspect the actual response and each possible redirect layer. Do not repeatedly toggle hosting types because that can cause further data loss. If the original files are missing, restore a known recovery point and account for data created after that point.

• Redirecting a Plesk subdomain to another website
• Creating a subdomain website in Plesk
• Uploading website files with Plesk File Manager
• Creating and downloading a full subscription backup in Plesk

• Plesk: 18519602874263 How To Change Hosting Type For Domain In Plesk
• Plesk: 12377711705623 How To Create A Domain Forwarder In Plesk