GvilleRick

Most of the PhpBB hacks exploit the code to inject information into the MySQL database. I would suggest looking through your site using either FTP or the File Manager in cPanel to see if there are any files that you don't recognize. You can also look at the database using PhpMyAdmin and see if you see any odd entries left over. I would guess the restore of the database you had run corrected that for now. You should update the software as soon as possible to keep them from returning to hack in again.

I reread the whole thread and do not see a domain given that we can look at to see what comes up. The main page should be called index.htm or index.html and should be all lower case letters. If you post a URL we can see what loads for us and that can help determine if there is something causing the problem on your local machine.

I would suggest reopening the ticket and ask someone to check the account set up and provide the IP address that the account is on. The TCH nameservers are not returning an IP for the domain which could indicate a problem with the account set up.

You should submit a ticket and have a tech check that the mailman daemon has not stalled.

You have Hotlink protection on and do not have the subdomain listed as allowed. You can go to the Hotlink protection section in your cPanel and add the http://www.cms.loonsecho.net/ and http://cms.loonsecho.net/ entries so that it will allow graphics or disable Hotlink protection.

I have installed it on a couple of accounts and had no problems. I just installed it on a test domain into a folder called cms and it worked fine. I then created a subdomain called cms and it worked using the subdomain as well. It looks like a problem either in the configuration or a setting in .htaccess since I see the graphic fine at http://www.loonsecho.net/cms/.

You can set up an FTP account for the folder in your Manage FTP section. This will allow access to that folder (and folders within that folder.)

If you send through your Gmail account to an account that forwards to the GMail account it will fail. I have seen that before when testing for a similar problem. I suspect that it is due to GMail refusing the mail to prevent looping.