Support

Akeeba Backup for WordPress

#30875 no permission to access admin idrivesync

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

WordPress version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by tampe125 on Monday, 04 February 2019 04:32 CST

damnsharp
Hi Nicholas,
Suddenly on all sites where I have set-up Akeeba back-up to upload files to iDriveSync I get the following message after back-up is finished:
The backup operation has been halted because an error was detected.
The last error message was:
You don't have permission to access /wp-admin/admin.php on this server

When I let Akeeba back-up local there is no problem.

What could be the problem?
Please also see attached image for the screenshot of settings.

Thanks!

tampe125
Akeeba Staff
Hello,

can you please attach the log of the failed backup? So I can take a look at what's going on during the backup process.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

damnsharp
Hi Davide,thanks for quick reply. I will attach the log file.
Also when I run a configuration check I get this error:
"Akeeba Backup for WordPress detected that your server requires a maximum execution time that is too low to be practical. You are better off switching hosts or asking your host to increase PHP's maximum execution time and lift any CPU usage limitations from your account."

tampe125
Akeeba Staff
Yes, that was what I was afraid of.
Your host is imposing very low limits on CPU usage: if you exceeding them, you get temporary blocked.
Now, let's start to tweak your configuration to optimize everything. Please try these suggestions one by one, if they work, there's no need to apply the next one. That's because every change will make your backup process slower (so it will require fewer resources), but let's try to avoid making it dead slow.

  1. Exclude folders wp-content/uploads/cache and wp-content/cache from the backup. Looking at the logs, there's only temporary data, which we can safely ignore.
  2. Double check that the Site Engine Scanner is set to Large site scanner
  3. Inside the Archiver Engine settings, set the Part size option to 20Mb
  4. Use the following timing settings: Minimum execution time 5 seconds, Maximum execution time 3 seconds, Runtime bias 50%. Yes, minimum is greater that maximum, that's not a typo.


Give it a try and tell me if those suggestions did work for you.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

damnsharp
Hello Davide,
I will try the steps.
It's still strange because several sites are on the same hosting server.

Can I ask my hosting company to change anything? I know them well so they can change things for me.

damnsharp
Step 1 and 2 did not change anything.
Step 3 I got a message after changing that value to 20:
White screen with message:
Forbidden - You don't have permission to access /wp-admin/admin.php on this server.

tampe125
Akeeba Staff
I was writing this while your new answer was posted:
Yes sure, you can ask your host to take a look at it. Usually hosting companies aren't very inclined to perform changes, but I glad to see there's an exception from time to time!
However, I'd strongly suggest you to apply the first 2 points of my bullets list: you really don't need to save cache data (it will only take space and time since it will be generated again form scratch) and you should double check that the scanner is the correct one, since it will speed up the whole backup process.

------
Please try to lower the execution time AND to contact your host. It seems they are banning the user that's requesting the same page too many times in a small timeframe, usually it's a security setting to prevent DOS attacks.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

damnsharp
Hi Davide, your last sentence made me wonder, maybe I was too quick to back-up several sites which are on the same hosting platform.
"It seems they are banning the user that's requesting the same page too many times in a small timeframe, usually it's a security setting to prevent DOS attacks."
And indeed, when I let one site first completed the configuration wizard again (just to make sure) I got the message: Finished Benchmarking
Next I started the back-up and it went o.k.!

I waited 5 minutes and did the same on another website and also it went o.k.!

damnsharp
oh, apparently this ticket is Private but it is o.k. if you can change it to Public. Maybe it is useful to someone else.

tampe125
Akeeba Staff
If you're Ok with that, I'll make this ticket public, so it could help other people struggling with the same problem.
And yes, it's always a good thing to avoid updating/backing up all the sites at the same time, since you could hit resource usage limits. I had the same exact problem with RAM usages.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!