401 Access Denied on CPanel resources
This happens only to some accounts on the server.
When accessing cpanel, after logging in, the cpanel appears unstyled, after checking Chrome dev tools, I noticed that every requested resource has a 401 access denied response code. If I click on any link I am automatically sent back to the login page which means somehow cpanel logs me out before it even completes sending the first page. Any ideas what could be causing this? I tried switching the problematic accounts from x3 to paper lantern but the issue doesn't go away.
-
Force a cPanel update, clear your browser cache and / or try another browser, to narrow things down some if possible. 0 -
I already tried a different browser it gave the same results - even tried incognito mode which skips the browser cache. How do I force an update? Note that other accounts using the same theme do work fine. 0 -
You can force a cPanel update using this shell command: # /usr/local/cpanel/scripts/upcp --force
Do you have any rules defined in Home " Security Center " Host Access Control? You may be able to find more information about what is happening by watching /usr/local/cpanel/logs/access_log and /usr/local/cpanel/logs/error_log, while loading the page that causes the 401 error. You are welcome to submit a ticket using the link in my signature so that we can look at the server directly and try to find what is causing the 401 codes. You can post the ticket number here so we can follow up on it.0 -
Forcing update solves the problem temporarily but it seems like it returns later. I checked the log files and I found the following error: [2015-04-15 22:37:19 +0300] warn [Cpanel::Config::LoadConfig] Unable to open /var/cpanel/sessions/raw/xxxx:j9TwLP4TmtnzrS2iybIb3yqiL2Ikh5UQUIu6D7T148Z12Om7QF5O9L9DaYx6gzqp: No such file or directory at /usr/local/cpanel/Cpanel/Config/LoadConfig.pm line 215 I checked /var/cpanel/sessions/raw/ does exist. 0 -
Feel free to submit a ticket using the link in my signature, so that we can investigate directly and try to find the definitive cause of this recurring problem. 0
Please sign in to leave a comment.
Comments
5 comments