Forum Replies Created

Viewing 15 replies - 31 through 45 (of 397 total)
  • Plugin Author shift8

    (@shift8)

    Apologies for this issue!

    The most common reason for this happening is the site URL from what you enter in our dashboard versus whats defined in the plugin settings is very sensitive. For example :

    Plugin settings : site.com

    CDN Dashboard settings : site.com/

    Note the trailing slash above. The settings URL has to be absolutely identical in both spots , otherwise that error will happen.

    Forum: Plugins
    In reply to: [Shift8 CDN] Cors Problem?
    Plugin Author shift8

    (@shift8)

    Can you perhaps provide a link that we can see the problem or perhaps paste the entire CORS error message here for review? There could be a few factors that contribute to this.

    The CDN should be allowing your site URL domain as well as its own domain for its own CORS but your web hosting may also be adding CORS headers for your site url that could impact this, not to mention pixi.js as well. Seeing the full error will help of course.

    Thank you!

    Forum: Plugins
    In reply to: [Shift8 CDN] File Update
    Plugin Author shift8

    (@shift8)

    Hello!

    Apologies for the delay in response. The CDN leverages browser caching as well.

    Do you know offhand if the JS file had a version query string indicating the version? For example file.js?v=4.6. If this file is loaded by your theme you could wp_enqueue_style with a version defined in this function call.

    Defining a version will tell wordpress to add this query string which, for the CDN, will treat it as a new file and not cache or serve a cached copy.

    Thank you and apologies for the delay in response again. There is a cdn help email that you could try as well if you have problems in the future.

    Forum: Plugins
    In reply to: [Shift8 CDN] SSL Issue
    Plugin Author shift8

    (@shift8)

    Hello,

    This issue should now be resolved – thank you!

    Forum: Reviews
    In reply to: [Shift8 CDN] Lovely
    Plugin Author shift8

    (@shift8)

    Thank you for the kind words!

    Plugin Author shift8

    (@shift8)

    Yes indeed it is working! There are many reasons you may see a 502 gateway error.

    The most common reason is your web host may be blocking requests from our CDN thinking it is automated bot traffic.

    Some shared web hosting providers have these kinds of protections in place so that they can fit more people on a shared platform by mitigating what it thinks is automated traffic.

    The CDN “fetching” a static resource when a request comes in is quite normal for a CDN. A “502” (bad gateway) error means we tried to connect to your site via a CDN endpoint and your web host blocked the request.

    You can try to reach out to your web host to turn that sort of setting off, or if they ask to whitelist IPs you can email us directly and we can provide a list of IPs to whitelist. I’d start with them first.

    Hope that helps!

    Plugin Author shift8

    (@shift8)

    Closing for now – feel free to reach out should you want to troubleshoot further

    Plugin Author shift8

    (@shift8)

    Hello!

    This is a tricky one as elementor (and other page builders) may load assets via “lazy loading” or similar means.

    You could try disabling “lazy loading” in elementor to see if this fixes your problem. However I do know that google pagespeed scores offer bonus points if you use lazy loading.

    You should narrow down if this is indeed the cause first and let me know here. I’d be happy to analyze any page URL you are having trouble with to offer further insight because at this point its just guessing. Elementor is quite bloated in what it brings to the table so its difficult to say without checking the page in question.

    Thanks for the kind words!

    Plugin Author shift8

    (@shift8)

    The SSL for the website (only) uses Let’s Encrypt and the automated renewal process didn’t catch it between the few hours of when it expired and when the automated process would have run.

    This has been corrected moving forward – thank you for letting us know!

    Plugin Author shift8

    (@shift8)

    Closing this issue

    Plugin Author shift8

    (@shift8)

    Closing this issue , if you have more info or further comment you can either email directly or reply to this issue

    Plugin Author shift8

    (@shift8)

    Hello!

    I’m sorry to see you are having issues.

    Our CDN should only be rewriting urls to go through our systems that are static assets (media files, css, js, etc).

    What it looks like you are showing here is a HTTP POST request through WordPress’ admin-ajax , which isn’t designed to go through our CDN at all.

    I’m curious about your current setup with our CDN – are you able to go to the plugin settings and cut/paste the debug info?

    Thank you

    Plugin Author shift8

    (@shift8)

    I’m sorry you are having this issue! I’d be happy to help troubleshoot it for you.

    First of all, how are you determining that the CDN is slowing down your website? Can you please paste a link of the TEST url for the CDN for your site? Also please confirm the country you are testing from.

    Thank you!

    Plugin Author shift8

    (@shift8)

    Closing issue

    I am having an issue with this as well. Temporary workaround is to bypass the TML reset password links :

    /wp-login.php?action=lostpassword

    If you make a lost password request from the default WP password reset , it will generate an email with a link to the default password set screen.

    Granted just not using the plugin isnt the best solution, but at least it works for now. Hoping the plugin author reads this and issues a fix quickly.

Viewing 15 replies - 31 through 45 (of 397 total)