ad682005
- Total activity 20
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 6
Activity overview
Latest activity by ad682005-
ad682005 commented,
Scratch that. I think the issue I faced was because of cphulk protection. As soon as I cleared that - I was able to login (although by this time the license had been renewed).
-
ad682005 commented,
Unfortunately - this issue is occurring even now. I am reporting this on 16-Sep-2019 and this ticket was first opened in Nov-2018. My cpanel is on version 82 (build 14. [root@srv local]# /usr/loc...
-
ad682005 commented,
Hi, The below things have worked for me. Let this be input for anyone who is facing the yahoo temporarily deferred message. The steps below assume that you already have the knowhow of blacklists, ...
-
ad682005 commented,
Hello @cPanelMichael Apologies for no response for such a long time. All issues are fixed.
-
ad682005 commented,
I have come to the conclusion that this is a specific issue with a particular hosting provider. WHY did I conclude this? I setup another server with exact same configuration/specs with another ho...
-
ad682005 created a post,
Messages get automatically deleted from exim queue without retry
Hi, I have been facing an issue with a new setup that I did. Specs: CentOS 7 Cpanel 11.0.78 (RELEASE BUILD as of today) I have configured exim to queue messages if more than 19 messages are sent...
-
ad682005 commented,
ADDENDUM TO THE ABOVE ISSUE: I had manually added the entry under handlers section in suphph.conf application/x-httpd-ea-php72 = "php:/opt/cpanel/ea-php72/root/usr/bin/php-cgi" After that when I ...
-
ad682005 commented,
This is not an issue - I asked my component provider to send me update version of component so that I don't need mcrypt. Thanks so mcuh
-
ad682005 commented,
I have the same issue. How come? 2017 maintenance release would have been released long time back? I am on Centos 7.3 WHM 62 (build 24) How can I get this resolved? ADDENDUM TO THE ABOVE ISSUE: ...
-
ad682005 commented,
I have the same issue. How come? 2017 maintenance release would have been released long time back? I am on Centos 7.3 WHM 62 (build 24) How can I get this resolved?