access denied serverrequest

I noticed errors in my Indigo logs pointing to my Domotics Pad device whenever it displays a control page:
access denied "http://IP-OF-INDIGO:8176/serverrequest" from myuser @ IP-OF-DOMOPAD
Note that the control page works perfectly. All buttons and all status displays work correctly. Am using Indigo 6.,1.11 and Domotics Pad 1.4.1. Did I miss some knob in the setup?

Thanks
-Roland

I noticed errors in my Indigo logs pointing to my Domotics Pad device whenever it displays a control page:
access denied "http://IP-OF-INDIGO:8176/serverrequest" from myuser @ IP-OF-DOMOPAD
Note that the control page works perfectly. All buttons and all status displays work correctly. Am using Indigo 6.,1.11 and Domotics Pad 1.4.1. Did I miss some knob in the setup?

This is the first that I've heard of this from anyone -- but I can't think what would cause it if the control page is working as expected. You can try setting an identifier in the settings under Error Reporting (such as to your username, but really anything that you let me know), then go load the Control Page. Once the error occurs on the server, within Domotics Pad choose the menu and Help then "Send Debug Report". I can see if the error is reflected in the logs that way.

Adam

Thanks Adam for looking into this. I just cleared the image cache and opened the control page. Got this in my server's log (see below - replaced my real user name with MYUSER). I did send you the debug log from the Domotics Pad Help screen.
All the images shown as "access denied" did show correctly on the control page screen and all the interaction with the server works just fine. Weird. Hope something makes sense to you

Nov 7, 2016, 22:08:29
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button Switch+inactive.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Alarm Zone+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button HVAC Auto+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button HVAC Cool+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button HVAC Heat+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Flame Red.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button Garage Door+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button Switch+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/variables/My Button Housemode Night+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/variables/My Button Housemode Away+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button Down Arrow Blue+on.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button Up Arrow Red+on.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/Wunderground-2x+nt_mostlycloudy.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/resolveimagepath" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Flake Bleu.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/variables/My Button Housemode Vacation+.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/variables/My Button Housemode Home+home.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Alarm Zone+true.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/images/controls/devices/My Button HVAC Off+on.png" from MYUSER @ 192.168.0.132
WebServer access denied "http://192.168.0.118:8176/serverrequest" from MYUSER @ 192.168.0.132

Thanks... I don't see anything in the Domotics Pad debug report that you sent that shows any recognition of the error and your indigo log makes me think every request to the server gets an access denied before completing; together this makes me think that it is automatically being handled by the (Android) system. Though it appears to be working, I suspect the extra authentication request is making it a tad bit slower (even if you don't realize it).

Two follow up questions based on the log:
What authentication method are you using - basic or digest?
Do you see a similar issue when browsing Devices (i.e. not on the control page view)?

I get an "access denied "http://192.168.0.118:8176/serverrequest"" error about once a second also when I am on the Device screen without me performing any action.
How do I check the authentication method? I don't see anything related in Settings->Advanced Settings.
I only have Username/Password/Server/HostName/HomePort/Home User HTTPS (which is off).

I get an "access denied "http://192.168.0.118:8176/serverrequest"" error about once a second also when I am on the Device screen without me performing any action.

What that indicates to me is that every request going to the Indigo server is being attempted without the proper authentication method (either with no password or a different scheme, then since it fails Android is automatically re-trying with a second (this time matching) scheme and it goes through. That authentication should be cached and reused, so something is going wrong for sure.

Update before I even hit Submit... I was just able to duplicate this issue using my older client which for some reason had not yet auto-updated. Looks like this is a bug (or "feature" ) in the interaction between the latest Google libraries and Android v4.x or another library. I'll see what I can do to work around that now that I can duplicate it.

Adam

Any update? I'm experiencing an identical problem

Any update? I'm experiencing an identical problem

It was an error in an open source library... I have corrected it and it is published for those on the beta program. Unless I hear of any issues it will be released tonight or tomorrow.