New guy here with new guy questions…
When my ISP changes my cable modem’s IP address as they do from time to time- does Vera2 broadcast it’s new/current IP address to MiOS so I can still log into my dashboard from MiOS when away from home via web browser?
If I know my home’s IP address can I setup port forwarding in my router to directly log into Vera2 like I do when I’m at home?
If so- what port(s) does Vera2’s GUI run on- and if it’s port 80- is that end user configurable cause my ISP blocks webservers (port 80) on home internet accounts.
Vera shouldn’t have a problem finding you with a dynamic isp.
You can set it up for port forwarding but that means setting a static internal ip for Vera and using a different port number so it won’t be blocked. Then set up port forwarding with those numbers.
You can use a free hosting service like dyndns.org to access your setup via internet with a unique web address. That too will find your dynamic isp address.
I have all my devices set as static ip addresses because I use VNC often and I also port directly into my Panasonic Webcam. Vera2 is already setup and running well as a static IP device.
I went into advanced/net & wireless/ tab where you setup network type, static address, etc… but I don’t see anywhere for changing Vera2’s GUI port?
If I click on the “Advanced Configuration” link from in the Net & Wireless tab- it pops up a new window with “NOT FOUND- The requested URL /cgi-bin/webif/info.sh was not found on this server”.
Typically your router would allow you to do a mapping from port X on the outside to port Y on the inside. That way, you can leave Y at 80 for Vera, your webcam, etc., so they are still reachable internally without providing an explicit port number. It’s also easier to maintain because it’s all in one place, i.e. your router.
Thanks oTi@…
Just wasn’t sure if I could change Vera’s GUI port to something other than 80, but I set the port forwarding to Vera’s IP at port 80 in my router and now I have direct access from remote locations as if I were still om my home network ;D
, but I set the port forwarding to Vera's IP at port 80 in my router and now I have direct access from remote locations as if I were still om my home network
Password protected, right?[/quote]
Thanks for the reminder…
No way to password protect access to port forwarding AFAIK.
So I leave the forwarding to VERA turned off by default which requires logging in to my password protected (DD-WRT FW) router to enable forwarding. I have “Allowed Remote IP Range” set to only accept connections from my static IP address from work so only someone from my work IP can remotely log into the router to turn on the port forwarding for Vera (if they know my home IP address, which port I use for remote router log in, my username and password to get in to the router). Hopefully I’ve covered all the bases- oh and I have Vera’s radio turned off!
You can also force Vera to ask for a password by going to the myMios systems page, click on settings, and set “Require local http authentication” to yes. Click on “Learn more” to find out more about what happens when this is done.
Vera maintains SSH tunnels to mios servers - so servers always know your IP.
No port forwarding is required unless you want to bypass mios and access Vera directly.
Given things Vera can control I’d never risk opening ports for direct access - someone may have way too much fun.
PLEASE NOTE: my response will only be helpful to those that want to or already port forward to apache or some other web engine that can do proxy and reverse proxy.
I saw this post and wanted to play a bit further as it wasn’t clear (or crystal clear rather) how to password protect the vera ui. I have had the unit for only a couple days so please take this for what it is worth and I’m learning as I go along (obviously with the help from these posts and the manual).
Anyways, since it was not clear on how to password protect the vera UI and I won’t simply port forward all traffic to the vera (couple reasons, 1. not secure, 2. I’m already port forwarding 80 and 443 to apache). I decided to dig into simply adding a VHOST to the apache instance that I’m already having all traffic forwarded to, I verified that the proxy module is loaded in Apache, then I added the following configuration lines to my section:
Now when I go to my home URL http://myhome/cmh/, the VERA interface looks to work in full and I’m able to control the devices I currently have configured. At this point, the test appeared good which means I can add allow lists via apache or .htaccess files as necessary.
I do have further research to do regarding SSL to make the proxy available for https however this should be trivial at this point.
Again, while this is not meant for the general user, I only wished to provide this information as there was an alternate method available and if so inclined.
The proxy settings below are great for me given I already have a secure proxy for other things. I do use SSL for my proxy, this did work fine with SSL which I recommend if you don’t want your passwords sniffed. The only change I needed to make was to allow my other cgi-bin traffic through so I changed the last two lines with /cgi-bin/ to the following (adding the /cmh/):
[quote=“watchdogrr, post:12, topic:168015”]PLEASE NOTE: my response will only be helpful to those that want to or already port forward to apache or some other web engine that can do proxy and reverse proxy.
I saw this post and wanted to play a bit further as it wasn’t clear (or crystal clear rather) how to password protect the vera ui. I have had the unit for only a couple days so please take this for what it is worth and I’m learning as I go along (obviously with the help from these posts and the manual).
Anyways, since it was not clear on how to password protect the vera UI and I won’t simply port forward all traffic to the vera (couple reasons, 1. not secure, 2. I’m already port forwarding 80 and 443 to apache). I decided to dig into simply adding a VHOST to the apache instance that I’m already having all traffic forwarded to, I verified that the proxy module is loaded in Apache, then I added the following configuration lines to my section:
Now when I go to my home URL http://myhome/cmh/, the VERA interface looks to work in full and I’m able to control the devices I currently have configured. At this point, the test appeared good which means I can add allow lists via apache or .htaccess files as necessary.
I do have further research to do regarding SSL to make the proxy available for https however this should be trivial at this point.
Again, while this is not meant for the general user, I only wished to provide this information as there was an alternate method available and if so inclined.
Thank you,[/quote]
Best Home Automation shopping experience. Shop at Ezlo!