shift8

This is still indeed maintained. The SSL certificate issue will be resolved shortly.

Hello,

Is this issue still happening for you? If so can you share the actual test URL you are trying? Its possible your web host may be interfering with the CDN endpoint’s ability to fetch the asset.

Thanks!

There are many many reasons why this would happen. Are you able to provide the test URL that the plugin provides in the main settings page?

Two of the most common reasons why this would happen :

1. The settings for the site url doesnt match your url. Note that “site.com/” and “site.com” are treated differently by the system. Make sure the url defined in the CDN dashboard settings matches exactly what your site url is.
2. Your web hosting provider is blocking our CDN endpoints mistakenly thinking it is automated bot traffic

We can try to rule out the issue. Step 1 would be to provide the test URL so I can see what is happening.

Thank you

For anyone else curious and slightly more intermediate with MySQL you can just run this query to bulk delete all the redirects from your database. Tested in multiple environments, just be sure you take backups before just in case :

delete from wp_options where option_name = '301_redirects' limit 1;

Its all JSON encoded serialized data in that one row in wp_options.

Hello!

First make sure that you are using the most recent version of the plugin.

Then under “CDN Settings” tab within the plugin settings, you should be able to enter the URI path of each item you do not want to be served, like the following example :

/wp-content/uploads/2023/09/name-1800x1800.jpeg
/wp-content/uploads/2023/09/logo-light-1.png

Hope this helps!

Resolving the issue for now – happy to revisit if needed

Hello,

An update to the plugin has been pushed out earlier today to resolve this critical error. If you ensure that you are running v1.68 at a minimum then it should resolve the issue for you.

Thank you

I should note that also entire file extensions should be possible with this, but your original (.*) regex wouldnt work, for all mp4 files you could do the following :

*.mp4

On a single line in that setting

I have verified the bug that you initially outlined here. I have to thank you for taking the time to submit this information as with people like you engaging in support you are improving the quality of the free software.

The ignore url text area in the CDN Settings of the plugin should now properly be processing one URI to ignore per line. It accepts a single asterisk as a wildcard if you wanted to pattern match a partial filename , for example these two lines would work :

/wp-content/uploads/2023/06/IMG_6110*
/wp-content/uploads/2023/12/Screenshot-from-2023-12-20-14-04-13*

Please update your plugin to v1.66 and let me know if the issue is resolved for you. Happy to troubleshoot further if needed.

Really – I’d have to verify this on my side and see if there is an issue with the exclusion logic.

Hey there! Sorry about the delay in responding. Supporting free software is a challenge but I’ll try my best to accommodate

I think adding a line in CDN settings to exclude /wp-content/cache/(.*) should work – does it not for you?

If it does not its possible that the URLs that are being rendered are being interfered by another plugin

Hello,

I believe the issues in the support ticket were resolved so I am closing this issue now. Feel free to contact directly or open a new ticket if you would like further assistance.

Closing issue for now, feel free to reopen or contact directly if you want us to troubleshoot further

Thank you this is added to the roadmap

Hello!

First of all sorry to hear you are having these problems!

I just tested the endpoint that would be serving the Hong Kong region and it is indeed working for me. Can you provide the CDN prefix or the URL that you are attempting to serve through the CDN that is generating the 502 bad gateway error?

I’d like to emulate the exact conditions that you are experiencing. If at all possible just click the “support” tab in our plugin settings and paste the debug information that is collected there. This will help me understand the environment that is being used that produces the problem.

Thank you!