Is this working


#1

I signed up for the free account and not I’m sure if I set this up right. It says my account is active, I changed the name servers but when I go to my site, there isn’t a https:// in front of my domain. Help :slight_smile:


#4

I signed up for the free account and not I’m sure if I set this up right. It says my account is active, I changed the name servers but when I go to my site, there isn’t a https:// in front of my domain. Help :slight_smile:


#5

First check that your site is reachable using SSL by appending https:// in from of your domain then, if it works you need to configure a redirect from HTTP to HTTPS. If it doesn’t work check the SSL setting (it must be at least Flexible). If you have a SSL certificate on your server then you can change it to Full (Strict only if the certificate is valid).

I would recommend doing the redirect from the Cloudflare Dashboard using Always Use HTTPS in the Crypto Tab.


#6

When I did that this came up:

Error 502 Ray ID: 412128dd7fc35619 • 2018-04-27 12:05:50 UTC
Bad gateway

How do I fix that?


#7

now I get this message and my site is completely screwed up.

This page (https://www.eleven22.co/) is currently offline. However, because the site uses Cloudflare’s Always Online™ technology you can continue to surf a snapshot of the site. We will keep checking in the background and, as soon as the site comes back, you will automatically be served the live version.


#8

What setting do you have on the first option in the Crypto tab? SSL Off, Flexible, Full or Full (Strict)? It may be that in the two Full cases your hosting does not allow HTTPS traffic, I would switch it to Flexible in that case.


#9

It is on flexible.


#10

Would you mind telling me exactly what did you toggle or change between the working and not working state? Only the redirect?


I was working with Matteo
#11

The redirect from the Cloudflare Dashboard using Always Use HTTPS in the Crypto Tab. But even before I did that I was getting the 502 page.


#12

I just want to end this service…how do I get my name servers back to what they were??


#13

Let’s try a bit more to fix issues, it may be a simple configuration. Would you mind sharing for a moment the Origin’s IP? I could try doing a couple of test, 5 simple minutes.


#14

Where do I find that?


#15

In the DNS page, the eleven22.co and www records on the right of the page point to a domain or an IP address.


#16

52.203.86.228


#17

52.73.83.244

The A records


#18

The IP address you provided (AWS in the US, I believe) require a certificate to connect on the 443 HTTPS port and timeout on the 80 HTTP port.

Did you setup Authenticated Origin Pulls, by any chance? Otherwise the issue is with your server.

If you have setup AUP then the issue may be solved by switching to Full/Full (Strict) on the Crypto tab in the Dashboard.


#19

I don’t get any of this language. Someone suggested I create a https for my domain and now it’s completely screwed up. I thought it was as easy as to change the name servers to what they provided. How do I just get things back to normal? I bought the domain from go daddy but use GSuite for my email.

Please get me out of this mess.


#20

I just want to go back to being unsecure site. How do I cancel this???


#21

It is usually with Cloudflare, but in this case your configuration is messed up.

You never changed you name servers to Cloudflare’s, didn’t even occur to me this was a possibility given your initial message.

; <<>> DiG 9.10.6 <<>> NS eleven22.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56926
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;eleven22.com.			IN	NS

;; ANSWER SECTION:
eleven22.com.		3600	IN	NS	nsa1.nts.ch.
eleven22.com.		3600	IN	NS	nsa2.nts.ch.

;; Query time: 44 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Apr 27 14:52:43 CEST 2018
;; MSG SIZE  rcvd: 85

First follow this guide (using the name servers that Cloudflare indicates in the DNS tab under Cloudflare Nameservers, then we can talk about issues, even though I believe there are additional issues with your server if the IPs you provided are correct:

https://www.godaddy.com/help/set-custom-nameservers-for-domains-registered-with-godaddy-12317


#22

Additionally: in the Overview tab for your domain, what is the status (and respective color) of the first box?