If you’re getting a 403, 404, or 500 error when you go to your domain name, there are many different causes that may be to blame. Below are some of the more common issues and how to fix them.
The first thing you should do is check the DNS records on your domain name. Make sure that you have the correct name servers and DNS records. If you are hosted with Name.com, then this means that your name servers should be ns1-ns4.name.com and your DNS should include A records that point to your hosting. You can find our guide on how to set up our default name servers here, and our guide on adding A records for your Name.com hosting is here.
If those records seem fine, the next step is to look into your hosting files.
- Log into your hosting cPanel.
- Click File Manager under Files.
- Make sure you select Web Root as the destination and check the box for Show Hidden Files, then click Go.
- This will bring you to the public_html folder. In this folder, there needs to be either an index.html file or an index.php file. If you do not see one of those here, this is the problem. Check to make sure that the file has not accidentally been uploaded to the wrong directory, and re-upload it if necessary.
If you do have an index file in the public_html folder, then it may be a file permissions error. In the file manager, you can see the permissions for each file under the Perms column on the right. In most cases, files should be set to 644 and folders should be set to 755.
- To change the permissions on a file or folder, right click the item you would like to change and select Change Permissions.
- To set the permissions to 755 for folders, check all three boxes under the User column, and under the Group and World columns check only the Read and Execute boxes.
- To set the permissions to 644 for files, check only the Read and Write boxes under the User column, and check only the Read boxes under the Group and World columns.
Note: Changing the permissions on a folder will not change the permissions of the files within that folder.
If none of the above works, the problem may be something in your .htaccess file. Find this file, and rename it to something like .htaccess_old. This will cause the system to auto-generate a new, blank .htaccess file. If after changing this the domain name now resolves, this means there is an error in the coding of the original .htaccess file. Unfortunately, we can’t fix coding errors for you, so you’ll have to take a look in there and see what’s wrong for yourself, or get your web developer to take a look at it. please note, not all sites have an .htaccess file, but if your does, be very careful with the coding.
While there can be many causes, the above problems are by far the most common. If all of this still doesn’t resolve your problem, send us an email at firstname.lastname@example.org and let us know everything you have tried so far. We’ll do everything we can to get it working for you again.