Impossible to reach the site

Help
1

My domain is:
asfundation.it
My web server is (include version):
ubuntu 20
The operating system my web server runs on is (include version):
apach2
My hosting provider, if applicable, is:
hetzner

I installed correctly certbot on my server but when i go to https://asfundation.it it load for a few minutes and then it response with "impossible to reach this website".
I need help please

2

I cannot reach your site using HTTP or with HTTPS. Thing to check would be any firewalls to make sure both port 80 and port 443 are open. Also check that the IP address in your DNS is still the correct one. I tried checking from multiple locations and I could not reach you on any of those.

Some example tests

2 Likes
3

I agree with @MikeMcQ

I believe you have a firewall (and / or router) between your server and the Internet that is filtering (blocking) access to Port 443 on your server, thus HTTPS is failing to connect.

From around the world Permanent link to this check report shows "Connection timed out".

And with this online tool Open Port Check Tool - Test Port Forwarding on Your Router this is shown

image
image1081×774 49.6 KB

$ nmap -Pn -p80,443 asfundation.it
Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-03-15 16:22 PDT
Nmap scan report for asfundation.it (49.13.169.129)
Host is up (0.18s latency).
rDNS record for 49.13.169.129: static.129.169.13.49.clients.your-server.de

PORT    STATE    SERVICE
80/tcp  open     http
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 3.99 seconds

$ curl -Ii http://asfundation.it
HTTP/1.1 301 Moved Permanently
Date: Fri, 15 Mar 2024 23:23:10 GMT
Server: Apache/2.4.41 (Ubuntu)
Location: https://asfundation.it/
Content-Type: text/html; charset=iso-8859-1

And HTTP is redirected to HTTPS

$ curl -Ii  https://asfundation.it/

^C

And HTTPS fails to connect.

1 Like
4

Yes now it works. Thank you all! I forgot to open port 443 because in the certbot instruction this isn't writen.

2 Likes
5

That's a good point, Certbot still assumes that people setting up HTTPS (which always defaults to TCP port 443) know at least a little bit of what it is and how it works - it's debatable whether it's Certbots job to tell you that sort of thing or not but we do see people here every day having problems because they don't know which ports to open.

2 Likes
6

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