Http protocol's disabled on *.mios.com domains?

Community Playground General Discussions
#1

Since this morning all my automation stopped. Upon checking, it seems my vera3 is offline (not reachable via apps or webui), but via ssh I can login to the system.

If I tail the /var/log.Init-LuaUPnP logfile, I get the following:
ERROR: failed to get auth token from: vera-us-oem-authd11.mios.com, curl/http: 6/0, is backup: 1
ERROR: failed to get auth token from: vera-us-oem-authd12.mios.com, curl/http: 6/0, is backup: 0

Trying to open these in the browser fails also. Changing the URL to https kinda works (in the browser).

It seems that EZLO is blocking all http traffic to the mios.com endpoints :frowning: causing my Vera3 to be kinda worthless :frowning:

Any other Vera3 “die hard” users that have this issue?

No longer able to access Vera 3 UI5 from outside network
#2

Same here for me, though my links access fwd3.mios.com (UI5 related I believe).
Lost access a few weeks ago for about 10 days, but it came back.

Suspect the days are approaching when us Vera3 die-hards will have to upgrade to keep up with the technologies.

Chris

#3

Please tell us the firmware version, it should use https, not http. You can also tell me the serial, in a private message.

#4

Hi @alecs,

It’s running version 1.7.1040. This is the latest version for the Vera 3 as far as I’m aware.

Regards,
Rogier.

#5

Will do a check and provide a solution. Non SSL is not ideal but if we won’t find the culprit I will enable non SSL data to be allowed if coming from the controller/gateway.

#6

Soooo, I found the issue.

It seemed strange that also vera alerts was not working anymore, so I dug a little deeper.

Apparently the DNS servers were gone or not responding anymore which caused all calls to aliases to simply fail. After adding new DNS servers, everything started working again and I can confirm that the vera 3 tries to connect to https endpoints :wink:

First determine if you have the same issue. Log in to your vera3 through ssh.
Then simply try a ping to google.com:

root@MiOS_Serial:~# ping google.com
ping: bad address 'google.com'

My fix: (be careful, you might break stuff…)
Login with root to your vera3 through ssh.
Execute “uci show dhcp” and inspect the “dhcp.@dnsmasq[0].server” entry (was missing in my config)
Add DNS servers to this variable and restart dnsmasq:

uci add_list dhcp.@dnsmasq[0].server="8.8.8.8"
uci add_list dhcp.@dnsmasq[0].server="8.8.4.4"
uci commit dhcp
/etc/init.d/dnsmasq restart

ping google.com should now work again :slight_smile:

And a big thank you to @alecs for wanting to help me with an officially unsupported device :slight_smile:

4 Likes