Reverse proxy for home automation

Homelab
1

Hi!

I just installed home assistant on a raspberry pi and want to set it behind reverse proxy. So I installed nginx on my fedora server (running in a proxmox vm) and this is the config file:

server {
    listen 80;
    server_name dom.jeansibelius.net;

    location / {
        proxy_pass http://something.something.something.100:8123/;
    }
}

I have set up port forwarding on my router (80 => nginx_server:80, 443 => nginx_server:443).
Also I have set up subdomain (dom.jeansibelius.net) to point to my public ip address.

So when I go to http://dom.jeansibelius.net/ I should see my home assistant, but I do not…
I only see “Secure site not available” and after accepting I see “connection was reset”.

Nothing in /var/log/nginx/access.log and in /var/log/nginx/error.log.

Can you guys help me?

Kazimierz Krauze

2

You will need to configure your DNS to point there as well. Not sure what you are using for DNS. Is it safe to assume you are using ISP defaults?

1 Like
3

*.jeansibelius.net points to my public IP, I’m using Cloudflare.

4

Does your local DNS have a record for that? What does dom.jeansibelius.net point to locally? It should point to your NGINX server and nginx will direct from there assuming ports are configured correctly.

5

Thank you for your reply, but I’ve given up with a reverse proxy.

1 Like
6

I’ve been using nginx reverse proxy manager in docker with pihole (in docker as well) for several years and it works good for me.

I do not have an internet facing domain, so I use home.arpa as my internal domain. I created a DNS record to point that domain to npm, and, I created DNS records (alias’s really since they all share the same IP) for each application name.

I’m currently hosting 18 containers on a RPI-4 and I’m averaging about 18% CPU utilization and about 2.5gb of RAM (out of 8GB). It’s all for a one-person homelab, but it works great for me.

1 Like