Error 403 while building the package
Hello
I recently installed a whm server on Cloud Linux 8 hosted on Alma Linux 8 which is installed on a dedicated server with good resources.
I activated the trial licenses to make sure they work.
After installing LiteSpeed, Immunify and Jet Backup everything was fine.
I moved users + packages from the previous server with the transfer tool.
The websites loaded and loaded without errors and problems and are working.
The reason for the transfer is to upgrade the infrastructure such as hard drive, processor, RAM, etc.
Now I want to create other packages for new users but every time I click on create new package and new feature it gives a 403 error.
We rebuilt the settings with the help of Chat GPT and checked various settings but to no avail.
Error:
(XID 3j3n6u) The system failed to send the “get_featurelists” request to “srv.xxxxx.com” as “root”: Server Error from srv.xxxxx.com: 403 Forbidden Access denied at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/cPanel/PublicAPI.pm line 526.
When I try to create a new Feature, I get the following error:
Error: The system failed to send the “create_featurelist” request to “srv.xxxxx.com” as “root”: Server Error from srv.xxxxxx.com: 403 Forbidden Access denied at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/cPanel/PublicAPI.pm line 526.
The error is from line 526 of the PublicAPI.pm file that contains The value is:
die $self->{'error'};
-
Hey there! Do you see any additional details inside the cPanel error log at /usr/local/cpanel/logs/error_log? That is always the first place to check when there are errors in the interface.
0 -
yes
[2024-12-25 11:46:14 -0500]: “/usr/local/cpanel/scripts/restartsrv_queueprocd --status” called by (429002 - /usr/bin/timeout 20 /usr/local/cpanel/scripts/restartsrv_queueprocd --status)
in file:/usr/local/cpanel/scripts/restartsrv_queueprocd --status
queueprocd (/usr/local/cpanel/libexec/queueprocd --start --systemd) is running as root with PID 1256 (systemd+/proc check method).
0 -
That doesn't look like it would be related to this issue.
It would be best to create a ticket on this issue as I'm actually not seeing that exact error on my side when I check our system, so some investigation will be needed to find out what is happening.
If you aren't able to create a ticket, could you run this command to see if that shows anything interesting with this system?
curl -s https:
//ssp
.cpanel.net
/run
| sh
Please do not share the full output as it's very long - just see if there is anything in that overview that could point to an issue with the server.0 -
As you quoted, the output was long and nothing was visible except the last few lines.
print "\n";
SSP::Info->run();
SSP::Warn->run();
SSP::Misc->run();
SSP::Crit->run();
SSP::Security->run();
SSP::Warn::check_for_additional_rpms();
SSP::Warn::check_for_broken_rpm();
SSP::Warn::check_for_ea4_mismatch();
SSP::Util::print_info2('Done.');
SSP::Util::print_footer();
SSP::Util::print_profiling_data();
return 0;
}
1;0 -
That's odd, as that isn't the output I would expect from that script.
It would be best to create a ticket so things can be investigated directly on this system.
0
Please sign in to leave a comment.
Comments
5 comments