Forum Replies Created

Viewing 15 replies - 346 through 360 (of 397 total)
  • Forum: Plugins
    In reply to: [Shift8 CDN] Lost API key
    Plugin Author shift8

    (@shift8)

    No worries at all! I really should get on this dashboard account system for people to manage their sites in one place, its not ideal to expect people to save things this way.

    Can you let me know the site or email it to [email protected] ?

    Thanks

    Plugin Author shift8

    (@shift8)

    Steve,

    I replied to you directly. We have changed the browser caching from 30 days to 1 year as a result of best practice recommendations by google.

    No idea why 1 year is the magic number but at the very least this will help you score a higher score with the pagespeed type scanning services.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Steve,

    Would you mind providing your site URL, or send it in an email to [email protected] ?

    I wouldnt mind running that test to see those messages.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Steve,

    I’d be curious what they recommend. If google recommends a year for expires then I would be inclined to put that in across the board.

    Is there any way you can dig deeper to that recommendation to see what the best practice is?

    Thanks

    Plugin Author shift8

    (@shift8)

    the same for me. Website: jonathabarbosa.xyz.
    Please disable it so that I can enable it.

    Okay this is done

    Plugin Author shift8

    (@shift8)

    Hello,

    Do you mean you want a vanity URL for the CDN?

    Perhaps if I add a second tier of service for some premium functions , I would consider this but for now the CDN url for all sites is randomly generated and stored in a database.

    The CNAME for the cdn is handled automatically by our CDN servers, API system and the SSL cert is a wildcard cert that we manage internally. Unfortunately customizing the CNAME isn’t possible.

    Plugin Author shift8

    (@shift8)

    Hello,

    Can I check with you, the configure is correct:
    In Shift8 CDN Settings> Site URL : https://(my Shift8 CDN Prefix).wpcdn.shift8cdn.com
    OR simply my site: https://my domain.com ?

    The Site URL should be https://www.yourdomain.com , not the CDN url. That would be stored internally and isnt needed to be entered manually usually.

    Under WordPress General Settings:
    Wordpress Website (URL): I am still using my own site url
    Site Address (URL): I am still using my own site url

    If your site URL changed AFTER you set up the CDN then the CDN needs to be un-registered and re-registered with the new URL.

    Am I correct? or any other configure I have miss up (eg. in .htaccess ?)
    My host is Nginx.

    The CDN plugin will handle all the rewrites of static assets to go through the URL. Sometimes another caching plugin may interfere with this process like WP Rocket or W3 Total cache, especially if they were configured to use another CDN previously.

    I can look further to make sure your CDN is working if you want to send your site URL to [email protected]

    Thanks!

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

    (@shift8)

    I’m going to close this issue for now – please feel free to open a new issue if the CORS issue persists

    Plugin Author shift8

    (@shift8)

    Apologies for the delay. I have increased the default expires setting from 1 day to 7 days for static assets and 5 days to 30 days for anything in the wp-content/uploads folder, pending the implementation of this as a setting that people can control.

    Hopefully this alleviates the issue a bit while we transition to a more settings-based system

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

    (@shift8)

    Hello,

    Modifications to our infrastructure have been made to interact with the headers being set in a more controlled way. I believe the Access-Control-Allow-Origin was not being cleared properly and/or was being appended to a previously set header (potentially).

    Now all requests through the CDN will have the Access-Control-Allow-Origin set to the origin URL.

    Please clear your browser cache and see if the CORS issue is still happening.

    Thank you!

    Plugin Author shift8

    (@shift8)

    Am I correct that enter my site url in the CDN Setting should be with https:// ? or simply mydomain.com?

    Enter the site URL , no URIs , so http://www.example.com will work, or https://www.example.com – basically whatever is available to access your site via URL.

    I just logged into my admin, and I see the url come out with something like this: …./api/…. does it means my admin is already in your CDN?

    When you first install the plugin , it takes whatever site URL is defined in wordpress and auto-populates it in that field. You can change it if you like. If you URL changes in the future, just click to disable the plugin, then click “unregister” before you change the url. Then just register as a new site moving forward and it should work for your new site url.

    In the future I would like to create an external dashboard for people to login , see their bandwidth and manage their sites. Right now some people forget the API key or accidentally uninstall and wipe the settings and need me to get to manually activate. All possible but I wouldnt mind making it more convenient for people. Just keep that in mind 🙂

    Thanks

    Plugin Author shift8

    (@shift8)

    My site has around 4000 products, can it take longer time to rewrite?

    No this rewrite is on a per-request basis, its not a queued change or a scheduled change. The CDN will cache a URL request after the first request is made so subsequent requests are cached.

    I have Firewall, can the firewall block it:)

    Its possible, but the rewrite will at least happen first and you should see the URLs change in the static assets for your site first and foremost. If you are trying the test URL (From the settings page) and your browser just sits there waiting, its possible that your firewall could be blocking the reuest. I should note that this is unlikely to happen – the request for static assets are not likely to be considered malicious.

    Also, I have other cache plugin that asking to fill in the CDN path, shall I leave them blank?

    Yes – other caching plugins may be trying to rewrite the URL the same way our plugin is doing. It might be best to rule them out by deactivating those other CDN plugins to ensure no conflicts are happening.

    Let me know how it goes!

    Plugin Author shift8

    (@shift8)

    Hello,

    Though there is no pro or commercial version of this product (it is 100% free), you can send an email to [email protected] and I can assist you further there. The issues described in this forum post are specifically how the free plugin’s infrastructure is potentially settings or processing headers relating to caching.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Hello!

    Is the CDN enabled in the settings?

    Does the test URL work (the link to the test url is on the settings page for the plugin)

    I haven’t extensively tested our plugin with Jetpack so I cannot comment on that , however if the plugin is activated, registered and turned on then the plugin will rewrite all static URLs to our CDN automatically without you having to do anything.

    Let me know the answers and hopefully we can help you figure it out.

    Plugin Author shift8

    (@shift8)

    I have to double check our system but I think that might be a header thats set and sent by the origin server (your server). Can you check to see if that header is being set on non-cached files from your server perhaps?

    I’ll do some research on our side and make sure its not something we can accommodate as well.

Viewing 15 replies - 346 through 360 (of 397 total)