top 19 comments

sorted by: hot top controversial new old
[–] 13 points 1 year ago* (3 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.

  • source
  • hideshow 3 child comments
  • load more comments (1 reply)
    [–] 7 points 1 year ago (1 child)

    The domain name in the certificate has to match the one in the browser. Does it? You haven't said.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 3 points 1 year ago (6 children)

    How does it fail exactly? Surely there is some error message.

  • source
  • hideshow 6 child comments
  • [+] [S] 1 point 1 year ago* (last edited 1 year ago) (5 children)
  • [–] 2 points 1 year ago (2 children)

    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.

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

    What does your nginx config look like for ssl? It should specify a certificate and key file - that certificate subject needs to match your fully qualified domain name (fqdn). Certificate can have subject alternative names (SAN) for other names and even IP addresses.

    For instance, you could have a single certificate for foo.bar with a SAN for just foo and an IP SAN for 192.168.1.30.

    Certificates also need to be signed by a certificate authority (CA), and in order for your browser to visit https://foo.bar/ without a warning your browser must trust that CA.

    If you did a self signed cert, this is most likely the problem you're running into.

    It's important to know that your communication is still encrypted because of SSL, but since your browser doesn't trust the CA (or the subject doesn't match the FQDN) the browser will say it's not secure.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 2 points 1 year ago (2 children)

    Is your firewall allowing port 443 (https) traffic?

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

    It’s most likely that your external IP is resolving to your firewall and it’s not redirecting LAN traffic.

    Either setup a redirect for LAN or setup a custom DNS entry on your router pointing to the server IP.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 1 point 1 year ago (2 children)

    If you do a DNS lookup (through nslookup or many other tools) on the client you're using to connect, does it get the right IP back?

  • source
  • hideshow 2 child comments
  • [–] 1 point 1 year ago

    make sure ports 80 (htttp) or 443 (https) are unblocked on your server

  • source
  • [–] 1 point 1 year ago (1 child)

    I suggest you check out pangolin. For me it’s worth about $12/year to not have a domain pointing directly at my home network, but instead have a layer of privacy and security. Running geofilter and crowdsec is really nice. Sometimes my logs show more than one blocked connection attempt per second. Another option if you want a free service is cloudflared tunneling.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)