• Resolved Sean Thompson

    (@seanthompson)


    Image optimization stopped working. I can send optimization request, but it won’t pull the images. I have cron enabled. If I disable the cron, the pull images button remains greyed out and absolutely nothing happens when I click it.

    I contacted support through QUIC.cloud and they said REST api is blocked. I have it disabled on the front end for unauthenticated requests only, and whitelisted all the QUIC.cloud IPs so they can access REST api. I disabled the plugin to allow full api access and it still won’t pull the images.

    I also whitelisted all QUIC.cloud IPs in my server firewall.

    I double checked with my server support department and they said nothing is blocking those IPs.

    It was working, and then just stopped without me changing anything. One website stopped working in December, another in January.

    I’ve been trying to figure this out for days. The other day it started working on a couple of sites and then stopped working again.

    I searched this forum and tried everything I found in other threads.

    If the api request is authenticated there shouldn’t be an issue.

    Image Optimization has been buggy for years.

    Thanks in advance, Sean

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

    (@qtwrk)

    please provide the report number

    you can get it in toolbox -> report -> click “send to LiteSpeed”

    Thread Starter Sean Thompson

    (@seanthompson)

    Last Report Number: WRCBINZK

    Plugin Support qtwrk

    (@qtwrk)

    access https://domian.com/?rest_route=/litespeed/v1/notify_img you still get 403 error as REST API disbaled

    Thread Starter Sean Thompson

    (@seanthompson)

    If the request is coming from QUIC.cloud it should have access. I have all the IPs whitelisted. I added my own IP to that array and I was able to access it fine. When I removed my IP I got Rest api disabled.

    Plugin Support qtwrk

    (@qtwrk)

    I was sending request from one of the QC IPs , 163.182.174.161 to be precise, and it is listed in

    Thread Starter Sean Thompson

    (@seanthompson)

    That IP is in the whitelist.

    Also, If I disable that plugin, it still doesn’t work.

    With my own IP in the whitelist I can access /wp-json and /litespeed/v1/notify_img is in the list of endpoints.

    If I try to access /?rest_route=/litespeed/v1/notify_img I don’t get a 403, I get…

    {“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method.”,”data”:{“status”:404}}

    Something else must be wrong.

    I have that plugin enabled on a site I just built, and the pull cron is working:

    Last Request: 07/23/2025 12:08:04

    Last Pulled: 07/23/2025 12:10:05 (Cron)

    On other sites…

    The one I sent you the report from…

    Last Request: 07/23/2025 16:32:02

    Last Pulled: 12/18/2024 14:15:04 (Cron)

    Another…

    Last Request: 07/23/2025 15:47:15

    Last Pulled: 01/24/2025 09:28:02 (Cron)

    Other sites, sometimes it works, sometimes it doesn’t. The only thing that does work sometimes is the cron. The pull images button does absolutely nothing.

    Plugin Support qtwrk

    (@qtwrk)

    on my browser, I get REST API is disabled. notice

    on node , I get

    <!DOCTYPE html>
    <html style="height:100%">
    <head>
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
    <title> 403 Forbidden
    </title><style>@media (prefers-color-scheme:dark){body{background-color:#000!important}}</style></head>
    <body style="color: #444; margin:0;font: normal 14px/20px Arial, Helvetica, sans-serif; height:100%; background-color: #fff;">
    <div style="height:auto; min-height:100%; "> <div style="text-align: center; width:800px; margin-left: -400px; position:absolute; top: 30%; left:50%;">
    <h1 style="margin:0; font-size:150px; line-height:150px; font-weight:bold;">403</h1>
    <h2 style="margin-top:20px;font-size: 30px;">Forbidden
    </h2>
    <p>Access to this resource on the server is denied!</p>
    </div></div><div style="color:#f0f0f0; font-size:12px;margin:auto;padding:0px 30px 0px 30px;position:relative;clear:both;height:100px;margin-top:-101px;background-color:#474747;border-top: 1px solid rgba(0,0,0,0.15);box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;">
    <br>Proudly powered by LiteSpeed Web Server<p>Please be advised that LiteSpeed Technologies Inc. is not a web hosting company and, as such, has no control over content found on this site.</p></div></body></html>

    which is the default 403 error page , you must have something else that blocking the REST API , by rewrite rule or deny,allow directive

    Thread Starter Sean Thompson

    (@seanthompson)

    Is your browser running on one of the QUIC.cloud IPs? If not, you’re supposed to get the disabled message. There’s no other rewrite rule or directive blocking it.

    That wouldn’t explain why it works on some sites, and not others and only sometimes on others.

    I shouldn’t have to have REST api fully accessible to anyone to allow an AUTHENTICATED request from an IP I whitelisted.

    This stopped working on it’s own without me making any changes.

    Plugin Support qtwrk

    (@qtwrk)

    yes, I know , I meant to see that , but it is on 200 OK response with that message

    while from QC node , it is 403 error , this indicates something from server level is blocking it , it seems

    Thread Starter Sean Thompson

    (@seanthompson)

    I doublechecked my firewall whitelist and contacted my server support and they assured me all those IPs weren’t blocked by anything.

    Plugin Support qtwrk

    (@qtwrk)

    when I send from a different QC IP , the first one in the list, it works

    support@161:~$ date ; curl -XPOST -d "test" https://xxx.com/?rest_route=/litespeed/v1/notify_img -i
    Thu Jul 24 12:16:07 AM UTC 2025
    HTTP/2 403
    date: Thu, 24 Jul 2025 00:16:07 GMT
    content-type: text/html
    content-length: 1242
    cache-control: private, no-cache, no-store, must-revalidate, max-age=0
    pragma: no-cache
    server: LiteSpeed
    vary: User-Agent
    permissions-policy: browsing-topics=()
    content-security-policy: frame-ancestors 'self' https://www.google.com
    referrer-policy: no-referrer-when-downgrade
    x-frame-options: SAMEORIGIN
    alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
    x-turbo-charged-by: LiteSpeed

    <!DOCTYPE html>
    <html style="height:100%">
    <head>
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
    <title> 403 Forbidden
    </title><style>@media (prefers-color-scheme:dark){body{background-color:#000!important}}</style></head>
    <body style="color: #444; margin:0;font: normal 14px/20px Arial, Helvetica, sans-serif; height:100%; background-color: #fff;">
    <div style="height:auto; min-height:100%; "> <div style="text-align: center; width:800px; margin-left: -400px; position:absolute; top: 30%; left:50%;">
    <h1 style="margin:0; font-size:150px; line-height:150px; font-weight:bold;">403</h1>
    <h2 style="margin-top:20px;font-size: 30px;">Forbidden
    </h2>
    <p>Access to this resource on the server is denied!</p>
    </div></div><div style="color:#f0f0f0; font-size:12px;margin:auto;padding:0px 30px 0px 30px;position:relative;clear:both;height:100px;margin-top:-101px;background-color:#474747;border-top: 1px solid rgba(0,0,0,0.15);box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;">
    <br>Proudly powered by LiteSpeed Web Server<p>Please be advised that LiteSpeed Technologies Inc. is not a web hosting company and, as such, has no control over content found on this site.</p></div></body></html>

    maybe you can ask your provider to check the access log on that date and IP (163.182.174.161) , what happens with this request

    • This reply was modified 10 months ago by qtwrk.
    • This reply was modified 10 months ago by qtwrk.
    Thread Starter Sean Thompson

    (@seanthompson)

    Something must be wrong on the QC end then. Would that also cause the pull images button to remain greyed out and not work?

    Plugin Support qtwrk

    (@qtwrk)

    yes, I was sending from one of the main image optm server

    you must have not properly whitelist our IPs

    actually , I sent from 2 image optm server, and plus other 2 different nodes , all end up in 403

    • This reply was modified 10 months ago by qtwrk.
    Thread Starter Sean Thompson

    (@seanthompson)

    I just checked the access logs and 163.182.174.161 wasn’t there.

    I checked in firewall whitelist and it’s definitely whitelisted.

    Plugin Support qtwrk

    (@qtwrk)

    support@node119:~$ curl -XPOST -d "test" https://xxx.com/?rest_route=/litespeed/v1/notify_img -i -v
    Note: Unnecessary use of -X or --request, POST is already inferred.
    * Trying 209.xxx.xxx.107:443...
    * Connected to xxx.com (209.xxx.xxx.107) port 443 (#0)
    * ALPN, offering h2

    209.xxx.xxx.107

    is your origin IP ?

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

The topic ‘Can’t Pull Images’ is closed to new replies.