webdash

Thanks, I’ll give it a try and observe for a few days

Hi – I was just wondering if you had made any progress resolving the ESI issue you mentioned above, as I am still experiencing the problem in OP.

Kind regards

Dave

Appriciate the update, hopefully the fix will help when it’s ready.

Hi – unfortunately, after a few days of not occuring the issue has returned.

Any further suggestions to resolve this would be much appriciated.

I have created a new report: Report number: ECXYMQBH

many thanks Dave

– fingers crossed that fixes it.. thank you so much.

I’ve got this issue on several sites using LSC + DE, but I haven’t been able to leave the error in place to make a report.

done – time to wait and observe after crawl?

figured it out..

there are 2 x php files calling that and 1 js..

the php in the files is :

function divi_filter_loop_enqueue_scripts() {

    $ajax_nonce = wp_create_nonce('filter_object');



    wp_enqueue_script('divi-filter-loadmore-js', plugins_url('../../../js/divi-filter-loadmore.min.js', __FILE__), array(

        'jquery'

    ), DE_DF_VERSION);

    wp_localize_script('divi-filter-loadmore-js', 'loadmore_ajax_object', array(

        'ajax_url' => admin_url('admin-ajax.php'),

        'security' => $ajax_nonce

    ));

I’m not exactly sure how to do that? do you have any suggestions?

I did find a reference to that spcific term in a js file in the plugin – would that be relevant at all?

Hi, the page linked at the top of the post has the issue – need to do a sort (of the blog posts) to trigger the 403 showing.

here you go, thank you.

Report number: ZUSHMTXH

Hi – was this ever resolved?

I have the latest version installed and currently having this issue…

thanks

Dave

Thanks for the response Peter.

I disabled my litespeed cache, then toggled throught the IP detection options, starting a scan on each to see if it would resolve. When I went back to the default option, the scan got further (past the ‘server state’ check), but failed with a cron key error and retry fail while testing files.. I changed the number of attempts to 5 and sucessfully completed a test.. reactivating litespeed cache, i have sucessfully run another test.. so looks like all good now.

guessing the issue must have been something provider-side as you suggested.. using litespeed and quic.cloud for reference.

appriciate the assistance, markig as resolved, will come back to you if anything presents as an issue.

Kind regards,

Dave

Hi. Thanks for the response.. both the site address and the wordpress address are https.

I have no other issues with https on the site, everthing appears to be working as it should except scheduled Updraft backups

It’s very odd! as i mentioned above if I manully trigger a backup the email notification and database backup are both https, the scheduled backup creates http..

Kind Regards, Dave

Hi David, thanks for the reply.

Yes, in the log and the notification email I receive to confirm the backup status always reports the site as http if the backup was created by the scheduled run.

If I create a backup by clicking ‘backup now’ in the updraftplus backup/restore dashboard the notification/log reports https.

If i try to restore the database from a ‘http’ backup, updraft gives warnings about the database not using the correct protocol.

Warnings:

This backup set is of this site, but at the time of the backup you were using http, whereas the site now uses https. As long as your web hosting allows http (i.e. non-SSL access) or will forward requests to https (which is almost always the case), this is no problem. If that is not yet set up, then you should set it up, or use the migrator add-on so that the non-https links are automatically replaced.
You can search and replace your database (for migrating a website to a new location/URL) with the Migrator add-on – follow this link for more information`

The site is all https, I’ve tried uninstalling the plugin and reinstalling, but made no difference.
I know in an emergency I could probably still use the ‘http’ backup, but if possible i would like to avoid this, and identify what is casuing this issue.

Please let me know if you need any further information.

Kind Regards
Dave

Thanks for the reply Bryle – it’s a single site.. not a migration.

The only diference is that scheduled backups (for some reason) create a http backup, whereas if I run the backup manually (from the same site/installation) it creates a https version (which is what I want.)

kind regards,
dave.