SSL not enabled on my website

Website, Application, Performance Security
1

What is the name of the domain?

What is the error number?

just says no SSL

What is the error message?

not secure

What is the issue you’re encountering

SSL not enabled on my website

What steps have you taken to resolve the issue?

I followed these instructions:

Created my cloudflare account and my domain says its active.

On my synology NAS the certificate shows up in the security area and assigned to all the services. Even changed the domain forward at godaddy.com to https://50.214.75.161/wordpress/ which is my publice static IP on my synology NAS. Still when I pull up the domain says not secure. Any help greatly appreciated.

Was the site working with SSL prior to adding it to Cloudflare?

No

What is the current SSL/TLS setting?

Strict (SSL-Only Origin Pull)

2

Your site is working with HTTPS: https://marine-captain.com

Insecure requests are not being redirected to HTTPS. If you want to do that, the easy way is to go to your Cloudflare dashboard, choose SSL/TLS, choose Edge Certificates, and enable the “Always Use HTTPS” option. This will redirect any HTTP requests to HTTPS.

3

So I followed your directions. Went into cloudflare and chose SSL, while also checking the “always use https” option … still my website is insecure …

4

You don’t have the Cloudflare proxy enabled, so no Cloudflare features will work on it. Browsers are connecting directly to your server.

Enable the :orange: proxy on the DNS entries.

2 Likes
5

Pretty sure they are enabled.

Untitled
Untitled723×296 42.6 KB

7

Your site is currently not using Cloudflare at all. It is using GoDaddy nameservers instead:

marine-captain.com.     172800  IN      NS      ns07.domaincontrol.com.
marine-captain.com.     172800  IN      NS      ns08.domaincontrol.com.
;; Received 187 bytes from 2001:500:d937::30#53(l.gtld-servers.net) in 27 ms

marine-captain.com.     3600    IN      A       15.197.225.128
marine-captain.com.     3600    IN      A       3.33.251.168
marine-captain.com.     3600    IN      NS      ns08.domaincontrol.com.
marine-captain.com.     3600    IN      NS      ns07.domaincontrol.com.
;; Received 131 bytes from 2603:5:2270::4#53(ns08.domaincontrol.com) in 27 ms

Though it seems to be active on Cloudflare as well - have you made any changes very recently?

2 Likes
8

thanks for the quick reply, You guys help is greatly appreciated.

So I added the name servers to godaddy per the directions in cloudflare.com

Not sure what to do here:

Untitled
Untitled1102×803 85.5 KB

9

I would assume that you can change the nameservers in the “Nameservers” section in your screenshot.

1 Like
10

I did change the nameservers on godaddy:

Untitled
Untitled1168×572 69 KB

11

The nameservers on your screenshot are clearly not the same that are assigned to your Cloudflare account.

So what do you mean by

?

2 Likes
12

Okay, I updated the nameservers from cloudflare to godaddy

NS nash.ns.cloudflare.com
NS yolanda.ns.cloudflare.com

but when I pull up marine-captain.com, I see a lock on the address bar, but the page says HTTP Status: 404 (not found)

13

Please check that you are using the Full (strict) SSL setting on Cloudflare: https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls

14

Okay I am in cloudflare.com

My domain shows it is active

Always use HTTPS is enabled

Automatic HTTPS Rewrites is enabled

Still I am getting the 404 error

Native address comes up fine:

http://50.214.75.161/wordpress/

15

That’s not the IP you’ve been using until a few hours ago:

It also doesn’t work when sending a host header:

curl -svo /dev/null http://marine-captain.com/ --connect-to ::50.214.75.161
* Connecting to hostname: 50.214.75.161
*   Trying 50.214.75.161:80...
* Connected to 50.214.75.161 (50.214.75.161) port 80
> GET / HTTP/1.1
> Host: marine-captain.com
> User-Agent: curl/8.5.0
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Server: nginx
< Date: Tue, 03 Dec 2024 22:49:37 GMT
< Content-Type: text/html
< Content-Length: 3566
< Connection: keep-alive
< Keep-Alive: timeout=20
< Vary: Accept-Encoding
< ETag: "673fd7d0-dee"
<
{ [1230 bytes data]
* Connection #0 to host 50.214.75.161 left intact
1 Like
16

so what am I supposed to do

17

First thing, I’d recommend you change your DNS records in Cloudflare to DNS-Only.

18

I am not sure I understand …

Can you please instruct me …

19

In this post, you see your DNS record and a column named Proxy-Status: SSL not enabled on my website - #5 by ray.mccormack

Click on edit next to the records and change the Proxy-Status to DNS-Only.

1 Like
20

ok did that

21

Ok, just to make sure: Was your website working with the domain before you changed your nameservers to Cloudflare earlier?