No longer able to access Vera 3 UI5 from outside network

Using: Vera 3, UI5, 1.5.622, Chrome, IE, Edge
Error Message: Could not select database status.

Hello Group,

For a few months, I’ve been unable to reach my Vera 3 receiving the above error message.
Realizing the mios/ezlo company can’t support these old systems forever . . . trying to determine if the problem is with the mios servers or my Vera / internal network.

(initiated from the portal)
(ALTUI style)

Although familiar with using WinSCP / Putty to ssh into my vera, I don’t have enough expertise to troubleshoot further.

Could anyone advise?

Thank You,

Pics attached . . .

I see you commented on this recent thread, can you SSH in to the Vera and ping does that reply? Is it a DNS issue as mentioned on this thread?

1 Like

This was happening to me a year ago but it did get resolved for me. I am currently able to log in and control devices using a few different browsers.

I’m running the same firmware 1.5.622 but I guess I’m directed to a different server? (fwd4). I tried changing 4 to 3 and saw the message you got.

At this point I’m reluctant to change anything for fear of breaking it. You should probably file a ticket with support though I’m not sure how much time they are willing to put into these legacy systems.

Check this note from last year…

Good Luck…

1 Like


Pinged from Putty. No issue there (results below)
I’ll re-read that thread, thanks for the research!


Using username “root”.

BusyBox v1.17.3 (2012-01-09 12:40:42 PST) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.

| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
_____|| |
||||___||| |____|
| W I R E L E S S F R E E D O M

-------------- Backfire (10.03) -------------------

*** MiOS LTD. ( ) ***

*** WARNING : ***
*** Any changes made to the system without ***
*** guidance from MiOS support will VOID ***
*** your future Support requests ***

root@MiOS_XXXXXXXX:~# ping
PING ( 56 data bytes
64 bytes from seq=0 ttl=119 time=8.474 ms
64 bytes from seq=1 ttl=119 time=8.108 ms
64 bytes from seq=2 ttl=119 time=8.762 ms
64 bytes from seq=3 ttl=119 time=8.238 ms
64 bytes from seq=4 ttl=119 time=8.104 ms
64 bytes from seq=5 ttl=119 time=7.900 ms
64 bytes from seq=6 ttl=119 time=7.842 ms
64 bytes from seq=7 ttl=119 time=8.579 ms
^C ping statistics —
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 7.842/8.250/8.762 ms

Thanks RichD73 for responding.

I read your thread and believe symptoms are similar to zedrally’s.
Was able to initiate a trouble ticket via the Vera and opened the remote access portal.

Hopefully they can advise on my old EOL system.


Hi Chris,

Out of curiosity did you get your issue resolved?


1 Like

No, no resolution yet. Trouble ticket initiated but no response. I can’t tell if anyone from support has been inside my unit yet. But I test the remote access every morning . . .

Crossing my fingers that someone from the home company will take kindly to my situation. Not yet in a position to be able to upgrade to the current ezlo offerings.