| 15 Apr 2025 |
conr | i just did the local unencrypted version by opening the port on the firewall. | 23:05:01 |
@hexa:lossy.network | never tried that tbh | 23:05:23 |
@hexa:lossy.network | the nixos test tests plain http though | 23:05:40 |
conr | so you did the reverse proxy with nginx? | 23:07:01 |
@hexa:lossy.network | yes | 23:07:05 |
@hexa:lossy.network | as documented on the wiki | 23:07:09 |
conr | ok but how does that domain work, is it internal or public facing? | 23:07:35 |
@hexa:lossy.network | for me it is a public domain pointing to an internal ip | 23:07:55 |
conr | so it won’t resolve outside the network? | 23:08:16 |
@hexa:lossy.network | it will, but you will not be able to reach it | 23:08:26 |
conr | oh right, that’s what i meant. | 23:09:29 |
conr | actually i started that but had a acme config issue | 23:10:03 |
conr | @hexa do you have a config setup for amce registrations? | 23:11:55 |
@hexa:lossy.network | https://wiki.nixos.org/wiki/ACME | 23:12:14 |
conr | do you use cloudflare for dns? | 23:24:32 |
@hexa:lossy.network | lol no | 23:31:57 |
@hexa:lossy.network | domain is at porkbun, delegated to desec | 23:32:11 |
conr | porkbun, me too | 23:35:11 |
conr | how do you do auth? | 23:35:22 |
@hexa:lossy.network | source ip | 23:37:21 |
conr | can you explain more? | 23:38:46 |
@hexa:lossy.network | https://www.home-assistant.io/docs/authentication/providers/#trusted-networks | 23:40:10 |
conr | i mean for generating acme ssl certs | 23:40:39 |
conr | i only see api token and user/pass options in the wiki for DNS Challenge | 23:42:08 |
@hexa:lossy.network | well you need to check the dns providers that lego supports and how to set them up | 23:42:34 |
@hexa:lossy.network | https://go-acme.github.io/lego/dns/ | 23:42:44 |
conr | how do you do it with porkbun? | 23:42:54 |
@hexa:lossy.network | delegation to a nameserver I run | 23:43:15 |
@hexa:lossy.network | and dynamic updates to that | 23:43:22 |
conr | oh i see it on leggo | 23:44:13 |