Comment

Comment on [question] Help me access my local homeserver using a public domain name

0x01@lemmy.ml ⁨3⁩ ⁨weeks⁩ ago

You set the A record to your internal ip address from within your router?

Nginx configs have a lot of options, you can route differently depending on the source context

So a couple questions:

Do you only want to access this from your local network? If so setting up a domain name in the broader internet makes no sense, you’re telling the whole world what local ip within your switch/router is your server. Make your own dns or something if you just want an easier way to hit your local resources
do you want to access this from the internet, like when you’re away from home? Then the ip address you add to your a record should be your isp’s public ip address you were assigned, it will not start with 192.168, then you have your modem forward the port to your local system (nginx)

If you don’t know what you are doing and have a good firewall setup do not make this service public, you will receive tons and tons of attacks just for making a public a record.

source

Sort:hotnew top

TheHobbyist@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago
The A record was set on my registrar, so on a public DNS, so to speak.

It allows me to use HTTPS on a private service without setting up any custom DNS locally and without me using any selfsigned certificates and with all my IP addresses being private. It’s a good solution for me to have the real certificates using the default public infrastructure while keeping everything private. What’s the danger of sharing that my private server is accessible at 192.168.10.20 for the external world? What could they do with that information?

I use my tailscale network to which I expose my local network to allow remote access. Works great for me.
source
- 0x01@lemmy.ml ⁨3⁩ ⁨weeks⁩ ago
  Then next I would examine the redirect and check your stack, is it a 302, 304, etc, is there a service identifying header with the redirect?
  
  After that I would try to completely change your setup for testing purposes, greatly simplify things removing as many variables as possible, maybe setup an api server with a single route on express or something and see if that can be faithfully served
  
  If you can’t serve with even a simple setup then you need to go back to the drawing board and try a different option
  
  source
  - TheHobbyist@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago
    Opening up the network developer tools in Firefox, I’m seeing the following error: NS_ERROR_UNKNOWN_HOST, though I haven’t been able to determine how to solve this yet. It does make sense, because it would also explain why curl is unable to resolve it, if the nameserver is unreachable. I’m still confused though, because cloudflare, google and most other DNS’s I’ve tried work without issue. Even setting google’s dns in firefox does not resolve it.
    
    source