SageBrian
- Total activity 35
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 15
Comments
Recent activity by SageBrian-
spoke too soon. I got in, then when I tried to Add Account, my session wanted to log me in again, though I could see I was already logged in. I'll clear browser cache and restart process and see if...
-
I just had the same thing happen. Brand new install of cpanel. I run EasyApache, and my session ends. I then cannot login anymore with root, via whm browser, or ssh. I come back about a half hour ...
-
It's not the warnings you should be concerned with. It's the possible access that is not caught by the firewall. :) Sleep well. The first time you see how many attempts are made on a server, it c...
-
So glad to see mtindor and sparek-3 state what I thought was obvious. Users are the weakest link. I've been getting these 'hacks', which are nothing but bots using known credentials. No guessing,...
-
Is the error coming from Joomla trying to send an email? By default, Joomla uses PHP on the server to send mail out. That's why I put the IP address in SPF. But, if the user setup Joomla to login ...
-
If using Google Apps, the mail should not be going through the cpanel server. All mail flows through Google's servers. The only setting to be aware of is to put your cpanel server's IP address in t...
-
I remember that bug. I always wondered why, when an account was suspended, it wasn't noticed. And it's because they were still using email. I don't suspend often, but when I do, I have been manuall...
-
Wordpress and Joomla sites are getting very very big brute force attacks lately. The bots are looking to take advantage of all the users of Joomla and Wordpress that don't bother upgrading their ve...
-
Fowarders and noobies. (and some not so new 'admins') If forwarding to another address, and you do not need a copy of the email, do NOT create a Mail Account. I know this seems obvious, but I'm a...
-
Run "yum -y update". I had the same problem, ran yum again and it resolved the problem for me. Looks like Apache was compiled yesterday and then again today. Yup, that fixed it for me.