• Resolved sporbillis

    (@sporbillis)


    Failed to communicate with QUIC.cloud server: Unknown error: request to https://www.domain.com/?LSCWP_CTRL=before_cache failed, reason: Hostname/IP does not match certificate’s altnames: Host: https://www.domain.com. is not in the cert’s altnames: DNS:domain.com [server] https://node17.quic.cloud [service] health

    I have changed my domain with domain.com .

    I get this error everytime i click the page speed sync in litspeed. If i click sync on “QUIC.cloud Service Usage Statistics” it works fine. This only happens when I click sync on page speed.

    Report number: FJQJLEKK

    I have already sent it to you guys.Please help!

    Thanks!

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

    (@qtwrk)

    could you please try click it again ?

    Thread Starter sporbillis

    (@sporbillis)

    I clicked it now, doesn’t seem to give error now. How was it fixed?

    Plugin Support qtwrk

    (@qtwrk)

    I am not sure , but it looks like a temp issue when cert is being sync’ed when you enable QC CDN or renew its cert.

    Thread Starter sporbillis

    (@sporbillis)

    Is there something i can do to help out to identify the issue? It is still working today as well!

    Plugin Support qtwrk

    (@qtwrk)

    just wondering , did you enable the QC CDN at or around that time when first error occurs ? because when enabel CDN, there was a gap time for about 10 – 15 minutes the cert is being regenerated , based on error message you provided , that’s my most logical guess.

    Thread Starter sporbillis

    (@sporbillis)

    Yes to be honest I set up again the CDN however, I waited for over 30 minutes – 1 hour before opening a ticket just in case it was something related to that. Maybe it’s the cert you mentioned but takes longer I guess!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Failed to communicate with QUIC.cloud server:’ is closed to new replies.