Need help with tailscale and Certbot standalone for new cert

[rg305]

Something is blocking the inbound HTTP connections.
You need to find out why and allow it.

[mrdp]

any idea what it might be?

[mrdp]

actually i'm new to this field and have very less idea about these things !

[rg305]

Speak with your HSP [Digital Ocean] - they may know more.

[mrdp]

i'm using tailscale , is it causing the issue?

[mrdp]

curl -i -m10 http://www.hornet.technology/.well-known/acme-challenge/y1PTWNViPqMriwcYvoyZmFwCDyQJRCDh6p9MSNux6aI
curl: (28) Connection timed out after 10001 milliseconds " got this when trying it from my other device.

[rg305]

@mrdp

i'm using tailscale , is it causing the issue?

I wouldn't know.
What do you do with it?
[how experienced are you with it?]

[MikeMcQ]

@mrdp

i'm using tailscale

A few helpers here use tailscale but I am not one of them. I changed the title of the thread in hopes of drawing their attention.

[mrdp]

thanks for your help @MikeMcQ @rg305 , i have found the issue and solved it! it was the digital ocean firewall !!

[jvanasco]

@MikeMcQ

@mrdp

i did not delete an active certificate it was expired

We mean "active" in different ways. While expired if your web service still referred to those file locations it is still active. A client will see an expired cert but will still be able to make a TLS connection (usually HTTPS).

Expanding on this...

Web Servers are fine with (re)starting services with an expired certificate. Clients will not automatically trust the certificate, but have the option to - and uptime is not affected.

Most (all?) web servers will fail on initialization and fail to start up if their configuration file point to an SSL Certificate that has been removed from the filesystem. This will create downtime until either the Certificate is replaced, or the config file remove/comments-out the SSL directives (which will give you port 80, but not port 443 services).