dgrl

@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, 4 days ago by dgrl.

This thread can be archived I will make a new one with more details

It seems like regenerating images using the OOTB function (Woo) fixed the issue I was facing.
although it takes a lot of time (260 images in 22 hours) all these images are now served as AVIF.
I have to regenerate the theme images and will do that after woo is finished.
I will update this threat if both processes are finished

I’m kind of bamboozled here now.
A few entries are still connected????
In the screenshot you see original generated images and dark blue size box of the plugin….

https://snipboard.io/iTRlIN.jpg

Did I broke the plugin or my WordPress install again?

Same directory different file is disconnected
https://snipboard.io/Z7tWRL.jpg

• This reply was modified 1 month ago by dgrl.
• This reply was modified 1 month ago by dgrl.
• This reply was modified 1 month ago by dgrl.

In the screenshot below you can see a good example
All the images where auto created using the plugin when the image was uploaded to the product
As I mentioned before I just unchecked all sizes except for WOO 495×495 to regenerate
After that the word SCALED was placed in the filename and all original are ignored (light blue box)
When regenerate ALL images it will just make new ones with the word SCALED in it.

https://snipboard.io/sFc2GL.jpg

I wonder why the images are created without the word scaled in it at first, why the link will be broken as soon as you uncheck the size in the plugin menu and why when regenrating the original is ignored?

Hi @vmarko

Thanks for the help
I will try different settings. As this is only happening as soon as I turn Minify on

Kind regards

Hi

Thanks for the answer
This seems to solve the 2 errors yet it introduces 3 new ones
Any idea why this is popping up?

Here you have all info

I just turned it on again..

Kind regards

Got ya.

Thanks for all the info and responses.

I think this is resolved for now ‘:-)

Hi

Thanks for the answer

I am not using Jetpack theme at all?
Does this mean I need to buy jetpack theme to use this feature?

Kind regards

Hi

I just found out that the image is present in 2 folders.
Same name different picture

1 is in uploads 2021/01 the 2nd one is in uploads 2024/02

Only the first image is present in the plugin.
Maybe you can share an email so I can send you a screencast

I happen to find other small issues

1 example is that the “button” in the image field are not clickable when browser is big
When I make the screensize of the browser smaller and hover over the button a small screen popsup with info like size and retina pending;….

Hi

I think you should check your hosting firewall settings or if you use cloudflare check it there.
I just installed this plugin first time. After removing my XML map from google search console
Added the XML after making with this plugin… Got fetched within 10 min.

I checked the sitemap inside Google Search Console and it matches the settings from the plugin.

Still have to see how the outcome will be in few weeks, So far it seems to be good.

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

@threadi

Thanks for the help

Hi @threadi

I am just using the build in editor of WP and the astra theme

No other plugins etc.