Cannot login #3
Comments
|
hmm sounds like a connection establish problem hope to find some time next week for this ( probably Tuesday or Wednesday ) |
neither can i |
Thanks ! If you need additional info, please let me know. |
|
sorry for late response pushed a update today for better error handling b755d73 so you use the same url in settings like for accessing fritzbox via web ? pls try [Fritzbox IP]/login_sid.lua -> it should show you a xml response if you still have problems pls provide some informations about your setup ( fritzbox version, fritzbox local ip, homey local ip, fritzbox type ( model ) ) |
|
No problem on the delay, we're all busy people and have iimited time
available ... I'm glad do you take the time to review and respond.
I'll do some more testing tonight, but want to already confirm I'm using
the same url as when accessing using the browser.
I tried without and with http:// in the url - not sure whether I tried with
https:// - will reconfirm tonight. I did notice regardless of whether I
tick the 'strict ssl' box the app always connects to port 80 (I was
expecting 443 for ssl).
One question:you mention to try the .lua link - should I enter this in the
app settings, or using a browser accessing the firtzbox ?
And where should Isee the xml ? I'm new to Homey apps and have not yet
found a way to see app logs ...
Talk later
…On Thu, May 2, 2019, 12:01 puschie286 ***@***.***> wrote:
sorry for late response
pushed a update today for better error handling b755d73
<b755d73>
but i guess its a different problem.
so you use the same url in settings like for accessing fritzbox via web ?
(i guess you already tested to use http/https infront of your ip)
pls try [Fritzbox IP]/login_sid.lua -> it should show you a xml response
if you still have problems pls provide some informations about your setup
( fritzbox version, fritzbox local ip, homey local ip, fritzbox type (
model ) )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEHF5W7G22HOFQJDVG255DPTK3Y5ANCNFSM4HGTGUDQ>
.
|
|
hmm, i can check the port for https -> should be handled by the npm package 'request' but i will check the [...]login_sid.lua address is for the browser -> your browser should show a xml file |
|
When I access the mentioned URL in the browser - before login, I get the
following response:
<SessionInfo><SID>0000000000000000</SID><Challenge>485e81f6</Challenge><BlockTime>0</BlockTime><Rights/></SessionInfo>
After logging in, it changes to:
<SessionInfo><SID>0000000000000000</SID><Challenge>080edd99</Challenge><BlockTime>0</BlockTime><Rights/></SessionInfo>
Honestly speaking, I'm not clear how this helps but wanted to share anyway
...
I'll have a look at changing HTTPS in the URL to see how that effects the
result.
…On Thu, May 2, 2019 at 2:03 PM puschie286 ***@***.***> wrote:
hmm, i can check the port for https -> should be handled by the npm
package 'request' but i will check
the [...]login_sid.lua address is for the browser -> your browser should
show a xml file
note: there is an issue with something similar that was caused by wrong
DNS setup -> Link <andig/fritzapi#11>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEHF5TG6RVLNP6GBKOCFYDPTLJ7JANCNFSM4HGTGUDQ>
.
|
|
When I use HTTPS in the URL, the destination port changes to 443 as
expected.
Even when I de-select the "strict SSL" tickbox in the settings, traffic is
pointing to port 443.
I'm not sure how the tickbox effect the traffic - but at least by changing
the URL the port can be controlled.
Unfortunately, neither case results in a proper login :(
Regarding your note on DNS: I'm using IP address in the app settings, so I
don't think DNS would make an impact.
I'll read-up on the link nonetheless and let you know.
On Thu, May 2, 2019 at 8:18 PM Marco van Laerhoven <mvl1729@gmail.com>
wrote:
… When I access the mentioned URL in the browser - before login, I get the
following response:
<SessionInfo><SID>0000000000000000</SID><Challenge>485e81f6</Challenge><BlockTime>0</BlockTime><Rights/></SessionInfo>
After logging in, it changes to:
<SessionInfo><SID>0000000000000000</SID><Challenge>080edd99</Challenge><BlockTime>0</BlockTime><Rights/></SessionInfo>
Honestly speaking, I'm not clear how this helps but wanted to share anyway
...
I'll have a look at changing HTTPS in the URL to see how that effects the
result.
On Thu, May 2, 2019 at 2:03 PM puschie286 ***@***.***>
wrote:
> hmm, i can check the port for https -> should be handled by the npm
> package 'request' but i will check
>
> the [...]login_sid.lua address is for the browser -> your browser should
> show a xml file
> note: there is an issue with something similar that was caused by wrong
> DNS setup -> Link <andig/fritzapi#11>
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#3 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AKEHF5TG6RVLNP6GBKOCFYDPTLJ7JANCNFSM4HGTGUDQ>
> .
>
|
|
Looks good... |
|
I've confirmed traffic from Homey is reaching the Fritzbox, by looking at
the firewall logs.
Also on the FritzBox, I see the connection attempt in the event Log - it is
reported there as an incorrect password.
See screenshot below. Note the Homey address is 192.168.30.27.
[image: image.png]
I obviously confirmed the password is correct - it is just one character,
can't go wrong there.
If you still think this is pointing to a network issue, can you please
clarify ?
…On Thu, May 2, 2019 at 8:35 PM puschie286 ***@***.***> wrote:
Looks good...
It’s pretty sound like a network problem - I guess the fritzbox ip is
different in your homey subnet
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEHF5RJNAUXCOW6O4OQ7NTPTMX6JANCNFSM4HGTGUDQ>
.
|
|
Sry can’t see the img ( only Text no link ) |
|
Ow, sorry - Ill attach it as a file, rather than in place ...
[image: Capture.JPG]
…On Thu, May 2, 2019 at 8:59 PM puschie286 ***@***.***> wrote:
Sry can’t see the img ( only Text no link )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEHF5WBSPLDTFIKP3CCJZTPTM22VANCNFSM4HGTGUDQ>
.
|
|
Unfortunately not |
|
Hmm, sorry about that
…On Thu, May 2, 2019 at 9:03 PM puschie286 ***@***.***> wrote:
Unfortunately not
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEHF5X4SERNLEKYR7V3LS3PTM3JBANCNFSM4HGTGUDQ>
.
|
|
can you upload the image somewhere ( or use the browser ) ? currently i have no idea why the fritzbox reject the password/challenge and maybe it will help to have the error message, could you post your homey/SimpleLOG log entries when trying to login ? |
|
Hi Puschie,
Sorry, I was out of the country for a couple of days and too busy to follow
up on this.
Tried again today, after I noticed an app update was installed earlier this
week.
Problem still occurs; please refer to file attached.
I have now logged in to the fritzbox with the same account (Homey) on the
web browser, since you mentioned I would be logged out automatically.
That does not occur to me, the browser session is still active whereas you
can see the failed attempt from the Homey device (on 192.168.30.27).
I hope you are able to see this attached file, I've uploaded it instead of
dragging it into the browser.
If not, can you give me an alternative mail address or do you have a way
for me to upload it on github ?
I noticed you mentioned in the change log of this version you've added some
logging.
Is there a way for me to access the logs, and send you some screenshots?
…On Thu, May 2, 2019 at 11:52 PM puschie286 ***@***.***> wrote:
can you upload the image somewhere ( or use the browser ) ?
currently i have no idea why the fritzbox reject the password/challenge
-> do you have other devices/services that access the fritzbox. trying to
login with wrong credentials will cause all active sessions to be destroyed
( found that in the documentation^^ )
and maybe it will help to have the error message, could you post your
homey/SimpleLOG log entries when trying to login ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKEHF5U3SXRKUYOJXTBIBRTPTNPB7ANCNFSM4HGTGUDQ>
.
|
|
Hey, np. |
|
I was replying by email, it seems this removes the attachement (sorry, I never checked this thread on github after creating the initial ticket).
|
|
hmm double checked the password hashing function but everything looks good there ( tested for special keys like € @ ä ö ). |
|
My password currently does not use special characters, so that's not it. The error reported is reloaded to "zero depth sigl signed cert" it seems. |
|
nice thx :) |
|
When I try without https, there is no log entry anymore I've even restarted the the app to confirm, as you can see in the log: |
|
that's bad, sounds like a timeout will happen soon ( 20s - 120s ). im almost out of idea's how to face this problem :( your homey ip is 192.168.30.27 and it tries to connect to 192.168.5.76 |
|
Correct, Homey is in the IoT network segment which has no access to internal networks except for some specific devices. I've included a firewall rule to allow Homey to Fritzbox and vice versa - network traffic logging shows there is a flow both ways.
Yes, I know it is reachable: I can see the login attempt on the FritzBox - and in return it reports "invalid password". Both ip addresses are correct, I also see the firewall is logging traffic going from Homey to the Fritzbox. NOTE: I only use the fritzbox for smart devices now - replaced my router and access points a while ago. NOTE: I cannot change the fritz ip to 192.168.,30.1 - as that is the address of the router. |
|
yes pls try it^^ well, the point is: fritzbox-bridge use fritzboxapi -> fritzboxapi is an implementation of the official fritzbox api. ( also checked the implementation and validate with example data from documention) so im not sure how the password can be wrong if you use the correct one and the implementation is correct :/ the last thing i can try is to setup a network with similar configuration and try to reproduce it |
|
Hmm, looking at the code it seems the password is hashed and the hash is sent to validate the password on the box. I'm using a one character password to rule out me making typos, could that be causing issues (is there a minimum length for the MD5 hash?) |
|
Guess not - there is no min length.
One more idea - can you try to use a laptop and configure it for the smart home subnet and try to login to the fritzbox from there ?
…
On May 20, 2019 at 4:40 PM, <mvl64 ***@***.***)> wrote:
Hmm, looking at the code it seems the password is hashed and the hash is sent to validate the password on the box. I'm using a one character password to rule out me making typos, could that be causing issues (is there a minimum length for the MD5 hash?)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (#3?email_source=notifications&email_token=AASRA3FSFNWSJTN2B5RERU3PWKZ4RA5CNFSM4HGTGUD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVZBK6A#issuecomment-494015864), or mute the thread (https://github.com/notifications/unsubscribe-auth/AASRA3AQZ3IMB2AVEVOQEJDPWKZ4RANCNFSM4HGTGUDQ).
|
I have moved the FritzBox into the same network segment as Homey (the IoT network) and it worked right away. Not sure how the API is effected by crossing the router, but apparently it's breaking the login. Thanks a lot for your time and effort. |
|
hehe^^ |
|
Yes, I confirm: now (after moving FritzBox into the IoT segment) I cannot login anymore from my original network segment (main lan). This issue was unrelated to your app - just unexpected Fritz behaviour ! |
I have a problem logging in to the fritzbox, the app keeps reporting "invalid login".
I have ensured I'm using the correct login details (account and password) and even setup a separate account on the Fritzbox for Homey with a more simple password.
I can login to the fritzbox using both accounts using the web browser.
Note: my homey and fritzbox are in separate network segments, maybe that effects this issue.
I did confirm in the firewall traffic is passed on (port 80 from homey to the fritzbox) - I log all the traffic - fritzbox ip-address is specified correctly in the settings (so, I don't use the default http://fritz.box URL).
Enabling SSL in the app's dialog did not seem to make a difference - same error message is reported back.
The text was updated successfully, but these errors were encountered: