shift8

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!

Ok our merchant service is sending those out so we’ll look into the email notifications through that service.

I’ll wait to hear back from the originating issue in this thread and we can assist with troubleshooting.

Our support email was never what was listed here in this message, not sure where you got that email address.

Regarding the originally reported issue, it would be immensely helpful if @mediciner could provide the originating URL that is being requested that generates the SSL error.

There are a multitude of reasons why this might happen to a person, but the expiration date of our SSL certificates is currently May 2024

Our CDN endpoints , in order to connect, may have a baseline best practice minimum requirement to consier an SSL connection valid. I’m happy you were able to figure out the issue!

If I use Qualsys SSL Labs free online SSL checker, and enter your website address, the attempt just times out.

Then I found another free SSL certificate checker and ran it against your site, it works and validates correctly. So maybe my original assessment is still happening somehow. Your welcome to double check but the first thing I always check when looking into these types of problems is can I just wget that test file directly from the command line of one of the CDN endpoints, and I cannot so that usually rules out a lot.

Hello,

The backend proxy fetch is failing resulting in the 502 gateway error. If I just try to wget the test file from your site directly, this is what I see :

curl -v <your site>/wp-content/plugins/shift8-cdn/test/test.png
About to connect() to <your site> port 443 (#0)
Trying x.x.x.x…
Connected to (x.x.x.x) port 443 (#0)
Initializing NSS with certpath: sql:/etc/pki/nssdb
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
NSS error -12190 (SSL_ERROR_PROTOCOL_VERSION_ALERT)
Peer reports incompatible or unsupported protocol version.
Closing connection 0
curl: (35) Peer reports incompatible or unsupported protocol version.

Looks like an SSL configuration issue on your side?

Hello,

As per my previous response , it looked like your web host was mistakenly identifying the CDN “fetch” request as automated bot traffic and blocking it.

Its best if you reach out to your web hosting provider to remove this security option. If they request a list of IPs to whitelist, let me know and I can send that to you directly.

Hello!

Apologies for the issue you are having. We see this from time to time because some web hosting providers try to maximise resource allocation by trying to “detect” automated traffic from IP addresses that they dont feel is legitimate traffic.

Sometimes this happens to our CDN (And others I’m sure). Each CDN endpoint will “fetch” the request from your web host and store it in memory until it expires. The fetching that happens may be considered automated “bot” traffic by your web hosting provider.

This doesnt happen for all endpoints, but the busier ones may hit whatever threshold your web hosting provider has, as is evidence when I check one of our endpoints to try to get your website :

Resolving <your website> (<your website>)… x.x.x.x, ::1
Connecting to <your website> (<your website>)|x.x.x.x|:443… failed: Connection refused.
Connecting to <your website> (<your website>)|::1|:443… failed: Network is unreachable.

You can reach out to your web host to confirm this. They may ask for a list of IP addresses to whitelist , depending on your policies. You can contact us directly or message here if you need that list.

Thank you!

You can import events using Pro

How do you export events using pro?

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.

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!

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.

Hello,

This issue should now be resolved – thank you!

Thank you for the kind words!

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!