Why in gods name is does vera use a external dns (resolver1.opendns.org) before it even contacts the dns that is setup by the user? This seems have been introduced in their latest firmware upgrade.
Either this has been implemented by someone who doesn’t know what a dns is and how it works or it is supposed to be a backdoor to influence the behaviour of the vera.
Could anyone please try to explain?
Umtauscher
oh, I have had problems with that, you cannot override it through the gui, and its first choice over your own.
It got in the way with the gui working correctly as it sometimes phones home to pull stuff for web pages… example… validating user account name is available when setting up findvera account, or when choosing location (city/state). also seems to cause tunnel problems (not sure though). I found errors in logs where the opendns would sometimes work and sometimes fail.
I have two veras and put a ticket in on the first one when I had problems registering it. They fixed it for me. The second unit I had would not let me choose location, sometimes the text would show up, sometimes not, when it did, I would select the state and the dropdowns would disappear… after digging in the logs i saw dns failures.
Looked further and realized that opendns was first choice no matter what.
Found that I needed to edit /etc/config/network and pull the dns line out of there. Everything started working perfectly.
I emailed tech support and asked why this was and was I the only one that could not make my vera work with dns configured the way it was. No response to that.
Its not really the vera code, its the openwrt code. But should be fixed before putting in distro for vera users.
yes it seems to be 994 (as well as a beta release or two before…)
SQ suggested I update to MCV firmware .995 last night and everything works great locally now but Findvera is now not working anywhere with the browsers or SQ…is there anything I can do???
I don’t understand where you are editing edit /etc/config/network DNS entry…
Please Help… or is it a temp server issue???
in my case the opendns server was failing to resolve more often than not which crippled parts of the vera gui
besides… when I configure something and tell it what I want it do use for DNS, I expect it to listen to me and not continue to prefer a dns resolver that may not be working correctly. As soon as I got that out of the config which put my preference in as first choice things worked great. (I expect microsoft products to try to know what is best for me no matter what I tell them, but did not expect an embedded linux box to act that way) :o
The only reason I did this (on my second box), was because that was what tech support did do my first vera when it had problems. I figure they must realize something isn’t right as well…
ra2.findvera.com appears to be down or unusable. Findvera no longer works for me.
Can it be that firmware .994 won’t let ra2.findvera.com talk to our Vera2 units anymore???
I updated to fix the SQ remote issue yesterday.
If I revert to .988 I’ll lose SQ capability but that is all I can think to do.
Sorry that you are having this trouble >:(but am glad I’m not the only one to be tearing my hair out with the update… :-X
I don’t think it’s a problem with the release. I was able to use findvera after upgrading.
Well, I just assumed the server was temporarily down. But, I haven’t been able to log into it since I updated to UI3 this morning.
yeah… what you guys are seeing right now is something else…
ra2.findvera.com does not seem to be responding…
well its responding to pings, looks like webserver is down…
thats not part of the problem i was describing…
i’m just chiming in here as well- i can confirm that i’m unable to connect via squareremote and findvera.com- it does appear that ra2.findvera.com is down. i’m running u13 firmware, and my unit doesn’t seem to be reporting any connectivity problems.
i’m curious- has anyone tried to get squareremote to connect directly? i just tried bypassing find vera and using my domain for the IP, and port forwarding 49451 through my firewall, but that didn’t seemt to work, which is frustrating, because square does have a tickbox that seems to indicate you can bypass findvera and to this on a LAN…i suppose it’s just that the vera only uses that port locally.
oh, and i’ll just add that i’m a little disappointed in the outage and the way miacasaverde seems to be handling it, which is to be completely oblivious to the fact that their finder service is down.
i’d be ok with a few hours, but this has been down since last night. i love the product, really want these guys to succeed, but his is amateur hour, there’s plenty of open source server monitoring tools, and if they were actually hosting somewhere and not in cousin bobby’s basement, i’m sure the hosting provider would have notified them and bounced the server already. this kind of mickey mouse stuff does not bode well for their future success.
they might consider investing in a real hosting provider with some failover, clustering support, and general high availability.
Works for me… although I’m getting on ra1…
Ra2 must be server setup setup for the newer version of Vera…I had an issue with it when I originally installed the SQ remote app…the great support guys at SQ walked me through it and I think they were even surprised the ra2 was different.
I’ve not been able to connect with anything except locally…it has to be the server…I just went to .995 because I needed it to resolve SQ remote issue and it worked last night but not this morning…
I wish we could tell somehow if it is the server because according to my networking trouble shooting my Vera 2 unit is reporting everything is OK.
How can you tell if a server is down?
For anyone using SQ Remote who wants to bypass the vindvera server:
YES, you can simply use your WAN IP address with port forwarding.
One (obvious) issue with this usage scenario is that since most home broadband users don’t have static WAN IP addressed, you will have to manually enter a new IP into SQ Remote when your provider changes your address.
Additionally, opening up a hole in your router is somewhat of a security risk.
I don’t know anything about the SQ, but if it lets you put in a hostname or IP, many broadband routers support dyndns and will reregister their dns when it changes. dyndns is a free service. I have used it for years to allow me to remotely address my broadband router.
Just register with dyndns.com (or one that your router supports) and configure the router to do its thing. Then the remote should always have the correct broadband address. I have had linksys and actiontech routers that both support dyndns.
Just remember - if you open a door for yourself, it’s open for anyone.
We don’t know if there’s a possibility that hacker could somehow cause Vera to execute an arbitrary shell command, and if he can you’re screwed.
[quote=“TheGadgetGuy, post:14, topic:165857”]For anyone using SQ Remote who wants to bypass the vindvera server:
YES, you can simply use your WAN IP address with port forwarding.
One (obvious) issue with this usage scenario is that since most home broadband users don’t have static WAN IP addressed, you will have to manually enter a new IP into SQ Remote when your provider changes your address.
Additionally, opening up a hole in your router is somewhat of a security risk. [/quote]
hey gadgetguy- i’ve thought that should be possible, but it won’t work for me using the default port in square remote, which is 49451 or something along those lines. do you have to open up 80 as well? have you done this yourself and which ports did you open?
oh by the way- i’ll also just note that ra2.findvera.com is still down…no comment or acknowledgment from vera, 2 plus days and counting. not good, this displays an alarming lack of professionalism and investment in basic IT tools to support a finder service like this one.
if my NAS does down in my home, i get notified, at the very least someone from vera should be aware of the situation.
@Theevaluator- Yes, basically you will simply need to forward port 49451 in your router to point to 49451 on the Vera box. You don’t (and shouldn’t) open port 80.
In SQ Remote, select the ‘Use fixed IP’, and deselect the ‘use findvera’.
It is faster and more responsive than using findvera.
Good luck. Let me know what happens.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules