Selfhosted

46672 readers

456 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Can't get DNS to work on web server (reddthat.com)

submitted 3 days ago* (last edited 2 days ago) by dr_robotBones@reddthat.com to c/selfhosted@lemmy.world

30 comments fedilink hide all child comments

I'm trying to self host my portfolio on an old laptop running Ubuntu server. I've successfully set up docker and nginx. I got a DNS subdomain from freedns.afraid.org.

The IP connected to the DNS matches my server's public IP address.

I can connect with https://mypublicip/ from outside the network, but it shows as an insecure connection and the https has lines going through it in the browser.

Any attempts to connect to the website via DNS have failed, and trying to connect via IP on port 80 fails as well. I really have no clue what is going on, let me know if you need more information, or if this is the wrong place to ask for help with this sort of thing.

Edit: Whatever problem I had before, it seems its been fixed. However my subdomain is being blocked by ISPs. Thank you for the help everyone, I'll probably have to do cloudflare tunneling instead of fully self-hosting it.

you are viewing a single comment's thread
view the rest of the comments

[–] SnotFlickerman@lemmy.blahaj.zone 11 points 3 days ago* (last edited 3 days ago) (2 children)

Have you set up certificates with LetsEncrypt or something similar?

Since you're running it on your own hardware and obviously have admin privileges, you could try out Certbot:

https://certbot.eff.org/

HTTPS requires signed certificates to be able to connect, that's part of the trust provided in the security. Also, HTTPS is port 443 while HTTP is port 80.

[–] osaerisxero@kbin.melroy.org 4 points 3 days ago (1 children)

This is likely correct but the browser's errors should be telling you what the error(s) is/are.

[–] dr_robotBones@reddthat.com 1 points 2 days ago* (last edited 2 days ago)

The error was: ERR_CONNECTION_TIMED_OUT. I also got an ERROR_CONNECTION_REFUSED earlier.

[–] dr_robotBones@reddthat.com 2 points 2 days ago

Yes, that's what I did.