If https://[ip] gives Not Secure, will https://[domain.com] works?

I am trying to debug why my web server suddenly stopped working.
I want to know if the problem is related to the encryption.
I don't have a strong background in SSL encryption, but a year ago I managed to set it all up myself and now I am stuck.

The problem is very much the title. I'm able to connect to the IP address of my web server and Chrome complains that the connection is Not Secure. I want to know if that's the reason that I cannot connect to the server through my domain name. Or that I need to find something else.

Can bad encryption cause DNS servers to not recognize my server? Since this DNS checker cannot find any resolution to my domain name.

Any help appreciate.
Even a hint toward the right solution.

My domain is: lifnim.ga

I am trying to connect to [ip address] and get Not Secure.

My web server is (include version): nginx/1.18.0 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 20.04.6 LTS

My hosting provider, if applicable, is: AWS?

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no.

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.6.0

Freenom very recently lost control of the .ga ccTLD due to mismanagement.

All .ga domains were deleted, including yours.

Your certificates is only valid for your former lifnim.ga domain. Accessing your webserver using the IP address is not valid, because your certificate is not intended for that purpose.


Oh! Thank you so much for the answer!
That's why ChatGPT couldn't help me :wink:

So I will change my domain. Hoped it will all be fixed.
Thank you so much!

1 Like

Maybe I can manage without Freenom.
I am using AWS ec2 instance. I remember that I couldn't make Let's Encrypt work with the AWS domain name.
That's why I register a domain in Freenom. But is there a better solution for that?

1 Like

I guess buying a real domain or using something like https://duckdns.org/ are some options.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.