5

Finally stumbled on the delpop command and cPanel's command-line interface. So, assuming: You have SSH access to your account Your host has installed cPanel in the usual way Then you can delete a single email account with this command, using an SSH client like PuTTY: /usr/local/cpanel/cpanel-email delpop account_003 0 mydomain.com To delete many ...


3

These files were never on your account, they were hosted on another account on the same (shared) server with username "impots". On many shared Apache servers you can access your account's files by a URL of the form http://<server-IP>/~username (a feature known as "per-user web directories" handled by mod_userdir). This allows you to access your ...


2

I cannot post an image as a comment, but I can tell you the problem is on the domain side Move the mail server from the orange box to the blue one. How you do that varies from host to host. Until your MX record is fixed you can only send mail from an address in your domain to an address in your domain. In case you cant see the image, I used the NSLOOKUP ...


2

I'd talk to your host about whitelisting certain URLs for ModSecurity. i.e. keep it on, but with modifications. It looks like an OAuth redirect (Google login) triggers the problem you are having. Your question is broad however, as is the topic of security. What security issues are you attempting to prevent? is probably a counter question to yours. Only once ...


2

Why wouldn't it be? People usually eliminate ads from the mental map of your site - and by that logic having the same banner would be more harmful in the long (LONG) term. Now, by rotating, do you mean literally it scrolls through during the same pageload, or each pageload it will load a different image? Having a scrolling banner, depending on the size, ...


1

I found that the IP address that came with my HostGator account information email was not the right one. I logged into CPanel via the temporary URL and found the actual IP address listed on the column to the right towards the bottom.


1

I had to wait 24 hours for a similar situation. DNS stuff can be slow to propagate. If the situation is not resolved by then, then there is a configuration issue or your DNS servers are down. You don't need to remove the hosting package if your DNS servers are set properly at Hostgator (i.e., you are using the IPs of DigitalOcean for your domain name). If ...


1

It turns out that the problem was how I was generating the response headers. I'm using the Slim PHP framework, and a custom error handler middleware. It looked like this: class ErrorResponseHandler { protected $view = null; function __construct(\Slim\Views\Twig $view) { $this->view = $view; } public function __invoke(Request $...


1

If you added on a domain name, make sure the domain is officially registered, and DNS is set properly and propagation is completed (usually about 24 to 48 hours). You can call HostGator.com via live chat http://chat.hostgator.com/ or via telephone 866-964-2867 available 24 hours a day to get assistance. https://www.hostgator.com/help > you can search '...


1

You do not need to change the DNS. If you did that, the CNAME and A records would be pushed to be handled by Github, and that is not how it works. Add a CNAME file to your repository in the GitHub account. Once you log into your GitHub account, click on your repository name: Then click on the + sign to add a new file to your repository: Use CNAME for File ...


1

In your cmd prompt, do a nslookup mydomain.com and make sure the correct nameservers display for HostGator. Also to be sure your ISP DNS is cleared, do a ipconfig /flushdns.


1

How long ago did you do this? While registrars will tell you it takes 24-48 hours for your DNS set up to propagate around the world, in reality, you could notice changes in less than an hour. So you need to wait a while for things to happen.


1

First, restart the router. This sounds like it may be a DNS issue and not with the site itself. Try accessing the IP address of the site rather than the URL (e.g., instead of http://google.com, type http://12.345.67.891). If it works, it's probably a DNS resolution problem. To fix, open up command prompt and run ipconfig /flushdns


Only top voted, non community-wiki answers of a minimum length are eligible