Selfhosted

40296 readers

284 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Stuck on Let's Encrypt certificate issuance due to firewall issue even after opening necessary ports (lemmy.ml)

submitted 8 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

[–] epyon22@programming.dev 10 points 8 months ago (3 children)

Many home ISPs block port 80 and 25. You should be able to Google that and confirm. If that's the case you'll have to use a different method.

[–] webhead@lemmy.world 6 points 8 months ago

This is the answer. Pretty much every ISP blocks 80 They say it is because worms use it blah blah but it is exactly what you think. They don't want you running a web server. You're probably going to have to do the DNS challenge instead.

[–] someoneFromInternet@lemmy.ml 1 points 8 months ago (1 children)

to Google?

[–] epyon22@programming.dev 3 points 8 months ago

Google search "Does block port 80"

[–] someoneFromInternet@lemmy.ml 1 points 8 months ago (1 children)

ISP said that it does not block port 80

[–] kevincox@lemmy.ml 2 points 8 months ago

Try something like https://www.webpagetest.org/ or any other "proxy" service to confirm for youself if it is publicly accessible.