Page 2 of 2

Re: Web server basic authentication

Posted: Wed Dec 31, 2014 7:06 pm
by lnevo
Block Party...damn floridian..its 27 degrees in NY!! Happy New Year's everyone!!!

Re: Web server basic authentication

Posted: Wed Dec 31, 2014 7:09 pm
by Sacohen
Yeah, my neighbors are Greek and cooking a goat on a spit.

Re: Web server basic authentication

Posted: Thu Jan 01, 2015 7:56 am
by lnevo
Nice!!!

Re: Web server basic authentication

Posted: Thu Jan 01, 2015 3:25 pm
by Sacohen
Yeah, my wife and son said the goat was excellent. I was not feeling adventurous and didn't try it.

I loaded the new dev code and it is connection to the portal fine now and staying connected, before I believe it would connect after the initial loading of the code and then a bit later it would not and give me an unavailable address message.

What do I need to have Russ at reeftronics do to see if it works there?

Re: Web server basic authentication

Posted: Thu Jan 01, 2015 3:29 pm
by rimai
I'm pretty sure he is pulling data from /r99.
We need to tell them to change it to /sa.

Re: Web server basic authentication

Posted: Thu Jan 01, 2015 4:18 pm
by Sacohen
Ok. I'll ask him to try, but before I do that I want to make sure that the code is working properly and we won't be changing things on him.

I just noticed that since putting the new dev code in that the Android app is giving me errors...

Error 13 Device Authentication Error.
check your username and password settings.

Re: Web server basic authentication

Posted: Thu Jan 01, 2015 5:01 pm
by pandimus
Sacohen wrote:Ok. I'll ask him to try, but before I do that I want to make sure that the code is working properly and we won't be changing things on him.

I just noticed that since putting the new dev code in that the Android app is giving me errors...

Error 13 Device Authentication Error.
check your username and password settings.
I've been getting that error constantly for the last two months.. But yet I hit refresh and my app still uodates

Re: Web server basic authentication

Posted: Fri Jan 02, 2015 1:20 pm
by Sacohen
Russ has enabled the /sa in the Reeftronics website. So if you enable the web authentication on your code it will still send information to Reeftronics.
Done! Well, that was surprisingly easy.

Apparently that /sa URI has been available all along. I was anticipating needing to modify my code to test if /r99 resulted in an authentication failure, then try /sa if needed. But I found that /sa works on all RAs on Reeftronics, so the necessary code change was really quite simple.

Re: Web server basic authentication

Posted: Fri Jan 02, 2015 5:07 pm
by lnevo
So does it query both or is there an option, or you have to resend your info to Russ? There's not much for Settings on the site..

Re: Web server basic authentication

Posted: Fri Jan 02, 2015 5:10 pm
by Sacohen
Not sure. It sounds like it is querying the sa.
Maybe a better question for Russ to answer.

Re: Web server basic authentication

Posted: Fri Jan 02, 2015 5:15 pm
by rimai
/sa has been in our libraries forever...

Re: Web server basic authentication

Posted: Fri Jan 02, 2015 5:38 pm
by lnevo
Cool did not know that.

Re: Web server basic authentication

Posted: Sun Jun 07, 2015 2:10 pm
by AlanM
I'm getting periodic 401 Auth errors from Reeftronics. I know Russ uses /sa to get the data, so it shouldn't be throwing this error. I'm trying to find where in the code it checks for Auth and am not locating it. Can you explain a bit where in RA_Wifi it checks to see if you're authenticated and where it might deliver up the 401 error defined in RA_Wifi.h as SERVER_DENY? I can't find any reference anywhere to that one.

Re: Web server basic authentication

Posted: Sat Nov 21, 2015 5:20 am
by Sacohen
Alan;
Did you get anywhere with this?
I'm not getting 401 errors, but I am getting emails from Reeftronics saying they were unable to connect to my controller a lot more often then when i didn't have the authentication on.

Sent from my SM-G928P using Tapatalk