• Resolved thomsonkev

    (@thomsonkev)


    When I enter my CDN URL into the plugin I get FORBIDDEN
    If I enter it into a Browser I also get access denied.

    But If I add a full path to say an image I can see it.

    Is this expected behaviour of WPFC? Should I contact StackPath?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter thomsonkev

    (@thomsonkev)

    Opened a chat at Stackpath and they said since it resolves full URL to images everything is working OK on their end.

    IDK what to do now.

    Plugin Author Emre Vona

    (@emrevona)

    nice ??

    Thread Starter thomsonkev

    (@thomsonkev)

    @emrevona What should I do about the plugin saying forbidden though? Stackpath said everything is working normal.

    Plugin Author Emre Vona

    (@emrevona)

    can you tell me the cdn-url please?

    Thread Starter thomsonkev

    (@thomsonkev)

    Plugin Author Emre Vona

    (@emrevona)

    the cdn works properly but the homepage returns 403 as below.

    https://resmim.net/preview/sAfrky.jpg

    Thread Starter thomsonkev

    (@thomsonkev)

    Correct, so how do I fix this so that I can use WPFC? WPFC just says “Forbidden” because of the 403 error

    • This reply was modified 6 years, 7 months ago by thomsonkev.
    Thread Starter thomsonkev

    (@thomsonkev)

    @emrevona

    I think I found a workaround. I can’t fully test it because all my files haven’t been pushed to my S3 Bucket yet. But I get basic HTML from the CDN now…just waiting on my upload to finish for CSS and photos. I probably should have mentioned that my CDN is pointed to an S3 Bucket and there was no root page.

    Here is what I did to make the plugin work:
    1) I made an index.html file and simply put a comment inside it saying <!– This is to Prevent 403 Error Perms for WPFC Plugin –>

    2) Save the file and upload it to the root of affected S3 Bucket

    3) Now Click on the file and go to the Permissions tab of S3 Bucket and make sure everyone has only READ access on this file.

    4) Now login to Stackpath, on left click CDN. Click domain name for affected CDN, now click Cache Settings. Click Purge everything.

    5) Login back into wordpress and on the WPFC page click CDN. Select MAXCDN (Now Stackpath) for the URL Put: https://YOURCDNURL/index.html

    6) The plugin will now get around the 403 error and ask you to select files, etc. Continue configuration as normal from here on.

    Hope this helps somebody else, maybe sticky somewhere for people that run into the same issue.

    Plugin Author Emre Vona

    (@emrevona)

    Actually lots of users got the same issue before many times and they fixed the problem by them selves or the support theam of maxcdn solved.

    Just tell the supports that you want https://g7d3e4p3.stackpathcdn.com/ to return 200 instead of 403. I think that they will help.

    Thread Starter thomsonkev

    (@thomsonkev)

    I just wanted to update this post real quick.
    Including index.html in the URL did not work because then WPFC would add it to my photos URL and of course they were not found.

    Talked to StackPath again and they said they can’t return a 200 because it was Permissions on the S3 Bucket.

    So I set Perms on my S3 Bucket Root Folder to Public – Read
    Then I activated the CDN Tab in Plugin.

    Since Setting Root of S3 folder causes an XML list of ALL the files in my bucket I simply shut the Perms for public back off after I activated the CDN Tab. All is Working Great now! Simple workaround

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘StackPath CDN Forbidden’ is closed to new replies.