Quic.cloud errors

  • Resolved Audiomonk

    (@audiomonk)


    4 years, 10 months ago

    Driving me crazy, the onboarding document to configure DNS settings is very difficult to follow indeed. Create an A record that’s a dummy subdomain to your main domain. Then create a CNAME to point to the dummy subdomain, then create a subdomain (WWW) to point to that, then delete your A entry, and create a CNAME that uses the quic.cloud entry?

    Totally lost as to what I’m supposed to be doing, I tried to follow this, but when I added the quic.cloud entry I got “Prohibited IP 1001” errors.

    I’m using cloudflare, is there a setting I am missing, can there be a simpler way to implement this ? All the settings in the plugin are correct, and on my quic.cloud dashboard I can’t enable CDN it says IP not protected and is being redirected. Or similar.

    I just want to give it a go, heard so many good things about it.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter Audiomonk

    (@audiomonk)

    This is the document I’m talking about

    https://docs.litespeedtech.com/lscdn/onboarding/#preparation

    Thread Starter Audiomonk

    (@audiomonk)

    Follow up, my host set it up as per the documents and still got errors. Host said

    “The setup is done as instructed in QUIC’s docs.

    The error which is shown is due to CloudFlare not getting a valid response back.

    Would you be available to contact QUIC for further assistance? The issue is with their system validating CloudFlare’s DNS entry”

    Could this be down to whitelisted IP addresses, do I have to whitelist IP’s inside of Cloudflare?

    Hi @audiomonk, the setting does not require any IP whitelist. Have you checked that is the DNS (DNS lookup tools) already updated? If yes, could you provide you DNS setting with us for finding out the problem? (Please hidden the root domain before reply)

    Thread Starter Audiomonk

    (@audiomonk)

    https://prnt.sc/qvrs37

    I did check the DNS yes, in the quic.cloud dashboard, would not verify, also CDN couldn’t be enabled as it said the IP was exposed.

    I’ve scribbled out the root domain and the server IP in this pic.

    Maybe would be better to email ?

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please try remove that CNAME record for www , and set it to same record as your root domain , as to c10097.tier1.quic.cloud

    Best regards,

    Thread Starter Audiomonk

    (@audiomonk)

    “You’ve requested a page on a website that is on the Cloudflare network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare’s system.”

    I removed the cname and added a new one cname www and c10097.tier1.quic.cloud and just gives that error all the time.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please :

    1. go to my quic cloud dashboard , set domain IP to your server IP , not Cloudflare’s IP

    2. when you create CNAME in cloudflare, please make sure you have set to “grey cloud”

    Best regards,

    Thread Starter Audiomonk

    (@audiomonk)

    Hi,

    Both of those were done by my host and continued to get errors about prohibited IP ?

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Could you please screenshot me both CF DNS setting and QC dashboard ?

    you can mask like half out of the domain/IP in order to not to expose it publicly.

    Best regards,

    Thread Starter Audiomonk

    (@audiomonk)

    Are you sure there isn’t a way to send that info privately? Not comfortable doing this.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please send the screenshot to [email protected] , with link of this thread.

    Best regards,

    • This reply was modified 4 years, 9 months ago by qtwrk.
    Thread Starter Audiomonk

    (@audiomonk)

    Thanks, will do.

    • This reply was modified 4 years, 9 months ago by Audiomonk.
Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Quic.cloud errors’ is closed to new replies.