If I set the TasmoAdmin config to: “ssl”: true, I get: This site can’t be reached
If I set the TasmoAdmin config to: “ssl”: false, I get: This site can’t be reached
Yes, thanks. I should be able to reach it with http and let the Proxy Manager handle the SSL. I know how to set up the Proxy Manager with example.mydomain.com but I can’t figure out how to do it with mydomain.com:1234 which is how the OPEN WEB UI button is configured for TasmoAdmin and other Add-ons.
Basically I think it’s just more user friendly with it’s GUI. Just a few clicks and you have reverse proxying.
For people that are familiar and comfortable with NGinx or Caddy I think there is no benefit.
I’ve been struggling the last few days to get this add-on to enable remote access for other add-ons. Here’s my current config: Hass.io running on Raspbian, remote access available via https://mydomain.duckdns.org with NPM set up per the GIF in the OP, routers has ports forwarded of 80:80 and 443:443. I’m trying to access add-ons (for example, Grocy running on port 9192) via mydomain.duckdns.org/grocy. To set this up as a location, it appears I would need these settings in NPM:
location: /grocy
scheme: https
forward hostname/IP: (same IP as rpi3) 192.168.xx.xxx
forward port: 9192
Does this also require router port forwarding of 9192:9192? If so, and if I’m trying to minimize the number of ports opened at my router, is there a way to access Grocy from mydomain.duckdns.org/grocy without opening another port?
You don’t need to open more ports, one of the main reasons you would use a reverse proxy.
I’ve never used grocy but are you using https? Try to also see what others use to get grocy working with nginx as it will be a case by case basis for configuration, depending on what the addon uses.
The grocy addon is running on port 9192 and is accessible on my internal network at 192.168.xx.yyy:9192. Here’s how I set up the custom location:
This gives me a 502 Bad Gateway error. If I change the http to https, I get Page Not Found. I’m a novice when it comes to nginx and HA, so I’m not sure what to try next. I’ve exhausted Google and these forums, really only finding many other people with this same question.
and for home assistant i have a different port other than 443
its 6773
like when i open my.ddns.net:6773
I get my homeassistant to work from anywhere.
Please guide me,
Thanks
I have. As to why, the only reason was the nice web UI and the fact that this will probably be updated more often.
The switch was very easy, turn Caddy off, turn Nginx Manager on and configure.
No problems.