Hi, Atheer

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

Can you please tell me do you have the latest Amelia version?

We had a bug to a very similar issue that you described here; and it got fixed in the meantime.

If you have the latest version, and you still have error 403 ;

it might be an issue with read/write permissions somehow got improperly set on the hosting side.

Here is a useful article about this error.

The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.

You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.

Can you please contact your hosting provider to check if you have an issue with your permissions?

Once you do that please let me know how it goes and if the issue persists.

-

I can then take a look at the WP Admin remotely, if you wish,

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.