EDIT: sorted thanks everyone!
Omg so close to remote access for my #HomeLab using #Pangolin CE.
I can expose web services with authorised or open access, I can remote ssh to my Proxmox nodes! I wasn't even sure ssh was possible.
The only thing I can't do yet is expose #HomeAssistant which is the original purpose of setting all this up 🤦♂️
The problem is either because HA is running (as HAOS) in a different VM, or because it isn't set up for https. I'm not sure.
Any ideas appreciated!
@happyborg I just tried moving my Newt node that serves HA to another machine. Can confirm, somehow the main page loads, but it says it can't connect to the service.
A quick search tells me you might need to add that machine as a trusted proxy: https://community.home-assistant.io/t/reverse-proxy-using-nginx/196954
If that doesn't work, try the add-on I mentioned before, it works wonders.
If everything else fails, Nabu Casa allows you to bring your own domain to their remote access, if you're a paying customer.
@nanianmichaels I have a site online using the Newt add-on and have set up the resource but still get "unreachable". Now looking at the configuration.yaml. Do you know if I should use 127.0.0.1 or does Newt add-on have its own IP?
@happyborg If 127.0.0.1 gives you an unreachable status, then try with the machine IP.
I haven't found why sometimes 127.0.0.1 works and other times doesn't, so I've defaulted to always use the machine IP for everything.
Though HA apps/add-ons run on Docker, within their own internal IP on the 172.x.x.x range, and AFAIK you can't run them with "host" as a network, so that would explain why 127.0.0.1 won't work.
@nanianmichaels I found that I'm getting "unreachable" only when the machine I'm using has the Pangolin CLI "up". If I 'pangolin down' and access the URL I get internal server error in the browser. So I guess the config isn't right somewhere.
But oddly, pangolin up/down doesn't affect access to resources exposed in the VM with Newt and Portainer.
I'm a bit lost at the moment. It's probably some simple config setting. The pangolin docs about the add-on aren't definitive.
@happyborg Let me know if you need me to tell you my configuration settings, so you can compare with yours.
Also, don't enable health checks on Pangolin until you have it working. If health checks are on and the service state is "unhealthy", then Pangolin will not serve you the page, even though everything might actually be OK.
It can a bit fiddly at first, yes.
@nanianmichaels Can you show me what you have in configuraion.yaml I've tried lots of trusted proxy settings but not sure if the Newt add-on has its own IP and how to find it if it does.
I've disabled authentication in Pangolin (no health checks enabled yet). Not sure how to debug. The Newt log is fine, the HA logs seem ok (except when I mess up the config!)
There you go:
http:
# ssl_certificate: /ssl/selfsigned/selfsignedCert.crt
# ssl_key: /ssl/selfsigned/privateKey.key
use_x_forwarded_for: true
trusted_proxies:
- 172.16.0.0/12
- 127.0.0.1
I should add that these come from a few years ago, well before I started running Pangolin.
You'll probably be OK with just the 172 IP range.
@nanianmichaels Thanks! I have it working now thanks to you and others for helping.
@happyborg you may create a "newt"-endpoint in your homelab. This one will connect to the external Pangolin.
*Through* this connection you can expose any local web service. (One or many.)
There should be documentation describing this...?
@happyborg Probably you know all this - and I misunderstand the problem...
@udob Thanks. I have several things working but am now adding Newt to HAOS VM using the HA App... I think this is what I needed to understand. Fingers crossed and thanks very much for messing with your system to help!
Install bonfire.cafe
Get the full app experience
