can't connect to vera

So, last night Vera reactivated my ‘kirbyb’ account, and deleted my ‘kirbyb1’ workaround/clone account. Great! So now I can login to my vera account as ‘kirbyb’ with my password, it redirects to local 192.168.0.6, and all is well. So I deleted my Concierge information, and put in userid ‘kirbyb’ and my password, and… nothing… here’s the log (below). I deleted it more than once and restarted, I even restarted the Raspberry PI 3. I’m 100% certain the userid and password are correct. Here’s the log:

15-Feb-2018 07:45:49 I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha12.mios.com/autha/auth/username/kirbyb?SHA1Password=15B37AA3126160B1F5C1EC6E90569AF48C4269DE&PK_Oem=1
15-Feb-2018 07:45:50 V:VeraService:Wacthdog:Restart
15-Feb-2018 07:45:50 I:VeraService:Start
15-Feb-2018 07:45:50 I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/kirbyb?SHA1Password=15B37AA3126160B1F5C1EC6E90569AF48C4269DE&PK_Oem=1
15-Feb-2018 07:45:52 V:CSWebContainer:Cmd:/Log?
15-Feb-2018 07:45:57 V:CSWebContainer:Cmd:/Log?
15-Feb-2018 07:46:02 V:CSWebContainer:Cmd:/Log?
15-Feb-2018 07:46:07 V:CSWebContainer:Cmd:/Log?
15-Feb-2018 07:46:09 E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketTimeoutException: connect timed out
java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.S

It would appear that ‘vera-us-oem-autha11.mios.com’ is not a valid vera URL…

a little more information… (its still FAILING).

I tried a windows server, same problem. I searched some forums, these are apparently the names of the mios authentication servers:

vera-us-oem-autha11.mios.com |

| vera-us-oem-autha12.mios.com |

| vera-us-oem-authd11.mios.com |

| vera-us-oem-authd12.mios.com |

It would seem that autha11 and autha12 are down… (I’ll be calling Vera support later when they’re at work on the west coast to answer phones). If I try to contact the ‘d’ servers, I at least get a response.

I’m guessing there’s a call to ‘vera/mios’ that returns a list of authentication servers, and then the code maybe just uses the first one and doesn’t iterate through the list? I don’t know, I can’t look at the code… I unziped the jar file, but the classes are binary.

Kirby

More info. I contacted Vera support, and the auth servers are NOT down… The ‘a’ named servers are for authentication, and the ‘d’ named servers are device servers. The Vera tech guy couldn’t understand why the ‘a’ servers were being queried…

Here’s the query that times out:

16-Feb-2018 11:57:58 I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/kirbyb?SHA1Password=368F8D7D8CC44A660B127C9981E4B1E9B25752A2&PK_Oem=1

Sure enough, if you paste that https query into a browser it times out…

I’m 100% sure I’m using the correct password. IF I copy it from the concierge setup to the Vera login prompt, it logs me in.

Kirby

So I uninstalled Concierge, rebooted the PI, reinstalled Concierge, and same thing.

Kirby

i did mine about 5 times, with the same instructions - reinstall noobs headless

I keep hoping something will change, but it does not. I can NO longer get the concierge java app to work. When I put in my Vera login information, it seemingly can’t connect to the Vera Account servers. I have another Vera installation at a church, and I tried that username/password, and it times out also. I called Vera support and they examined my Vera controller and found no issues. My network works fine… My firewalls are working correctly, but the Java app can’t detect any Vera controllers.

Help?

Kirby