30
Can't get DNS to work on web server (reddthat.com)
submitted 1 year ago* (last edited 1 year ago) by 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
[–] [S] 1 point 1 year ago* (last edited 1 year ago) (2 children)

I get ERR_CONNECTION_TIMED_OUT when trying to connect to it. I don't get any error logs on the server itself. I also got an ERROR_CONNECTION_REFUSED earlier.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    And you've verified that the DNS record has the correct IP address? I would check the web server config to make sure it will respond to that name. See if there is anything in the access or error logs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago (1 child)

    Yeah the DNS' public IP matches my server's. The access logs have some connections from the SSL validation and from when I successfully connected using the public IP address. The error logs are empty.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    connection timeout doesn't sound like ssl problem to me. is the webserver actually running? i think i read nginx in a different post, you might look for a running nginx process using

    ps aux | grep nginx

    If it is running, is the connection working with normal http:// on port 80?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •