Getting Backup File from Cloud

My Vera Lite just won’t connect to the MIOS cloud. It is plugged into a router that is behind another router/cable modem that is used as a cable bridge only. To be able to access my Vera Lite remotely I put it into DMZ on the router it is connected to. I can access it by just typing the IP Address into my browser.

But I cannot back it up, because it always goes to the MIOS cloud Web site, which cannot find the unit. Is there any way to fix this?

Is there a way to log into the cloud and download backups, even if the unit is not connected to the Internet?

Can I create a local backup?

[quote=“nagyg, post:1, topic:188449”]But I cannot back it up, because it always goes to the MIOS cloud Web site, which cannot find the unit.[/quote]This is the first problem that you need to fix. Why can’t Vera connect to the Vera servers? Are you logging into the correct website for your UI version?
UI7 - https://home.getvera.com
UI5 - http://cp.mios.com

Are you blocking Vera’s egress with one of the firewalls?

Is there a way to log into the cloud and download backups, even if the unit is not connected to the Internet?
You need a Vera(not necessarily the originally backed up Vera) that is connected to the account. Login, click download.

Alternatively, you could contact Vera support and ask them to provide you with a copy.

Can I create a local backup?
Click the create backup button.

Firewall is off and I am going to the right Web site … When I am connected to VERA directly and click on “backup” it always takes me right to the cloud login …

Tech Support could not help me with the issue that it won’t connect to the cloud and suggested I should plug it into the bridge - but that is not physically possible as it is too far from the devices …

[quote=“nagyg, post:3, topic:188449”]Firewall is off and I am going to the right Web site … When I am connected to VERA directly and click on “backup” it always takes me right to the cloud login …

Tech Support could not help me with the issue that it won’t connect to the cloud and suggested I should plug it into the bridge - but that is not physically possible as it is too far from the devices …[/quote]

I thought on the latest UI7 I am able to create local backups without a network, but that was an issue on older versions.

You have something in your local network screwed up which is why VERA support can’t help you.

Unfortunately I am not on the latest UI7 firmware. I cannot figure out what could be screwed up - everything but VERA is working fine. The only thing I can think of that I am using www.unblock-us.com so I can stream Netflix, Pandora etc., to Europe. That requires that I set the DNS servers to :
One: 208.122.23.23
Two: 208.122.23.22
Three:184.106.242.193

Could that cause the Vera not connecting problem?

[quote=“nagyg, post:5, topic:188449”]Unfortunately I am not on the latest UI7 firmware. I cannot figure out what could be screwed up - everything but VERA is working fine. The only thing I can think of that I am using www.unblock-us.com so I can stream Netflix, Pandora etc., to Europe. That requires that I set the DNS servers to :
One: 208.122.23.23
Two: 208.122.23.22
Three:184.106.242.193

Could that cause the Vera not connecting problem?[/quote]

Did you used to have a ui5 account and now have a ui7 account?
Is this what you get? (First pic)

and when you go to settings and network do you get an error or internet ok? (2nd pic)

So, what is that IP address in the screenshot? A public IP that trips a login prompt to server: “HomeControl”. It appears that you have the Vera portforwarded. If so, that is a mistake.

What else, besides portforwarding, are you doing to the network traffic. Are you portforwarding other ports, that Vera might need, to other devices? Are you doing egress filtering? You mentioned a VPN service, is Vera passing through a tunnel?

Fix your network so that Vera can reach the internet and open a SSH connection to Vera’s servers on port 232, at a minimum.

As I stated initially, the first thing you must fix is Vera’s access to the internet and Vera servers. Only then can anyone determine if there is an actual problem with Vera, which I doubt.

It really depends on how you have your network setup, but I don’t think that changing Vera’s address settings will improve your situation.

By default, Vera gets its addressing from a DHCP server. Most consumer off the shelf routers are configured by default to provide DHCP service on the private LAN. Often the address space used is 192.168.1.x, but depending on the manufacturer, it could be something else. These typical routers are configured to use NAT and allow all outbound traffic. The NAT blocks all inbound traffic, except for return traffic for outbound initiated connections.

In this typical scenario, Vera is placed on the private LAN, not the DMZ, just like any other device in the home. You would then access Vera locally(while you are within your home) at the private address 192.168.1.x. After Vera has been locally configured and registered with a Vera server account, remote access is accomplished via the https://home.getvera.com website, not directly by a portforwarded IP address or DMZ.

How you have your network configured, at this point, is beyond my knowledge. But, the fact that you have Vera in a DMZ(essentially portforwarding) and Vera can’t connect to the internet tells me that however it is, it is not correct. Once you get your network properly configured, Vera will work as it is supposed to.

Edit: Looking at your previous posts(I thought I’d seen you around the forums for a long while), it looks like you broke your network configuration years ago. I see a 2013 post about a Vera 2 with UI4 that also was not able to reach Vera servers and you moved it to a DMZ.

[quote=“Z-Waver, post:8, topic:188449”]It really depends on how you have your network setup, but I don’t think that changing Vera’s address settings will improve your situation.

By default, Vera gets its addressing from a DHCP server. Most consumer off the shelf routers are configured by default to provide DHCP service on the private LAN. Often the address space used is 192.168.1.x, but depending on the manufacturer, it could be something else. These typical routers are configured to use NAT and allow all outbound traffic. The NAT blocks all inbound traffic, except for return traffic for outbound initiated connections.

In this typical scenario, Vera is placed on the private LAN, not the DMZ, just like any other device in the home. You would then access Vera locally(while you are within your home) at the private address 192.168.1.x. After Vera has been locally configured and registered with a Vera server account, remote access is accomplished via the https://home.getvera.com website, not directly by a portforwarded IP address or DMZ.

How you have your network configured, at this point, is beyond my knowledge. But, the fact that you have Vera in a DMZ(essentially portforwarding) and Vera can’t connect to the internet tells me that however it is, it is not correct. Once you get your network properly configured, Vera will work as it is supposed to.

Edit: Looking at your previous posts(I thought I’d seen you around the forums for a long while), it looks like you broke your network configuration years ago. I see a 2013 post about a Vera 2 with UI4 that also was not able to reach Vera servers and you moved it to a DMZ.[/quote]

I agree with all of the above. Sounds like a thread just for fixing your LAN would be a good place to start. And with that a picture of what you have physically wired to what and what components you have might help us point you in a better direction. Maybe we can route only the devices you need (TV’s or media deivces) threw the www.unblock-us.com servers and get the rest of you house back on the right track.

You are right, but that was a different router that was proprietary to the provider UPC. Vera 2 connected to the cloud server, but it used to become unresponsive quite often and I had to send someone over to power cycle the VERA, as on that router I couldn’t set up VPN.

When UPC offered a router that could be operated in bridge mode (as a cable modem), I jumped on that and installed a WRT54G/GL/GS with DD-WRT v24-sp2 (10/10/09) vpn - build 13064 and got a new Vera Lite.

The only problem I am having is what I described: I can access Vera only when it is in DMC, even when I am using VPN Just tested that). I also have Vera on a timer that power cycles it every 24 hours. So at the most I lose it for 24 hours. So this is pretty much rock solid, but I can’t do backups or upgrades :slight_smile:

Everything else I run there (Amazon FTV, Foscam Camera, Amazon Echo, AppleTV, windows laptops, iPhones, Android Phones) runs perfectly normal.

You are right, but that was a different router that was proprietary to the provider UPC. Vera 2 connected to the cloud server, but it used to become unresponsive quite often and I had to send someone over to power cycle the VERA, as on that router I couldn’t set up VPN.

When UPC offered a router that could be operated in bridge mode (as a cable modem), I jumped on that and installed a WRT54G/GL/GS with DD-WRT v24-sp2 (10/10/09) vpn - build 13064 and got a new Vera Lite.

The only problem I am having is what I described: I can access Vera only when it is in DMC, even when I am using VPN Just tested that). I also have Vera on a timer that power cycles it every 24 hours. So at the most I lose it for 24 hours. So this is pretty much rock solid, but I can’t do backups or upgrades :slight_smile:

Everything else I run there (Amazon FTV, Foscam Camera, Amazon Echo, AppleTV, windows laptops, iPhones, Android Phones) runs perfectly normal.[/quote]

So are you saying you don’t want to fix you shotty home network setup? It’s clear you have issues with this an it’s not setup right, we are trying to help you get to the root of the problem not come up with a mickey solution only for backups. But if you don’t want to fix that then you can update your UI7 firmware to a newer version and get local backups and restores. This may include you having to temporary move the vera to properly working internet connection do the update and return to normal position after.

Of course I would like to fix it! But please consider that I am no computer expert. I can take it out of DMZ and then I will no longer be able to access it … If you’re willing to look at it I could pm you my passwords… Also, I’m physically over 4000 miles from the unit, so I can only work this remotely …

This was the last recommendation from tech support:

"From what I understand, you are able to connect to your Vera controller if it is directly connected to your main router. This means that it can reach the Internet from there.

“You may also try checking the forwarding rules from one router to the other, firewall settings, and also routing rules. Also, you may also try setting an IP reservation for your Vera controller, and also adding Vera to DMZ if your router does support it”

Connecting Vera directly to the Ethernet port of the modem (Ubee EVW3226EU) allows access only via the MIOS servers, also there is no VPN OR DMZ or anything else that can be set on this modem. I ended up with a lot more downtime …

[quote=“nagyg, post:12, topic:188449”]Of course I would like to fix it! But please consider that I am no computer expert. I can take it out of DMZ and then I will no longer be able to access it … If you’re willing to look at it I could pm you my passwords… Also, I’m physically over 4000 miles from the unit, so I can only work this remotely …

This was the last recommendation from tech support:

"From what I understand, you are able to connect to your Vera controller if it is directly connected to your main router. This means that it can reach the Internet from there.

“You may also try checking the forwarding rules from one router to the other, firewall settings, and also routing rules. Also, you may also try setting an IP reservation for your Vera controller, and also adding Vera to DMZ if your router does support it”

Connecting Vera directly to the Ethernet port of the modem (Ubee EVW3226EU) allows access only via the MIOS servers, also there is no VPN OR DMZ or anything else that can be set on this modem. I ended up with a lot more downtime …[/quote]

First Becareful about PM’n passwords to anyone.

Second I think we physically would like to know how things are connected and what devices you have. Maybe a little sketch of your network starting with the cable Modem to the Wrt54g to ??? Do you have other switches. On the cable modem is there only one cable from modem to the Wrt54g? Is there a switch or something after the Wrt54g or are all devices wire from there? Is there any wireless devices? Any other devices that not named?

Whats the local IP of the Cable modem and the Wrt54g?

The setup is very simple:

Ubee EVW3226EU in bridge mode. Once it is in bridge mode the GUI can still be reached at 192.168.100.1, but there is nothing that can be set but the password.

Ethernet cable from Ubee —> WRT54GL

Linksys WRT54GL (192.168.1.1) with DD-WRT v24-sp2 (10/10/09) vpn. Standard settings except the Static DNSs are set to:
DNS 1:192.168.0.1
DNS 2:208.122.23.23
DNS 3:208.122.23.22

Ethernet cable from WRT54GL to:

—> Vera Lite
—> Amazon Fire TV
—> Samsung TV

WRT54GL wireless to:

Foscam Camera
Amazon Echo
and - when I am there - to laptops, tablets and phones.

no switches.

Waring: Changing with your router’s configuration remotely is a great way to lock yourself out. Consider your actions carefully.

The first thing that I see is Static DNS 1 is set to 192.168.0.1 which is a private address range that is not on your network. It is almost certainly invalid and should be removed.

On the NAT/QoS tab; is there any port forwarding, port range triggering, port triggering, or QoS configured? Unless you’ve got very specific need for it UPnP should be disabled, and I’ve already stated that Vera should not be in the DMZ.

What about the Access Restrictions tab? Are there any that would affect Vera, who appears to be at 192.168.1.137?

You also have repeatedly mentioned that you are using a VPN version of DD-WRT and a VPN service provider. Do you have a VPN configured? If so, is the DD-WRT router configured as any sort of VPN client?

[quote=“Z-Waver, post:15, topic:188449”]Waring: Changing with your router’s configuration remotely is a great way to lock yourself out. Consider your actions carefully.

The first thing that I see is Static DNS 1 is set to 192.168.0.1 which is a private address range that is not on your network. It is almost certainly invalid and should be removed.

On the NAT/QoS tab; is there any port forwarding, port range triggering, port triggering, or QoS configured? Unless you’ve got very specific need for it UPnP should be disabled, and I’ve already stated that Vera should not be in the DMZ.

What about the Access Restrictions tab? Are there any that would affect Vera, who appears to be at 192.168.1.137?

You also have repeatedly mentioned that you are using a VPN version of DD-WRT and a VPN service provider. Do you have a VPN configured? If so, is the DD-WRT router configured as any sort of VPN client?[/quote]

Thanks! I will follow your advice and change the 1st static DNS when I am physically there, which will be in 10 days. The router is configured as a VPN server. I can try things more freely when I am there and than I will post again.

This was resolved by customer support. The problem was that the router blocked port 232. After forwarding this port to the Vera IP it could access the Internet
;D

I want to be glad that you got it working. But I am concerned that the fix is not correct. Portforwarding 232 is only slightly better than the DMZ port, which portforwards everything.

Vera does NOT require and in fact should not have ANY port forwarding in order to work behind DD-WRT. By default, DD-WRT routers allow all traffic out as well as reply traffic back in. This includes port 232 and I have successfully setup Veras behind DD-WRT with zero portforwarding. The SSH tunnels on 232 have no problem at all.

Unless you have altered something else in the router’s configuration that is blocking reply traffic, or have broken normal traffic filtering with your VPN setup, then no portforwarding is necessary for Vera. It is my contention that you still have a firewall issue and personally I would not allow SSH(232) to be port forwarded to Vera. I would not allow any portforwarding to Vera. Even more so after you disclosed the public IP address on an open forum.

As previously stated, your network setup is not correct. I’d recommend that you find a friend that knows how to do firewall/router configuration and have them fix your network for you. It ain’t right.