Hi!
I can't connect or ping my website (www.varelasnkrs.com) after installing Certbot with the Let's Encrypt certificate. I also disabled the HTTPS auto-redirect in the /sites-enabled/default file because I was thinking I couldn't connect because the WP setting had http://varelasnkrs.com as the default address but that is not the case and I already reversed the changes to the file. I also can't connect using the server IP (129.151.227.103), that worked before.
Can someone help me?
Thanks! 
Welcome to the Let's Encrypt Community!
Why are ports 80 (HTTP) and 443 (HTTPS) closed? 
I'm thinking you might have borked your webserver configuration when you tried to reset it. Apache or nginx? Please heed the great information that @Bruce5051 has provided below as well.
Hello @varela, welcome to the Let's Encrypt community. 
With Let's Debug results are here https://letsdebug.net/varelasnkrs.com/1395808
Best Practice - Keep Port 80 Open
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Thank you for assisting us in helping YOU!
Here is a list of issued certificates crt.sh | varelasnkrs.com, the last one seems to only have the domain name varelasnkrs.com and not www.varelasnkrs.com that had previously been on the cert.
I already fixed it by oppening port 443 on the server! Can you guys test if the website works now? Thanks!
varelasnkrs.com looks OK SSL Server Test: varelasnkrs.com (Powered by Qualys SSL Labs)
www.varelasnkrs.com has " Alternative names varelasnkrs.com MISMATCH" SSL Server Test: www.varelasnkrs.com (Powered by Qualys SSL Labs)
I have another issue. When I try to access the website using www.varelasnkrs.com or http://varelasnkrs.com it doesn't redirect to www.varelasnkrs.com
Port 80 is still closed - Best Practice - Keep Port 80 Open
With out Port 80, the only Challenge Types - Let's Encrypt that will work is DNS-01 challenge;
I am thing renewals.
$ nmap -Pn varelasnkrs.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-03-04 18:05 UTC
Nmap scan report for varelasnkrs.com (129.151.227.103)
Host is up (0.16s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 11.46 seconds
$ nmap -Pn www.varelasnkrs.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-03-04 18:05 UTC
Nmap scan report for www.varelasnkrs.com (129.151.227.103)
Host is up (0.17s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 11.45 seconds
$ curl -Ii https://varelasnkrs.com
HTTP/1.1 200 OK
Server: nginx/1.18.0 (Ubuntu)
Date: Sat, 04 Mar 2023 18:09:30 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Link: <https://varelasnkrs.com/wp-json/>; rel="https://api.w.org/"
Link: <https://varelasnkrs.com/wp-json/wp/v2/pages/1986>; rel="alternate"; type="application/json"
Link: <https://varelasnkrs.com/>; rel=shortlink
$ curl -k -Ii https://www.varelasnkrs.com
HTTP/1.1 301 Moved Permanently
Server: nginx/1.18.0 (Ubuntu)
Date: Sat, 04 Mar 2023 18:09:33 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Redirect-By: WordPress
Location: https://varelasnkrs.com/
I'm opening the port like I did when I setup the website:
Here is an online TCP Port Scanner, Online Port Scan, Port Scanning | IPVoid to assist in remote testing.
It take an IP Address, I do not believe it will take domain names. 
This is what I presently see
Isn't the port open in this print:
And is there something else I should close?
First thing that caught my eye is that your port 80 rule is below the -j REJECT rule. However, I'm not getting a rejection from port 80, but a time out.. So it seems my TCP connection isn't hitting the -j REJECT rule either? So perhaps something else is still blocking access to your server on port 80, as it doesn't seem to be reaching that iptables either.
Although @Bruce5051 is getting a "closed" answer on port 80 instead of the "filtered" (i.e.: time out) I'm getting.. So perhaps putting the port 80 rule above the -j REJECT might fix it for a numbe of people, but still weird I'm getting a timeout.
Hm, nevermind, the ipvoid.com site Bruce just used is now also seeing "filtered".. Did you change anything in your iptables rules to make the change from "closed" to "filtered"?
Previously I had three rules for port 80. I deleted all three and created the one that you are seeing.
I can also confirm that the port 80 is now filtered and not closed:
This will accept domain names:
I was already using that website before. It show that ports 443 and 22 are open but port 80 isn't and I don't know why...
Is your ISP blocking?
Using traceroute on Port 80 looks like the IPv4 Address causing the blockage is 129.151.227.103, the host server itself (or possibly a router with NAT and port forwarding to the host).
$ sudo traceroute -T -p80 varelasnkrs.com
traceroute to varelasnkrs.com (129.151.227.103), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.183 ms 0.222 ms 0.250 ms
2 96.120.60.137 (96.120.60.137) 11.240 ms 11.227 ms 11.214 ms
3 162.151.125.157 (162.151.125.157) 11.199 ms 11.186 ms 11.172 ms
4 68.85.243.154 (68.85.243.154) 11.478 ms 11.464 ms 11.452 ms
5 96.216.60.245 (96.216.60.245) 11.116 ms 11.102 ms 11.129 ms
6 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 12.186 ms 12.832 ms 12.813 ms
7 4.68.37.245 (4.68.37.245) 12.068 ms 9.553 ms 9.508 ms
8 ae1.3107.edge1.Marseille3.level3.net (4.69.158.178) 167.303 ms 167.997 ms 171.596 ms
9 140.91.250.25 (140.91.250.25) 166.889 ms 140.91.250.10 (140.91.250.10) 166.875 ms 140.91.250.7 (140.91.250.7) 166.516 ms
10 129.151.227.103 (129.151.227.103) 172.088 ms !X 169.430 ms !X 168.920 ms !X
$ sudo traceroute -T -p443 varelasnkrs.com
traceroute to varelasnkrs.com (129.151.227.103), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.233 ms 0.199 ms 0.144 ms
2 96.120.60.137 (96.120.60.137) 8.942 ms 8.879 ms 8.842 ms
3 162.151.125.157 (162.151.125.157) 15.399 ms 15.373 ms 15.355 ms
4 68.85.243.154 (68.85.243.154) 14.447 ms 14.413 ms 14.384 ms
5 96.216.60.245 (96.216.60.245) 14.358 ms 13.500 ms 14.308 ms
6 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 16.774 ms 19.883 ms 37.883 ms
7 4.68.37.245 (4.68.37.245) 41.848 ms 10.143 ms 10.021 ms
8 ae1.3107.edge1.Marseille3.level3.net (4.69.158.178) 168.263 ms 167.923 ms 173.439 ms
9 140.91.250.24 (140.91.250.24) 172.206 ms 140.91.250.3 (140.91.250.3) 172.403 ms 140.91.250.24 (140.91.250.24) 172.148 ms
10 129.151.227.103 (129.151.227.103) 167.089 ms 167.642 ms 172.447 ms
$ nmap -Pn varelasnkrs.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-03-04 20:54 UTC
Nmap scan report for varelasnkrs.com (129.151.227.103)
Host is up (0.17s latency).
Not shown: 998 filtered ports
PORT STATE SERVICE
22/tcp open ssh
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 11.51 seconds