Support

Akeeba Backup for WordPress

#31439 – access forbidden 403

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.
Tuesday, 11 June 2019 17:04 CDT
Hello, I am unable to run Akeeba. I keep getting a 403 Access Forbidden Error. This is the first time I'm seeing this.
Custom Fields
WordPress version (in x.y.z format) 5.2.1
PHP version (in x.y.z format) 7.1.30
Akeeba Backup version (x.y.z format) 3.5.1
ktjscm
Wednesday, 12 June 2019 01:47 CDT
Akeeba Backup for WordPress has strict access control which only allows the most trusted levels of site users to access its interface: Administrators on single site installations and Super Admins in multisite installations. First check that you are accessing Akeeba Backup as a user of this Role.

Furthermore, these checks are performed by checking the user's Capabilities, not their Role. If you get an error about not having adequate permissions to access this page it's Akeeba Backup telling you that your user does not seem to have the necessary Capabilities. I've seen that twice before, once four years ago and once more yesterday. In both cases it was a problem is with mapping capabilities to user roles in WordPress. This can be manually fixed using a plugin such as Members to fix Capabilities to Role mapping.

Please note that Capabilities to Role mapping is never, ever touched by Akeeba Backup itself. We do NOT change anything like that on your site. However, other plugins and even some themes do. It's very likely that one of the plugins or themes you installed did something stupid during installation, e.g. overwrite the "Administrator" Role's capabilities instead of adding to them, or directly manipulate the wp_user_roles entry in the wp_options table (containing a serialized data representation of the Role to Capabilities mapping) instead of going through the WordPress API. Finally, if you used a theme's prebuilt "quickstart" site to start developing your site it's possible that the problem simply existed on the prebuilt site.

If you did not get an error message stating you do not have adequate permissions please enable WordPress' debug mode and access the page again. It should now print much more information. Either copy and paste it here or save the page as a PDF and attach it to your next reply. It will tell us exactly what was going on when the error page appeared. For example, you may be having an issue with cookies on your browser which causes the session identifier to be reset on every page load, rendering most features of Akeeba Backup inoperable (for very good security reasons; it's the same reason WordPress uses nonces to prevent cross site scripting a.k.a. XSS attacks).


Nicholas K. Dionysopoulos

Lead Developer and Director



Greek: native

English: excellent

French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



nicholas
Wednesday, 12 June 2019 06:51 CDT
Here is what is generated in debug mode ( I replace actual site name with _SITE_/_SITE_):


Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 95

Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 96

Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 97

Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 98

Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 99

Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 100

Notice: Trying to get property of non-object in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/Solo/Application/UserManager.php on line 101
403 Access Denied


Please submit the following error message and trace in its entirety when requesting support

403 :: Access Forbidden in /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/app/Awf/Dispatcher/Dispatcher.php L 117
Debug backtrace

#0 /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/app/Awf/Application/Application.php(248): Awf\Dispatcher\Dispatcher->dispatch()
#1 /var/www/vhosts/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/boot_webapp.php(39): Awf\Application\Application->dispatch()
#2 /var/www/_SITE_/_SITE_/wp-content/plugins/akeebabackupwp/helpers/AkeebaBackupWP.php(421): include_once('/var/www/vhosts...')
#3 /var/www/_SITE_/_SITE_/wp-includes/class-wp-hook.php(286): AkeebaBackupWP::boot('boot_webapp.php')
#4 /var/www/_SITE_/_SITE_/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array)
#5 /var/www/_SITE_/_SITE_/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#6 /var/www/_SITE_/_SITE_/wp-admin/admin.php(253): do_action('toplevel_page_a...')
#7 {main}
ktjscm
Thursday, 13 June 2019 02:38 CDT
It looks like your WordPress installation is broken. Based on this debugging information, the problem occurs right after we've called WordPress' get_userdata() function. This is supposed to give us the information of the logged in user. However, WordPress returns no user data as if you are not logged in or the user you are logged in does not exist. As a result, Akeeba Backup cannot determine your user's capabilities and takes the safe and secure approach of denying access to itself.

Now, why would WordPress think that you are not logged in when you are? The only plausible explanation is that a third party plugin is doing something wrong. Apparently it's a plugin that loads before Akeeba Backup but after any other third party plugins which currently work correctly on your site. Unfortunately there's no way to define the load order of plugins or even view it. The only thing you can do is try disabling plugins one by one to find out which one is breaking WordPress.


Nicholas K. Dionysopoulos

Lead Developer and Director



Greek: native

English: excellent

French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



nicholas
Monday, 22 July 2019 17:17 CDT
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
system
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Cookies Notification - Action required

This website uses cookies to provide user authentication and improve your user experience. Please indicate whether you consent to our site placing these cookies on your device. You can change your preference later, from the controls which will be made available to you at the bottom of every page of our site.