In most cases, this error means that a certain file cannot be found within your website. This is not a fatal error; the requested file does not exist on the server or the address in your browser contains an error. Check the path (capital sensitive) and upload the file again if needed. Then, the file most likely will be found again.
If you visit your domain without a suffix (so example.com with nothing after that) and you see the 'Not Found' error, there is a bigger issue. The public_html folder is then deleted or inaccessible. You can follow the steps below to fix it.
Check if your domain is pointing to your Antagonist package
It can be the case that your domain is hosted elsewhere, and the nameservers are not pointed to your Antagonist hosting package. In that case, the website on your hosting package is not being displayed, and if your domain is not connected to another hosting package, this can result in a 'Not found' error.
Change your nameservers then to those of Antagonist. Do note that your DNS records should already be present within your Antagonist hosting package before you change your nameservers.
Restore symlink to public_html folder
While this problem is often not related to your website not being accessible, it is usually solved by doing this. You can do so by logging into DirectAdmin. Go to 'Account manager' and then 'Domain setup'. Check your domain using the checkbox and click on 'Set as default'.
Check afterwards if you are still having the exact same error. If so, continue with the next step. If not, the problem has been solved. Another error you are then getting is then another problem.
Restore your public_html folder
Check whether your public_html folder is in the right place and reachable from Apache.
- Log into DirectAdmin and go to File manager.
- Click on your domain name.
After that, you will probably see one of the following folders (of which deb12345 is your username):
| Folder name | Perm. | UID | GID |
|---|---|---|---|
| .htpasswd | 755 | deb12345 | deb12345 |
| logs | 755 | root | deb12345 |
| private_html | 711 | deb12345 | deb12345 |
| public_ftp | 711 | deb12345 | deb12345 |
| public_html | 750 | deb12345 | apache |
| stats | 755 | root | root |
Do note that the list above is just an example; it is not necessary that you have all the folders as noted above.
With this error, it is of the utmost importance that your public_html folder is on the right location and has the permissions to be written to. If you cannot find the folder on the indicated location, you can create a new folder and name it public_html. If you cannot find the folder with your domain name, you will need to create your domain again (which will be explained later).
Do check if public_html is readable from apache and can be written to from your user. You can do so by changing the chmods of the folder. The permissions in the table below are the minimum:
| UID | GID | Solution |
|---|---|---|
| deb12345 | deb12345 | Permission should be 755 |
| deb12345 | apache | This is correct, permission should be 750 |
| deb12345 | root | Permission should be 755 |
| apache | deb12345 | Permission should be 770 |
| apache | apache | Click 'Reset Ownership' and set permission to 755 |
| apache | root | Same as above |
| root | deb12345 | Permission should be 775 |
| root | apache | Click 'Reset Ownership' and set permission to 755 |
| root | root | Same as above |
Try your domain again. If you get a forbidden error, refer to the 403 manual. Otherwise, continue with the next step.
Creating your domain again
Apparently, the problem is a bit more complex and more has been deleted from your account. A simpler solution than erasing your domain does not exist then. However, this is not without risks.
Do note!
By following this procedure, all e-mails, settings and uploaded data will be erased. Databases will remain intact, since these are not connected to a domain. It is however good sense to also create a backup of your databases before continuing.
You can contact us at support@partners.one to take a look. We might be able to restore the package without any data loss.
Make sure to back up your important e-mails and data from your account and write down your settings somewhere. Then, follow the manual on resetting your account.
Once done, check whether you still get a Not Found notification. If you get a Forbidden notification, refer to the 403 manual.
If the problem still persists, contact us. We then need to recreate your account again. This will also include the removal of your databases, so make sure to back those up first on a separate location.