Website "Not Safe" despite I have my SSL Certificate enabled

0

Hi, I am having problems with my website development. The website runs perfectly, but it keeps saying is "not safe". I have my custom domains enabled and the certificate says it is "Valid, in use". I don't know if maybe there is a configuration I'm missing in my apache server or something I'm doing wrong.

I appreciate your help. Thanks.

demandé il y a 3 ans202 vues
15 réponses
0

Can you share the domain?
What reasons is it giving for saying "Not Safe"?

profile picture
David G
répondu il y a 3 ans
0

Can you share the domain name?
What reason is the browser giving for indicating "Not safe"?

profile picture
David G
répondu il y a 3 ans
0

https://www.somabeta.com/
It only happens with my custom domain.

Look my default domain is safe:
https://d3p99zve3eg8ar.cloudfront.net/

Thanks for your help

répondu il y a 3 ans
0

It looks like your DNS isn't setup correctly.

www.somabeta.com has address 54.152.227.225

d3p99zve3eg8ar.cloudfront.net has address 99.84.160.18
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.41
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.119
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.54
(and a bunch of IPV6 addresses)

profile picture
David G
répondu il y a 3 ans
0

I just changed my A record to point to distribution and I think it worked. Can you try again please?

Thank you so much.

répondu il y a 3 ans
0

You shouldn't use A records with lightsail distributions. Use CNAME instead.

That said, it appears to be working fine now.

profile picture
David G
répondu il y a 3 ans
0

You shouldn't use A records with lightsail distributions. Use CNAME instead.

That said, it appears to be working fine now.

profile picture
David G
répondu il y a 3 ans
0

Hahaha It's working man, it's been 6 long hours and you finally solved it. So thank you.

répondu il y a 3 ans
0

Seriously ... change the DNS to use CNAME and point that to the distribution host name. The IP's can change and your site might stop working.

profile picture
David G
répondu il y a 3 ans
0

Seriously ... change the DNS to use CNAME and point that to the distribution host name. The IP's can change and your site might stop working.

profile picture
David G
répondu il y a 3 ans
0

Why David and how to do that? Why A and AAAA is not good and should use CNAME? CNAME To what? Where is IP value declared - A record right? So how will WHOIS know IP without A or AAAA???? A and AAAA records it work perfectly in all my domain with static IPs. But I always try to be better and do it better if I can so I am interested why you say this please and do with CNAME and not A/AAAA? Can you give me an example please how to do it?

I may have double posts in this thread so I am sorry if that is case

Best, Stefano

Edited by: KaiserSnowball on May 21, 2021 12:53 AM

répondu il y a 3 ans
0

The point of a CDN (or distribution) is to distribute the content to various servers ... usually based on the location of the requesters location.

By using A or AAAA records, you are defining fixed IP's that will never change.

If you use CNAME, the IP will change to a host location that is logically closer to the browsers location, reducing delay.

For instance, if I do a lookup from my home in the north west suburbs of Chicago, I get the following:
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.41
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.54
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.18
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.119

But if I do the same lookup from my LS instance in the VA region...

d3p99zve3eg8ar.cloudfront.net has address 13.32.181.122
d3p99zve3eg8ar.cloudfront.net has address 13.32.181.11
d3p99zve3eg8ar.cloudfront.net has address 13.32.181.54
d3p99zve3eg8ar.cloudfront.net has address 13.32.181.94

The Cloudfront DNS servers determined that the shortest distance for the two requesting locations resulted in two different sets of hosts.

david

profile picture
David G
répondu il y a 3 ans
0

The point of a CDN (or distribution) is to distribute the content to various servers ... usually based on the location of the requesters location.

By using A or AAAA records, you are defining fixed IP's that will never change.

If you use CNAME, the IP will change to a host location that is logically closer to the browsers location, reducing delay.

For instance, if I do a lookup from my home in the north west suburbs of Chicago, I get the following:
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.41
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.54
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.18
d3p99zve3eg8ar.cloudfront.net has address 99.84.160.119

But if I do the same lookup from my LS instance in the VA region...

d3p99zve3eg8ar.cloudfront.net has address 13.32.181.122
d3p99zve3eg8ar.cloudfront.net has address 13.32.181.11
d3p99zve3eg8ar.cloudfront.net has address 13.32.181.54
d3p99zve3eg8ar.cloudfront.net has address 13.32.181.94

The Cloudfront DNS servers determined that the shortest distance for the two requesting locations resulted in two different sets of hosts.

david

profile picture
David G
répondu il y a 3 ans
0

Thank you David,
I am still not sures. I host my instances in London. So in Route 53 in London I points my domains' name to the A record. So what would I have to configure to do what you says? I not usings a CDN, not that I am aware nor Cloudfront - thjat costs mroe money right? MOst of my website's users in Italy.

Best, Stefano

répondu il y a 3 ans
0

My recommendation for using a CNAME is applicable for Lightsail distributions.

If you are using an instance, with a static IP, you only need an A and (possibly) AAAA record.

Edited by: David G on May 23, 2021 9:33 AM

profile picture
David G
répondu il y a 3 ans

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions