Backup stuck at creating a job

I tried the plugin also on an 2nd domain and get the same result
Both stuck at 17%

Initializing…
Creating a job to start Backup

I checked the scheduled actions and could not find any related to the plugin
The 2nd domain is not even active and does not have plugins installed except for maintenance plugin.

Some site health info

A scheduled event has failed
The scheduled event, action_scheduler_run_queue, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.


The REST API encountered an unexpected result
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

When testing the REST API, an unexpected result was returned:

REST API Endpoint: https://DOMAIN.com/TEST/wp-json/wp/v2/types/post?context=edit
REST API Response: (403) Forbidden


Your site could not complete a loopback request
Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

The loopback request returned an unexpected http status code, 403, it was not possible to determine if this will prevent features from working as expected.

Hope this helps to fix the issue

Kind regards

Hello,

For those who may have faced the same issue, the issue was caused because of Cloudflare, whenever the issue is related to 403 error most probably the issue is because of some kind of firewall at some layer.

The issue was resolved by whitelisting the IP of the server where the website is hosted in Cloudflare Security settings Tools tab.

Regards,
Backuply Team.

Hi All
I’m having the same issue, stuck at 17% on the initial backup.
The site I’m working on is in development and I’m viewing it using a modified local host file.
My hosting says that the site isn’t set tp to use Cloudflare so what else could it be?

Thanks
Andy

@backuply

Yes I can confirm that after whitelisting a specific IP the issue was resolved.
In my case it was a specific IP (not sure it was cloudflare ip) but I could see it in a report on cloudflare.
Whitelisting this specific IP fixed it.
As far as I remember it was the sever hosting IP that needs to be whitelisted in CLoudflare WAF (free plan)

Click the website in CLoudflare go to security and then events to get the IP

• This reply was modified 1 week, 5 days ago by dgrl.

Hello @andyjay2012 ,

We are sorry for the inconvenience caused, the issue is because of the modified host file, as your Computer know where the IP is pointing to but the server you are hosted on is trying to resolve the domain which must be pointing to some other IP, and when creating a Backup Backuply creates a request to itself to initiate the backup which is sent through the server you are hosted on which is connecting to the true IP of that domain, as the URL for the request is created using the domain of the website and not the IP.

Regards,
Backuply Team