I am using homeaccessanywhere.com. You just install it, sign up, and input your token, and domain, and it does the rest.
The problem I am having is with the wiki I want to set up. I want to use book stack. But I can only access book stack on my local network with the port and IP addres.
I want to be able to use the domain I have with homeaccessanywhere.com to hit my home assistant server, and also put the port number at the end to access bookstack. How can I accomplish this with nginx proxy manager?
I found I can install apache 2. Would that be better to use instead? I have looked at walkthroughs, and video guides for the proxy manager, and it does not work to do what I want.
So I am either doing some thing wrong, or it is not going to work for what I need.
On your internet router:
Create a rule for incoming traffic on port 80, 443 and 2665 to be forwarded to your local NPM address.
On your NPM:
Create a virtual host for homeaccessanywhere.com that points to your local HA address:8123
Create a virtual host for something like bookstack.homeaccessanywhere.com that points to https://192.168.50.203:2665
That is way for regular domains/subdomains. No clue if homeaccessanywhere supports subdomains.
If not, then try just doing a port forwarding on your router: external port 2665 → 192.168.50.203:2665
Not quite right, you wouldn’t open port 2665 to the internet at all. Nginx communicates with the service running on port 2665 on the internal network and therefore eliminates the need of having that port exposed to the internet.
I have the ASUS ROG Rapture GT-AX11000 which according to asus, nat loopback is on and cannot be turned off. I just do not know where in the router to take advantage of that. Is that port triggering, port forwarding? Or something else?
Homaccessanywhere.com does not allow subdomains. I have a Duck DNS account, but could not get duck DNS to work, so went with something easier to configure. With duck DNS you can do up to 5 domains for free I think.
I am in Mountain Time in the USA, but up until 3am my time, if anyone wants to hit me up privately, and do a screenshare. I would offer money, but am unemployed.
i added the IP address and port number as a short cut to book stack in the side panel of HA. On pc this is the message I get: 192.168.50.203 is blocked. 192.168.50.203 refused to connect.
I then tried it on my Android phone just to see if anything different would happen, and it did. This is the message: Unable to connect to Home Assistant The Home Assistant hostname certificate mismatch, please review the Home Assistant certificate or the connection settings and try again.
Second, DuckDNS allows wildcard SSL, which lets you create subdomains on your DuckDNS subdomain, like home.mysubdomain.duckdns.org for example. All you need is your DuckDNS token for the request. Google, however, doesn’t like subdomains; so it’s recommended (by DuckDNS themselves) to register the subdomain under your ownership in your Google Account. If you do that, it will get rid of the spooky scary warning page every time you visit your subdomain using a Google powered browser.
EDIT Also, it can take up to 24 hours for a domain to be accessible. It’s very rare it takes that long. Most of the time it’s near instantaneous these days. However, I have personally encountered a few hour wait after domain registration before a web browser would allow me to visit/use said domain. YMMV. My best advice is to be patient. Easier said than done sometimes.
I have there now, It would not let me reboot the server until I adjusted the spacing and lines. It does not like copying and pasting. So hopefully I did it correctly.
This is what I had before: http: server_host: 127.0.0.1 use_x_forwarded_for: true trusted_proxies: 127.0.0.1
I am about ready to give up, as I have been on this for 3 weeks. If I could get duck DNS to work, I would be fine using that.
Believe you me, I’ve walked 1000 miles in your shoes. The first time I tried getting NPM to work, I spent a whole month trying and failing. I gave up and sat on it for a year. Then, randomly one day, I was ready to attempt it again and I consulted AI. All of the forums and walk-throughs couldn’t help me get over the hump. Just like you, I was using the wrong trusted proxy address. Once I found the correct address to use, VOILA! Now I’ve got HA, Plex, and a couple other apps hosted and it’s been smooth sailing ever since.
EDIT I only have 2 port forward rules in my router setup for NPM to work.
Depending on your router’s capability, the first rule is using protocol TCP/UDP, WAN as source zone, external port is 443, destination zone is LAN, internal IP is the static IP of my HA machine. Second rule is specifically for Let’s Encrypt to work in NPM. It’s identical to the first rule, but uses external port 80.
For your port forward rules, you do not need to include an internal port, just the external port.
In NPM’s config, I left it default. When it’s working, you’ll be able to visit NPM’s GUI at http://192.168.50.203:81 (essentially, your HA IP appended to port 81).
-or- regarding your last question, are you asking about adding proxy hosts? Or are you wanting to verify the trusted proxy address in the HA config file? I may be misunderstanding the question, sorry.
Let me ask you this - Are you running NPM as a HA App? Let’s take a step back and establish how you’re setup. Is your HA ran on bare-metal? Or is it a virtual host ran in something like Docker or Proxmox? How you’re running HA and NPM will ultimately determine what your trusted proxy address will be.
If you’re running HAOS on bare-metal, you can use the SSH App and run docker network inspect hassio in CLI, you’ll see a subnet field. That’s the one you’ll want to list as a trusted proxy. It’s the Supervisor Docker network that the NPM App is running on.
I am using virtual box on KDE Ubuntu Linux.
I have installed HA into Virtualbox.
I am using the NPM app installed through HA.
All my connections are wired, no wireless except for my Philips Hue and Fire TV.
I hope that is enough information. What else do you need to know? I cannot think of anything else to add. My internet is fiber, which should not matter for internal network stuff.
I do not understand this statement: If you’re running HAOS on bare-metal, you can use the SSH App and run docker network inspect hassio in CLI, you’ll see a subnet field. That’s the one you’ll want to list as a trusted proxy. It’s the Supervisor Docker network that the NPM App is running on.
I am not sure what to ask about it. The Vbox has a static IP address, I did not force that onto the VM, it just did it automatically.
You can disregard that statement. Running HA on virtualbox, as long as you’re using bridged adapter, will allow HA to communicate like any other host device on your network.
After making these changes, have you tried restarting your router and rebooting the HA machine?
From here, add a proxy host, add your domain (full subdomain address, like mysubdomain.duckdns.org), scheme is http, use your HA local ip, the port HA is using (if you left it default, it’s 8123), and I’d keep Block Common Exploits and Websockets Support toggled on. As long as you are using the correct trusted proxy address in the config, it should work.
Regarding SSL, if you’re using it (which you should for external access), I’d keep Force SSL and HTTP/2 Support toggled on
But, again, the subnets you’re using as a trusted proxy needs to include the Supervisor Docker Network subnet. Which, as I’ve mentioned previously, is probably 172.30.33.0/24 or 172.30.32.0/24. I doubt your local subnet 192.168.50.0/24 will suffice by itself.
I do not know IP addressing that well. So when looking on line, the subnet of the IP that VM in virtual box address is 255.255.2555.0
The VM’s ip address is 192.168.50.203
The virtual box network adapter is bridged, so it is using the same IP address range as my computers and the host OS. This is what the guide suggested when setting up HA.
Thanks for all the help, hopefully this works, and I will post an update either way.
