• Resolved planetboris

    (@planetboris)


    Hi, I recently enabled QUICcloud CDN with my site. I have been experiencing 403 forbidden page errors in the editor and in live preview, which I have never experienced with the site. Occurs randomly with different pages. Any ideas how to diagnose? Trying with host provider but they haven’t been able to solve the issue yet. Thanks and best regards

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Support qtwrk

    (@qtwrk)

    is that 403 error page from origin ? or from QC ?

    Thread Starter planetboris

    (@planetboris)

    Not sure, here is screenshot of the 403 page: https://postimg.cc/MMTdRgkQ How can I check?

    Plugin Support qtwrk

    (@qtwrk)

    that’s 403 from origin

    please check your server log , it will log the reason , most likely I would think some false-positive mod_security block.

    Thread Starter planetboris

    (@planetboris)

    Ok, thanks for confirming. Server support had disabled mod_security for troubleshooting. Logs indicate: “…..conn limit: 300, cur conns: 1, access denied ” so apparently the server thinks my site exceeded the limit per IP set to 300. They said it could be malware or plugin causing this. Are there any other reasons for that conn limit 300 to be triggered ? Site has not been launched publicly yet.

    Plugin Support qtwrk

    (@qtwrk)

    well , that’s more like server-side configuration , I am not very sure

    if you are using LiteSpeed enterprise or OpenLiteSpeed, please create a ticket in our ticket system by mail to support at litespeedtech.com , our server staffs will help you further on that regard.

    Thread Starter planetboris

    (@planetboris)

    That’s great, thank you for the support email . I forgot to mention last message, should I be concerned about the following message from my Site Health dashboard: The scheduled event, litespeed_task_imgoptm_pull, is late to run… ?

    • This reply was modified 2 years, 6 months ago by planetboris.
    • This reply was modified 2 years, 6 months ago by planetboris.
    Plugin Support qtwrk

    (@qtwrk)

    you can set up a system cron job to trigger wp cron , so to make sure it runs in time

    for example https://encode.host/knowledgebase/2014/How-to-create-Cronjob-via-cPanel.html

    Thread Starter planetboris

    (@planetboris)

    Thanks. Yes, I switched CRON from WordPress to cPanel over a week ago, that’s why I am a little bit concerned.

    Plugin Support qtwrk

    (@qtwrk)

    double check the output from cpanel cron , I have seen some cases that wget or curl request to wp-cron would end up in error

    Thread Starter planetboris

    (@planetboris)

    When you say check the output you mean check the log files?

    Plugin Support qtwrk

    (@qtwrk)

    does your cpanel have SSH access?

    how exactly do you set up the cron in cpanel ?

    Thread Starter planetboris

    (@planetboris)

    Regarding SSH access, I believe so, I’m currently with NameHero.

    I followed NameHero’s tutorial for setting up cPanel CRON. Added a new cron job to run once an hour with the wget command (also disabling WP Cron in PHP config)

    ——————-

    Also it you don’t mind I want to return to the 403 issue I had earlier. NameHero support said that I was being blocked by Quic,cloud so we decided to disable it for troubleshooting. I tried to disable through Quic,cloud dashboard switching on their Bypass CDN setting but right after I was hit with: “Error code: PR_CONNECT_RESET_ERROR” so they disabled it by removing cName recordthat was set in cPanel zone editor and pointed it the the site name

    So since 2 days I have been free of 504 errors. I suspect it may be because of a certain plugin, Scroll Sequence: https://scrollsequence.com/ I noticed in the Image Optimization settings it states: “Optimize images with our QUIC.cloud server – You can request a maximum of 200 images at once. ” My sequence of images that I’m running is close to 400 images, totaling around 7 MBs. The configuration options are overwhelming, should I enable VPI? Lazy Loading? I’ve searched online and haven’t found any reference to this type of situation, with hundreds of images being loaded upfront. The scroll sequence is place at the start of my home page, so as soon as the user scrolls the sequence starts. Do you have any insight into how I should configure the optimization and other settings? Would you recommend another CDN that works with LiteSpeed? Thanks

    Plugin Support qtwrk

    (@qtwrk)

    the request is once 200 images , but you can request again and again and again

    I am not entirely sure what is it you want to configure now …

    Thread Starter planetboris

    (@planetboris)

    Well when I read the message, 200 images at once, I didn’t know you could request again and again, as you mentioned. What do I want to configure? I’m trying to troubleshoot my issue with Quic.cloud, the 403 errors I keep getting. So I thought that, perhaps because I was exceeding 200 images, that was the reason I was getting 403 error pages. So that is my rationale for asking about configuration settings. So from your question, you don’t know what I’m trying to configure, it seems that there are no special considerations regarding a scroll sequence effect with 400 images being processed., is that correct? I’m trying to find a solution because support from NameHero really don’t know what to do, and support from Quic.cloud, so far, insist that the issue resides server side. I have since disabled Quic.cloud and I no longer have 403 errors. What am I supposed to do? If you don’t have any solutions or suggestions then I guess I can’t use Quic.cloud and that is not a problem, I will just find another solution. I just want to finalize this so I can move on with finishing and launching the website. Thanks

    Plugin Support qtwrk

    (@qtwrk)

    no , the image optm has nothing to do with 403 , no matter how many image you requested

    for 403 , do you have access log? check if you see the 403 error in the access log , if so , that will indicate the 403 happens on the origin

    maybe some mod_security , you can try add

    <IfModule mod_security.c>
       SecRuleEngine Off
       SecRequestBodyAccess Off
    </IfModule>

    to your .htaccess and see if 403 still happens or not

Viewing 15 replies - 1 through 15 (of 18 total)

The topic ‘403 page errors since QUICcloud enabled’ is closed to new replies.