The uploaded file could not be moved to wp-content
Hi All,
A user reported that he is unable to upload files and getting this error.
As far as I understand the reason is lack of permissions which need to be modified in File Manager.
However, in my case permissions are set to 755.
Please advise what else it could be.
Thanks.
-
When I tried to upload files manually I got
Tried to check disk usage but getting this:
Failed to fetch stat item: diskusage:_count at /usr/local/cpanel/Cpanel/API/StatsBar.pm line 58.
at /usr/local/cpanel/Cpanel/API/StatsBar.pm line 58.
Cpanel::API::StatsBar::get_stats(Cpanel::Args=HASH(0x2a47760), Cpanel::Result=HASH(0x2a475e0)) called at /usr/local/cpanel/Cpanel/API.pm line 360
eval {...} called at /usr/local/cpanel/Cpanel/API.pm line 362
Cpanel::API::_run_module_function(Cpanel::Args=HASH(0x2a47760), Cpanel::Result=HASH(0x2a475e0), "StatsBar", "get_stats") called at /usr/local/cpanel/Cpanel/API.pm line 242
Cpanel::API::execute("StatsBar", "get_stats", HASH(0x2a47328)) called at /usr/local/cpanel/Cpanel/Template/Plugin/CPDefault.pm line 81
Cpanel::Template::Plugin::CPDefault::_execute("StatsBar", "get_stats", HASH(0x28e3300)) called at (eval 6) line 1
eval {...} called at (eval 6) line 1
eval {...} called at (eval 6) line 1
Cpanel::Template::Shared::__ANON__(Template::Context=HASH(0x279b9a0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Context.pm line 349
eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Context.pm line 322
Template::Context::process(Template::Context=HASH(0x279b9a0), "resource_usage_block") called at (eval 5) line 10
eval {...} called at (eval 5) line 1
Cpanel::Template::Shared::__ANON__(Template::Context=HASH(0x279b9a0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Document.pm line 165
eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Document.pm line 163
Template::Document::process(Template::Document=HASH(0x27a9478), Template::Context=HASH(0x279b9a0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Context.pm line 352
eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Context.pm line 322
Template::Context::process(Template::Context=HASH(0x279b9a0), Template::Document=HASH(0x27a9478)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Service.pm line 94
eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template/Service.pm line 91
Template::Service::process(Template::Service=HASH(0x279b580), "/usr/local/cpanel/base/frontend/jupiter/diskusage/index.html.tt", HASH(0x279ad60)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/x86_64-linux/Template.pm line 66
Template::process(Template=HASH(0x279b1b0), "/usr/local/cpanel/base/frontend/jupiter/diskusage/index.html.tt", HASH(0x279ad60), SCALAR(0x1d3d298)) called at /usr/local/cpanel/Cpanel/Template.pm line 483
Cpanel::Template::process_template("cpanel", HASH(0x279ad60), HASH(0x1d44990)) called at cpanel.pl line 1105
cpanel::cpanel::cptt_exectag("/usr/local/cpanel/base/frontend/jupiter/diskusage/index.html.tt", 1) called at cpanel.pl line 4645
cpanel::cpanel::run_standard_mode() called at cpanel.pl line 928
cpanel::cpanel::script("cpanel::cpanel", "./frontend/jupiter/diskusage/index.html.tt") called at cpanel.pl line 3240 -
Checked quota and space used.
I don't understand what disk usage quota this error is related to?
0 -
Hey there! It seems like there could be multiple issues happening - one with the quota, and one with the interface. If you run "/scripts/fixquotas" on the machine, does that adjust the quota for the account at all?
You may also want to try a forced update with "/scripts/upcp --force" to see if that gets things working properly and resolves that interface error in the second post.
0 -
Hi cPRex
In my case cPanel hosts a number of websites for different customers.
If I run "/scripts/fixquotas" would that affect all websites?
0 -
Yes, that command is global and would affect all users. BUT - if other users aren't experiencing a quota issue, I wouldn't expect this to negatively impact them.
0 -
Thanks.
By the way I just realized I forgot to attach a screenshot.
This is what I get when try to check disk usage.
It is not loading and I can't see disk usage.
0 -
Was there anything helpful inside the cPanel error log at /usr/local/cpanel/logs/error_log while you load that page?
0 -
Not sure if I do it right but tail-n 20 error_log returns this.
0 -
You'll likely need to create a ticket on this one so we can take a look directly at the system, as I'm not finding much related to these errors on my end.
0 -
Do you mind to advise how do I create a ticket.
I've never done this before.
0 -
If your cPanel license is purchased through us, you would use the WHM >> Create a Support Ticket function. If the license is through your hosting provider, you would reach out to them and then they could escalate to us if necessary.
0 -
I can only see this in WHM >>Create a Support Ticket.
Does that mean I'm not entitled (have no license) to do create a ticket?
0 -
No, that means there is another error in the interface that we'll need to check out, as it seems this system has multiple issues.
0 -
Since you aren't able to create a ticket there, you can start by email cs@cpanel.net and that will get the ticket creation process started.
0 -
Is it possible to check disk usage for a specific website from command line?
I created a ticket but that wasn't helpful unfortunately.
0 -
Sure - you can run this for any user on the machine:
quota -u username
0 -
Thanks.
This is the output.
Is the bottom value (141046700) the current disk usage?
0 -
If you expand your screen a bit the columns would line up better with the column headers, which would help with the readability. This screenshot will help clear things up a bit:
But yes, that first number, 141046700 is the space used. It also might be easier to run "quota -us" to print this out in human readable numbers:
0
Please sign in to leave a comment.
Comments
18 comments