Returning "Non secure Connection" when on HTTPS


#1

Changed NameServers, the site is working but with https:// it’s still showing “Non secure Connection”


#2

Whats the URL?


#3

First guess would be mixed content. You might have absolute URLs somewhere which still point to HTTP links.


#4

https://felixairservices.com/


#5

Here it is
felixairservices(dot)com

Thanks Sandro,


#6

Your site does not appear to be behind Cloudflare and the error you get is because you have an invalid certificate assigned.


#7

No, that is not the case. IN that case the browser shows a notification, but site is not getting downed.


#8

Really?
You should check this
https://www.whatsmydns.net/#NS/felixairservices.com


#9

Really ;). You are using the Cloudflare nameservers, but you dont tunnel the requests through it.

Check out http://sitemeer.com/#felixairservices.com

Your DNS settings are probably :grey: when they should be set to :orange:


#10

I see :face_with_monocle:
But I am unable to do that, because it’s still showing me the following message under Overview
“Status: Website not active (DNS modification pending)”


#11

It’s waiting for the NS propagation. Have you recently added the domain to Cloudflare? I believe that is the case.


#12

Yes, matteo. I have added the domain and changed the NS 4 hours ago.


#13

Then that would explain it. Wait for the domain to become active (shouldn’t take long), then turn it to :orange: and wait for the TLS certificate to be issued (of you are on the free plan it should take less than 24 hours). Then try again.

Set your Crypto SSL setting to Full, since the certificate you have is not valid to have TLS encryption both side of Cloudflare’s Edge Nodes.


#14

The change needs to be made at your registrar, not on the nameservers currently managing the zone. Currently your registrar points to

|felixairservices.com.|172800|IN|NS|ns1.ipage.com.|
|---|---|---|---|---|
|felixairservices.com.|172800|IN|NS|ns2.ipage.com.|

#15

That would explain it, didn’t even check…


#16

Hmm, the root servers do point to iPage, everything else (including 1.1.1.1) returns Cloudflare though.


#17

Interesting, the root servers point to iPage. iPage on the other hand disavows itself and returns (jake|dara).ns.cloudflare.com as nameservers.


#18

They do point to Cloudflare now…


#19

How are you testing? Both whois and dig felixairservices.com +trace @8.8.8.8 still return non Cloudflare nameservers for me. Those are no longer (incorrectly) sub-delegated to Cloudflare though.


#20

Using my University’s DNS, can’t use 8.8.8.8 here… Using DOH (https://dns.google.com/query?name=felixairservices.com&type=NS&dnssec=true) on Google they point to Cloudflare, though.

Matteos-MacBook-Pro:~ matteomanfredi$ dig NS felixairservices.com

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

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

;; ANSWER SECTION:
felixairservices.com.	3108	IN	NS	dara.ns.cloudflare.com.
felixairservices.com.	3108	IN	NS	jake.ns.cloudflare.com.

;; ADDITIONAL SECTION:
dara.ns.cloudflare.com.	69775	IN	A	173.245.58.91
dara.ns.cloudflare.com.	69775	IN	AAAA	2400:cb00:2049:1::adf5:3a5b
jake.ns.cloudflare.com.	13130	IN	A	173.245.59.122
jake.ns.cloudflare.com.	13130	IN	AAAA	2400:cb00:2049:1::adf5:3b7a

;; Query time: 1 msec
;; SERVER: 130.192.3.21#53(130.192.3.21)
;; WHEN: Fri May 25 10:31:41 CEST 2018
;; MSG SIZE  rcvd: 189