Hello everyone,

I recently started to redo my first and messy homelab (Raspberry pi with Home Assistant + old hardware pc as Proxmox-server power controlled by HA) to a NUC. I used a ddns + Port for most things.

For my goal, I want to get most of the things Google does for me (password manager, docs, cloud, etc) to my server. Not because I hate google or something, I just want a goal to keep me motivated to learn and understand my hobby.

I followed a guide on this subreddit and got most of it working.

I use my Foundryvtt VM as an example of my problem.

Lets say my ddns ist “example.dedyn.io”.

  • If I’m not on my local Network, everything works like it should. I go to “foundry.example.dedyn.io” and can use Foundry.
  • If I do the same on my Local Network I get “NET::ERR_CERT_AUTHORITY_INVALID”
  • If I use “example.dedyn.io:12345” I can get to Foundry. The port is opened by the Fritzbox to the Foundry VM and I would love to close the port, when everything is working.
  • If I put “192.168.178.103 foundry.example.dedyn.io ” in the hosts file of my PC It works like I want it to work. So Nginx ist working, I think.

I use a Pi-hole as local dns (set in the Fritzbox as local and normal dns).
foundry.example.dedyn.io is linked to the ip of Nginx in the local dns setting of Pi-hole.

Sometimes “foundry.example.dedyn.io” doesn’t show the Error but I get to the login Page of my Fritzbox.

I think my SSL Certificate from Let’s Encrypt gets a timeout because I have a loop somewhere, but I have no idea how to troubleshoot from here. I tried to find something via google, but it is hard to find a similar problem, without knowing the real issue.

The thing that worries me the most is, “fritz.box” is still working, even if my local dns in the fritzbox menu is set to the Pi-Hole. Maybe my local dns is the problem, but I don’t know how to test it.
I hope somebody can point me in the right direction.

Thanks in advance!

  • m_randall@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    First thing I would do is dig the address you’re going to to make sure it’s what you expect it is. I’d also look at the certificate to see what it’s presenting. Lastly - look at your nginx logs to try and see if that will give you a clue.

    I’m guessing you’re not hosting your own authoritative DNS and since putting an entry in hosts works my first inclination would be your DNS setup is off.