This refers to the origin IP of the site you want associated with QUIC.cloud.
Connection Type to Origin
When using QUIC.cloud, browsers first visit QUIC.cloud (CDN), and then may visit the backend (your origin server) if necessary. This configuration option refers to that possible connection between QUIC.cloud and the backend. When QUIC.cloud receives a request from the browser and ‘Match’ is chosen, the request from QUIC.cloud to the backend server will be the same type as the connection from the browser to QUIC.cloud.
When QUIC.cloud receives a request and ‘HTTP only’ is chosen, the request from QUIC.cloud to the origin server will be over HTTP only, regardless of if the request from the browser to QUIC.cloud was over HTTP or HTTPS.
This will downgrade any HTTPS connections to HTTP.
Frontend Force HTTPS
This configuration controls the connection between the browser and QUIC.cloud. When set to ON, HTTP requests are redirected to HTTPS via a 301 header.
Input all domains here that also point to the main site IP. We allow a maximum of 5 domains aliases, but if you have more please contact us for assistance.
www.example.com is automatically considered a domain alias. No need to add it here.
Pressing OFF means disabling QUIC.cloud. By disabling it, QUIC.cloud CDN will be bypassed when a client requests your website, and your IP will be exposed to the public.
Enable Static Cache
Enable this option to cache static files in addition to dynamic files. If switched “OFF”, only dynamic files will be cached. De-activating this will purge the CDN cache of static file entries. The static file cache depends on the ‘Expires’ or ‘Cache-Control’ response header from the backend server. Please make sure that at least one of these are present.
It is HIGHLY recommended to keep this “ON”; we suggest only turning this off when running benchmarks. Make sure to enable this if your site is under attack. If Anti DDOS is triggered, visitors will either be blocked or receive a reCAPTCHA verification before proceeding to secure the site. This verifies that the visitors are people instead of bots. Regardless of configuration, the servers have their own setting, so your visitors may redirect to reCAPTCHA regardless of this setting’s status.
Anti DDOS Whitelist
Any IPs listed here will not meet the antiDDOS filter. The Whitelist is meant only for IPs you trust.
Anti DDOS Blacklist
List any IPs here that you want to be blocked.
We recommend leaving this "ON" at all times. If you choose to leave it off normally, make sure to enable it when your site is under attack. Turning on this option can help defend against a flood attack.
Recaptcha Site Key
You obtain this key when you initially sign your website up for reCAPTCHA here: https://www.google.com/recaptcha/admin#list This is the key QUIC.cloud will give to Google for them to build the reCAPTCHA challenge for your website.
Recaptcha Secret Key
This is the key that Google uses to verify that visitors have passed the reCAPTCHA test.
Recaptcha Type: Checkbox or Invisible
If you select ‘Checkbox’, the visitor will have to check the reCAPTCHA box themselves. If you select ‘Invisible’, reCAPTCHA will activate automatically, and a challenge will appear if the activity is suspicious. QUIC.cloud only supports V2 of reCAPTCHA.
Recaptcha Connection Limit
The value inputted here is the amount of users that must be on your site at one time for QUIC.cloud to toggle reCAPTCHA. Maximum value is 10,000, but we recommend setting it to 100.
Generate Cert. for www/non-www
Switching this to “ON” makes it so certificates are generated for all base domains that both do and do not possess www. It also generates a certificate for all other domains that are configured to point to this site as well (alias domains).
To generate the certificates, each domain will be tested. Therefore, the domain must be configured in the DNS to point to QUIC.cloud. If the DNS entry for any of the domains does not point to QUIC.cloud, certificate generation will fail.
Last operation: 12/31/1969 19:00 – If you see this date it indicates you have never generated a certificate in QUIC.cloud. If a different date is shown, it refers to the last time you did generate a certificate in QUIC.cloud.
Use Custom Certificate
If you intend to use the generated certificate, leave this on “ON”. Otherwise, if you have your own certificate you’d prefer to use, set this to “OFF” and fill in the configuration boxes.
If you don’t have a valid certificate with QUIC.cloud, HTTPS requests served through QUIC.cloud will use our default, self signed certificate.