37
Stuck on Let's Encrypt certificate issuance due to firewall issue even after opening necessary ports (lemmy.ml)
submitted 7 months ago by someoneFromInternet@lemmy.ml to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments

Hello everyone,

I've been trying to set up a Mumble voice chat server on my home network using a Debian server. As part of the setup process, I need to obtain an SSL certificate from Let's Encrypt for secure HTTPS access to the server. However, I'm encountering an error when running the Certbot client to request the certificate.

Here's the command I'm running:

sudo certbot certonly -d mydomain.com

But I get the following error message:

Timeout during connect (likely firewall problem)

I've checked my firewall rules and confirmed that I've opened port 80 as required for the Let's Encrypt verification process. Here's the relevant rule in my ufw configuration:

80/tcp ALLOW Anywhere

Despite this, I'm still getting the timeout error. Has anyone else encountered this issue before? What steps should I take to troubleshoot further?

Thanks in advance for any advice!

you are viewing a single comment's thread
view the rest of the comments
[-] witten@lemmy.world 18 points 7 months ago* (last edited 7 months ago)

Since this is on a home network, have you also forwarded port 80 from your router to your machine running certbot?

This is one of the reasons I use the DNS challenge instead... Then you don't have to route all these Let's Encrypt challenges into your internal network.

[-] someoneFromInternet@lemmy.ml 2 points 7 months ago

like this?

[-] scott@lem.free.as 4 points 7 months ago

You don't need UDP on port 80 forwarded through. HTTP is TCP only.

[-] domi@lemmy.secnd.me 2 points 7 months ago

HTTP/3 is UDP as well but only on port 443.

[-] witten@lemmy.world 3 points 7 months ago

Maybe...? I'm not familiar with that router software, but it looks plausible to me...

load more comments (1 replies)
this post was submitted on 10 Mar 2024
37 points (95.1% liked)

Selfhosted

39683 readers
540 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz