All of the heetinc.net and www.heetinc.net requests work for me right now.
It seems extra complicated to have one system (ghs) handling redirects for heetinc.net yet have an nginx server handling www.heetinc.net
But, it's your system you can do as you like 
curl -Ii www.heetinc.net
HTTP/1.1 301 Moved Permanently
Server: nginx/1.22.1
Date: Tue, 28 Feb 2023 19:01:13 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive
Location: https://www.heetinc.net/
$ nmap -Pn heetinc.net
Starting Nmap 7.80 ( https://nmap.org ) at 2023-02-28 19:00 UTC
Nmap scan report for heetinc.net (216.239.34.21)
Host is up (0.015s latency).
Other addresses for heetinc.net (not scanned): 216.239.36.21 216.239.32.21 216.239.38.21 2001:4860:4802:36::15 2001:4860:4802:38::15 2001:4860:4802:32::15 2001:4860:4802:34::15
rDNS record for 216.239.34.21: any-in-2215.1e100.net
Not shown: 998 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 4.03 seconds
$ nmap -Pn www.heetinc.net
Starting Nmap 7.80 ( https://nmap.org ) at 2023-02-28 19:01 UTC
Nmap scan report for www.heetinc.net (83.179.80.74)
Host is up (0.21s latency).
rDNS record for 83.179.80.74: m83-179-80-74.cust.tele2.lt
Not shown: 978 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
254/tcp open unknown
416/tcp open silverplatter
443/tcp open https
900/tcp open omginitialrefs
990/tcp open ftps
1089/tcp open ff-annunc
2003/tcp open finger
3300/tcp open ceph
3389/tcp open ms-wbt-server
4567/tcp open tram
5911/tcp open cpdlc
7001/tcp open afs3-callback
7402/tcp open rtps-dd-mt
7496/tcp open unknown
8083/tcp open us-srv
8649/tcp open unknown
9944/tcp open unknown
16018/tcp open unknown
50002/tcp open iiimsf
64680/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 164.33 seconds
You can stay clear of heetinc.net
Focus only on the "www":
Name: heetinc.net
Addresses: 2001:4860:4802:36::15
2001:4860:4802:38::15
2001:4860:4802:32::15
2001:4860:4802:34::15
216.239.32.21
216.239.36.21
216.239.38.21
216.239.34.21
Name: www.heetinc.net
Address: 83.179.80.74
And now this is what I see.
My computer must have had A Momentary Lapse of Reason while Learning to Fly
$ curl -Ii http://heetinc.net
HTTP/1.1 302 Found
Location: https://www.heetinc.net/
Date: Tue, 28 Feb 2023 19:05:13 GMT
Content-Type: text/html; charset=UTF-8
Server: ghs
Content-Length: 221
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
$ curl -Ii https://heetinc.net
HTTP/2 302
location: https://www.heetinc.net/
date: Tue, 28 Feb 2023 19:05:17 GMT
content-type: text/html; charset=UTF-8
server: ghs
content-length: 221
x-xss-protection: 0
x-frame-options: SAMEORIGIN
$ curl -Ii http://www.heetinc.net
HTTP/1.1 301 Moved Permanently
Server: nginx/1.22.1
Date: Tue, 28 Feb 2023 19:05:24 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive
Location: https://www.heetinc.net/
$ curl -Ii https://www.heetinc.net
HTTP/2 200
server: nginx/1.22.1
date: Tue, 28 Feb 2023 19:05:30 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
x-powered-by: PHP/8.2.3
strict-transport-security: max-age=63072000
Will do! 
Congratulations, you're SSLLabs-ing Google.
That has a Let's Encrypt issued certificate Alternative names heetinc.net
vs this certificate Alternative names heetinc.net www.heetinc.net
No, it's a cert from "GTS CA 1D4". Not Let's Encrypt. It's hosted by Google. Not OP.
Yep! My bad.
Anyway, it seems a HTTP to HTTPS redirect for www.heetinc.net is currently also in effect, so all good I guess.
Thanks, everyone! I got it to work, thanks to everyone's help! No matter what you type, if it's http or https or www or not, it will redirect you to the website without using 2 separate systems to handle redirects! One issue, I used to be able to enter the phpmyadmin page through localhost/phpmyadmin. Now I can't anymore! If you need to see the configuration for NGINX, it's here! I also want to know if it's normal I can't enter my website through a private IPv4 address without using https://, because I used to be able to, and if it's usual to have my localhost IP address change to ::1!
::1 == localhost, just IPv6 instead of IPv4.
Alright, everything is fixed. Thanks, everyone! I did nothing to solve the certificate is invalid issue... I just had to wait! But there were still a couple of issues that I had to fix! Like using multiple systems handling redirect, phpMyAdmin not opening up anymore, and getting a false GET 404 error! I fixed phpMyAdmin by removing the root directive and adding phpMyAdmin to try_files like this: try_files $uri $uri/ /phpMyAdmin/index.php?$args; Next, the false GET 404 error was fixed by replacing the /scripts in the SCRIPT_FILENAME argument to $document_root like this: fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
Hope you have a fantastic day!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
