What to do when the Plesk subdomain is not working? Read the article to know more. Bobcares, as a part of our Plesk hosting support offers solutions to every query that comes our way.

Fixing Plesk Subdomain Not Working Issue

When a subdomain in Plesk stops working, it usually means that it is either not reachable or is not working as intended. So, a subdomain may not be functioning for a number of reasons, and diagnosing the problem may require testing different settings and setups. Here are some typical actions we can take to identify and fix the issue:

1. DNS setting: Incorrect or incomplete DNS setting is the most frequent cause of a subdomain not functioning. So, we must make sure that the DNS records are set up correctly. This involves setting up a DNS A record or CNAME record that points to the correct hostname or IP address.

2. Web server settings: Also, ensure that the subdomain’s web server setup is correct. Then, verify that the Plesk virtual host settings for the subdomain, including the document root and other essential settings, are configured appropriately.

3. Subdomain Folder: Verify the website files are in the folder or directory connected to the subdomain on the server. So, this folder should be the document root in the web server configuration.

4. SSL/TLS Certificates: If the subdomain uses SSL/TLS certificates, then we must make sure the installation and setup are correct. Access difficulties occur by mismatched or expired certificates.

5. Security and Firewall Rules: Verify whether any security or firewall rules are preventing access to the subdomain. Verify that server setup or security apps are not preventing access to the subdomain.

6. Permissions: Check the file and directory permissions for the files on the subdomain to make sure they are set properly. Access is not possible if the permissions are incorrect.

7. Services: Make sure that all essential Plesk services, such as the web server and DNS server, are operational. For information on the status of these services, we can check the Plesk interface.

8. Browser Caches: Clear the cache in the browser to resolve cache and browser issues, or try using a new browser or device to visit the subdomain. Potential access issues include cached DNS configurations and browser data.

9. Error Messages: If we receive any error messages while trying to visit the subdomain, these will be very helpful in finding the underlying problem. Discover the issue by looking into the error messages.

10. Logs: Search for any pertinent error messages that might provide more information about the problem in the server logs (such as the error logs for Apache or Nginx).

[Looking for a solution to another query? We are just a click away.]

Conclusion

The article points out 10 major things provided by our Tech team that we must consider when the Plesk Subdomain Not Working issue arises.