| 16 Apr 2025 |
 @hexa:lossy.network | so why doesn't it listen on 8123 then | 23:29:32 |
 conr | i think i disabled ipv6 | 23:31:09 |
| conr | i only use ipv4 with WG | 23:31:23 |
| conr | so change ::1 to 127.0.0.1? | 23:32:05 |
| @hexa:lossy.network | possibly | 23:33:53 |
| @hexa:lossy.network | how did you disable ipv6? | 23:34:00 |
| conr | i am not sure but all my wg config is ipv4 addresses only | 23:35:02 |
| conr | that fixed it | 23:35:41 |
| @hexa:lossy.network | but 127.0.0.1 and ::1 are on lo | 23:37:52 |
| conr | i’m not following | 23:43:08 |
| conr | 127.0.0.1 is loopback for ipv4 and ::1 is loopback for ipv6. | 23:43:31 |
| @hexa:lossy.network | yes, they are on lo | 23:44:06 |
| @hexa:lossy.network | * yes, they are on the lo interface | 23:44:10 |
| @hexa:lossy.network | if home-assistant and nginx run on the same machine that should work | 23:44:24 |
| conr | so was your comment that its ok? | 23:44:40 |
| @hexa:lossy.network | your messaging is super unclear | 23:45:06 |
| @hexa:lossy.network | Redacted or Malformed Event | 23:45:15 |
| conr | In reply to @hexa:lossy.network
but 127.0.0.1 and ::1 are on lo what do you mean by this? | 23:45:20 |
| @hexa:lossy.network | here | 23:45:22 |
| @hexa:lossy.network | wg is for remote connections | 23:45:33 |
| @hexa:lossy.network | wg will connect to your nginx | 23:45:36 |
| @hexa:lossy.network | and nginx will connect to the local home-assistant | 23:45:42 |
| conr | right so 127.0.0.1 is ok to use with HA? | 23:46:01 |
| @hexa:lossy.network | yes | 23:46:23 |
| conr | so whats the best way to find HA plugins on nix? search nixos.org packages? | 23:49:16 |
| @hexa:lossy.network | yes | 23:50:00 |
| conr | whats the .tests mean? | 23:50:16 |
| @hexa:lossy.network | can be ignored | 23:50:39 |
| conr | how can i filter, “no package set” | 23:52:31 |
| conr | like i’m looking for unifi protect | 23:54:15 |
