Author Topic: Cannot auth to Vera - Local server connectivity test fails  (Read 2288 times)

Offline zyphaz

  • Newbie
  • *
  • Posts: 9
  • Karma: +1/-0
Cannot auth to Vera - Local server connectivity test fails
« on: October 13, 2018, 12:41:55 pm »
I'm having trouble when testing connectivity from Vera Concierge locally.  When I hit the Connectivity test, I get a "There was a problem! Can't Connected to Vera!".  The error log shows that it fails auth 401 when trying to connect locally from the Concierge server to the Vera.  It looks like it pulls the token from mios.com correctly over the internet though?  Error logs below.

Code: [Select]
Oct 13, 2018 8:47:29 AM V:VeraConnect.VeraConnection:GetVeraAccess:UI6-SERIALNUMBER
Oct 13, 2018 8:47:29 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/USERNAME?SHA1Password=SCRUBBED&PK_Oem=1
Oct 13, 2018 8:47:29 AM I:VeraConnect.UI6Gateway:GetAuthToken:VTOKEN
Oct 13, 2018 8:47:29 AM I:VeraConnect.UI6Gateway:GetAuthToken:PK_Account:SCRUBBED
Oct 13, 2018 8:47:29 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/info/session/token
Oct 13, 2018 8:47:29 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-account12.mios.com:SCRUBBED
Oct 13, 2018 8:47:29 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/account/account/account/SCRUBBED/devices
Oct 13, 2018 8:47:29 AM W:VeraConnect.UI6Gateway:UI6VeraAccess: Setting Connection Info:UI6-SCRUBBED
Oct 13, 2018 8:47:29 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-device11.mios.com/info/session/token
Oct 13, 2018 8:47:29 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-device11.mios.com:SCRUBBED
Oct 13, 2018 8:47:29 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-device11.mios.com/device/device/device/SCRUBBED
Oct 13, 2018 8:47:31 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.3rd.4thOCTET/port_3480/data_request?&id=variableget&Variable=PK_AccessPoint
Oct 13, 2018 8:47:31 AM E:VeraConnect.VeraGateway:URLConnection:BadResponse:401
Oct 13, 2018 8:47:31 AM E:VeraConnect.VeraGateway:URLRequest:
Exception:java.io.IOException: Server returned HTTP response code: 401 for URL: [url]http://192.168.3rd.4thOCTET/port_3480/data_request?&id=variableget&Variable=PK_AccessPoint[/url]
java.io.IOException: Server returned HTTP response code: 401 for URL: [url]http://192.168.3rd.4thOCTET/port_3480/data_request?&id=variableget&Variable=PK_AccessPoint[/url]
   at sun.reflect.GeneratedConstructorAccessor16.newInstance(Unknown Source)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
   at java.lang.reflect.Constructor.newInstance(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
   at com.rtsservices.veraconnect.access.VeraGateway.URLRequest(VeraGateway.java:74)
   at com.rtsservices.veraconnect.access.UI6Gateway$UI6VeraAccess.URLRequest(UI6Gateway.java:264)
   at com.rtsservices.veraconnect.access.LocalRemoteManager.URLRequest(LocalRemoteManager.java:48)
   at com.rtsservices.veraconnect.access.UI6Gateway$UI6VeraAccess.FetchURL(UI6Gateway.java:281)
   at com.rtsservices.conciergeserver.CSWebContainer.CheckConnectivity(CSWebContainer.java:178)
   at com.rtsservices.conciergeserver.CSWebContainer.LegalCmd(CSWebContainer.java:137)
   at com.rtsservices.conciergeserver.CSWebContainer.handle(CSWebContainer.java:46)
   at org.simpleframework.http.socket.service.RouterContainer.handle(RouterContainer.java:106)
   at org.simpleframework.http.core.RequestDispatcher.dispatch(RequestDispatcher.java:121)
   at org.simpleframework.http.core.RequestDispatcher.run(RequestDispatcher.java:103)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: [url]http://192.168.45.91/port_3480/data_request?&id=variableget&Variable=PK_AccessPoint[/url]
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
   at java.net.HttpURLConnection.getResponseCode(Unknown Source)
   at com.rtsservices.veraconnect.access.VeraGateway.URLConnection(VeraGateway.java:115)
   at com.rtsservices.veraconnect.access.VeraGateway.URLRequest(VeraGateway.java:71)
   ... 12 more

FWIW, I had similar issues back in December of 2017,

http://forum.micasaverde.com/index.php/topic,52562.msg336611.html#msg336611

Back then I reloaded the lua onto my Vera after extracting it out of the .jar

I ssh'd into my Vera, cleared out the lua & lzo files, restarted Vera, reloaded the lua file and no luck this time around.

Is the call to http://192.168.3rd.4thOctet/port_3480/data_request?&id=variableget&Variable=PK_AccessPoint
right?

If I throw it in a browser, I get an auth prompt.  But if I edit /port_ out and go to http://192.168.XX.XX:3480/data_request?&id=variableget&Variable=PK_AccessPoint

I get a serial number.  Red Herring I assume?


Any ideas?

Offline zyphaz

  • Newbie
  • *
  • Posts: 9
  • Karma: +1/-0
Re: Cannot auth to Vera - Local server connectivity test fails
« Reply #1 on: November 06, 2018, 04:48:37 pm »
For anyone curious, or if this post comes up on any search hits.  The fix was contacting Vera support mentioning a lack of local anonymous access when accessing the Vera on the LAN.  Specifically if you migrated from a UI5 device to a Vera Plus, then upgraded to UI7, there are local authentication issues that must be fixed from ssh.