CDN URL and QUIC.cloud CDN config problems

Hi,

No , no need to create a CDN domain

you need to go to your DNS management , remove A record for healthgym.net , then create a CNAME record for healthgym.net , with value c126295.tier1.quic.cloud

Best regards,

Hello again.

I think I can explain it more clearly this time.

I want to make the CNAME record for QUIC.cloud CDN (c126295.tier1.quic.cloud), without removing the CNAME record for Cloudflare CDN (healthgym.net.cdn.cloudflare.net).

In other words, I want to know if exist some alternative way to keep the two CDN’s providers running simultaneously.

Even if you don’t know exactly how to do this, if you or someone indicates a tutorial or instructional material that I can study and follow, it will already be a significant help.

Thank you right now!

—
PS: I quoted the subdomain example, because I thought, hypothetically, it would be an alternative.

Hi,

Even if you don’t know exactly how to do this, if you or someone indicates a tutorial or instructional material that I can study and follow, it will already be a significant help.

Well , I am not exactly an expert here , but I think I could help on thing or two if you can make your requirement and goal more clear to me.

There are 2 scenarios

1. you put CF over QC , make it like

user <---> CF <---> QC <---> Origin

2. you set a separated domain , a sub domain , like cdn.domain.com , and put this domain over CF for static files , for example

user <---> QC  <---> Origin
  ↑                    |
  |                     |
  |                     ↓
  ------------> CF with static resources

so , please explain what exactly is it you want to do or achieve ?

Best regards,

• This reply was modified 4 years, 5 months ago by qtwrk.

@healthgym

If you are using CloudFlare as your name server You can have more than one Cname record but you can’t have both records be the “root” record at the same time.

I don’t see an issue if you create the CNAME for healthgym.net
as c126295.tier1.quic.cloud.

If your name servers are already: align.cloudflare.net and dana.cloudflare.net or “*.cloudflare.net” you don’t need a cloudflare cname.

You need to move your NS servers completely from
NS1.DNS-PARKING.COM
NS2.DNS-PARKING.COM

To cloudflare, just sign up for the free account and follow the instructions.

@qtwrk

Hello,

What I had thought is closer to the #2 scenario you demonstrated.

user <---> QC  <---> Origin
  ↑                    |
  |                     |
  |                     ↓
  ------------> CF with static resources

Hi,

In that case , you just need to create a sub-domain on Cloudflare , there should be plenty of guides here and there

https://community.cloudflare.com/t/static-content-from-subdomain/731/5

https://community.cloudflare.com/t/how-do-i-set-up-cdn-on-a-subdomain/25191/3

and the main domain part is just same as usually , to set up the QC

once you got CF CDN domain , you can use CDN tab in our plugin , to rewrite static resources URL from https://www.domain.com to cdn.domain.com

Best regards,

@qtwrk

I edited the CNAME for QUIC.cloud. (@ = healthgym.net)

From:
@ healthgym.net.cdn.cloudflare.net 86400

To:
@ c126295.tier1.quic.cloud 86400

Quic.CLOUD CDN connected to the control panel. But a serious error occurred in the SSL authentication certificate.

I also tried to edit CNAME of https://www.healthgym.net.
From:
www www.healthgym.net.cdn.cloudflare.net 1800

To:
www c126295.tier1.quic.cloud 1800

And I turned ON the “Map Both www/non-www to CNAME”. But it didn’t work. And the authentication problem persists.

I did several tests and these are the messages that appear:

Browser’s:

Your connection is not private
This server could not prove that it is healthgym.net; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.

NET::ERR_CERT_AUTHORITY_INVALID

GTmetrix.com:

Analysis Error

The SSL certificate being used on this website was issued for another website's address

Check that the correct certificate is installed or purchase a new certificate for the site.

PageSpeed Insight:
Lighthouse returned error: NO_FCP. Ocorreu um erro com a grava??o dos rastros no carregamento de página. Execute o Lighthouse novamente. (NO_FCP)

WabePageTest:

(Test Error: newt:ERR_CERT_AUTHORITY_INVALID)
(Error: 404)

I noticed that in the QUIC.cloud CDN dashboard, it was supposedly automatically generated an SSL certificate, but it’s like it has nothing.

‘SSL Certificate
Current Certificate
Status: will auto-renew in 79 days

Expiration date: 09/23/2020

Last updated: 06/25/2020 13:19

Issued by: Let’s Encrypt’

SSL Certificate:
System-Generated
QUIC.cloud will automatically generate and renew your SSL certificate from Let's Encrypt for free using certbot. Set it and forget it.

I made the edits as quic.cloud instructs. I don’t know why it generated this error/conflict with SSL.

PS: In order for the website to work again, I restored the CNAME records to what was before the changes. That is, to (healthgym.net.cdn.cloudflare.net)

From QC backend I see cert is valid for both https://www.healthgym.net and healthgym.net

this might be sync issue , other nodes are delayed to sync up with new data/conf/cert

please try change the DNS to CNAME again few moments later , it should have all the data sync up by then

if you still got issue with QC, please create a ticket here

Best regards,

Now I have to wait for the entire network to be reestablished and “stabilize”.

I’ll try again, as you said, tomorrow, over the weekend. This time, I will do the editing at night, so that the process of propagation and sync occurs by the nodes of the system/network, during at dawn and with minor problems with user traffic.

At least now I know how to restore the CNAME in case the same problem occurs. Which gives me more security to repeat the changes and the tests, without having a small heart attack. ??

I’ll send you the answer with the test results.

Best regards.

@qtwrk

Hello, I came back to give the feedback, as I promised.

I made another attempt yesterday. I edited the CNAME records for QUIC.cloud CDN.
@
healthgym.net --> c126295.tier1.quic.cloud 86400 TTL
www
www.healthgym.net --> c126295.tier1.quic.cloud 1800 TTL

This time it gave no problem or conflict with the SSL authentication certificate. The change was successful.:D

I made the change of the CNAME registration at 20:00 (06/26), and until 14:00 today (06/27), ie after 18 hours of propagation, the SSL certificates of QUIC.cloud (Let’s Encrypt) came to be recognized by all browsers, and there are several regions, including to my region (I tested using VPN).

And now, “whatsmycdn.com” has stopped detecting Cloudflare CDN. Which is a sign that change has taken effect. Probably with a few more hours, the “whatsmycdn.com” will detect the QUIC.cloud CDN. Although I don’t know if this tool has this capability. (I have to find a better external tool to do CDN testing).

But by doing speed and performance tests, in Uptrends.com, GTmetrix and etc. by the results presented, the CDN is already taking effect and working well.

Once this first step is complete, I will now go to the second step: Create a sub-domain, and point the subdomain records to the Cloudflare CDN. Following your recommendations and the instructions of the material/link, you gave in the posts above.

To achieve the proposed objective:

user <---> QC  <---> Origin
  ↑                     |
  |                     |
  |                     ↓
  ------------> CF with static resources

(I just don’t know how I’ll do the empirical test of this “multi CDN”)

@qtwrk Thank you so much for your help! I am grateful and happy for the attention you have given and the patience you have had in understanding my complicated goal.

I will return to this topic, to give feedback, when everything is ready.