Netgear integration on Nighthawk RAX29 gives a connection/login error.

IncognitoTGT commented 11 months ago

The problem

When I try to use the Netgear integration with my router in Home Assistant, it gives the error Connection or login error: please check your configuration. In the logs, it shows 2023-11-24 21:05:17.903 ERROR (SyncWorker_4) [pynetgear.router] login using all known port-ssl combinations failed. I went into the container and pinged the router ip so that isn't a problem.

What version of Home Assistant Core has the issue?

core-2023.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Netgear

Link to integration documentation on our website

https://www.home-assistant.io/integrations/netgear

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-11-24 21:05:17.903 ERROR (SyncWorker_4) [pynetgear.router] login using all known port-ssl combinations failed.

Additional information

No response

home-assistant[bot] commented 11 months ago

Hey there @hacf-fr, @quentame, @starkillerog, mind taking a look at this issue as it has been labeled with an integration (netgear) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `netgear` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign netgear` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

netgear documentation netgear source _{^{(message by IssueLinks)}}

dugancom commented 11 months ago

Having the same issue on my Orbi SXR80 and it seems to be that the self signed SSL cert on the router pages is being rejected.

https://community.netgear.com/t5/Orbi-Pro-WiFi-for-Small-Business/SSL-error/m-p/2347112

IncognitoTGT commented 11 months ago

Is there any to fix it?

dugancom commented 11 months ago

Not sure, I'm not the developer, or a developer for that matter. Still not sure this is the issue but this is the error I get when I connect to the router from my HA instance:

60D0E5BA7F000000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889:

If you poke around that link it suggests some fixes for Chrome, or the cert itself, neither of which apply. Again assuming this is the issue.

I'm going to poke around the code today and see if I can force it to connect without SSL. Maybe I can plug port 80 somewhere.

dugancom commented 11 months ago

Can you connect to your router admin page in chrome?

IncognitoTGT commented 11 months ago

So yes, I can connect in any browser. I actually tried adding http:// to the beginning of the URL when trying to set it up but it still gave the same error.

dugancom commented 11 months ago

Hmm, can you run this from your HA instance and see what it gives you?

wget http://[YOUR ROUTER IP]

IncognitoTGT commented 11 months ago

I did it with curl since wget would download a file. I also passed my login to the router to curl and I get the HTML page that says it doesn't support JS.

IncognitoTGT commented 11 months ago

According to #93263 it seems like someone got it working on a similar model, which is odd.

dugancom commented 11 months ago

I'm not sure what the problem was in #93263, seems like it might have been the routerlogin.net domain not resolving via the UI.

Did curl hive you an SSL error too? You might need -v for verbose. When I did I got the self signed cert error:

TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (OUT), TLS alert, unknown CA (560):
SSL certificate problem: self-signed certificate
Closing connection curl: (60) SSL certificate problem: self-signed certificate

IncognitoTGT commented 11 months ago

I did http:// instead of https.

On Nov 26, 2023, at 12:19, Nosrep @.***> wrote:

I'm not sure what the problem was in #93263 https://github.com/home-assistant/core/issues/93263, seems like it might have been the routerligin.net domain not resolving via the UI.

Did curl hive you an SSL error too? You might need -v for verbose. When I did I got the self signed cert error:

TLSv1.3 (IN), TLS handshake, Server hello (2): TLSv1.2 (IN), TLS handshake, Certificate (11): TLSv1.2 (OUT), TLS alert, unknown CA (560): SSL certificate problem: self-signed certificate Closing connection curl: (60) SSL certificate problem: self-signed certificate — Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104481#issuecomment-1826839996, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARGEUVSVA3WVIEMWHMPPBMLYGN23XAVCNFSM6AAAAAA7ZYA77SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWHAZTSOJZGY. You are receiving this because you authored the thread.

dugancom commented 11 months ago

Ok, if you are getting an SSL error then we may have different issues. Mine is looking more like the self certified issue so I'm going to split that off to another issue.

starkillerOG commented 11 months ago

@IncognitoTGT what did you fill in in the host field during setup? I will look into the SSL errors, but that may take some time before getting that fixed. I want to switch from requests to aiohttp but that is a massive change so I need quite some time to work on that....

IncognitoTGT commented 11 months ago

“10.53.19.1"

On Nov 29, 2023, at 02:56, starkillerOG @.***> wrote:

@IncognitoTGT https://github.com/IncognitoTGT what did you fill in in the host field during setup? I will look into the SSL errors, but that may take some time before getting that fixed. I want to switch from requests to aiohttp but that is a massive change so I need quite some time to work on that....

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104481#issuecomment-1831389310, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARGEUVU7W2NZZBNXBRB4MT3YG3TDHAVCNFSM6AAAAAA7ZYA77SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZRGM4DSMZRGA. You are receiving this because you were mentioned.

starkillerOG commented 11 months ago

@IncognitoTGT is that the local IP of your router, seems weird.... I would expect something like "192.168.1.1" or "192.168.1.0" or at least something starting with "192"....

IncognitoTGT commented 11 months ago

Yes lol.

On Nov 29, 2023, at 07:00, starkillerOG @.***> wrote:

@IncognitoTGT https://github.com/IncognitoTGT is that the local IP of your router, seems weird.... I would expect something like "192.168.1.1" or "192.168.1.0" or at least something starting with "192"....

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104481#issuecomment-1831760933, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARGEUVSPCKZZL2UP26UJ6N3YG4PU7AVCNFSM6AAAAAA7ZYA77SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZRG43DAOJTGM. You are receiving this because you were mentioned.

dugancom commented 11 months ago

In my case I tried 192.168.180.123, http://192.168.180.123 and https://192.168.180.123. Same with routerlogin.net.

IncognitoTGT commented 10 months ago

Update?

dcw329 commented 9 months ago

i am also having this issue. but i am using 10.0.0.1 , admin, password, and i know they are correct. and ive docker exec into home-assistant and checked the ping is functional network traffic. unless this is forcing over to ssl and rejecting due to self-sign, i cant imagine why this wouldnt work. and my router has https forced turned off. so 1+ for problem with integration as far as i can tell

R6700v3
Firmware Version V1.0.4.128_10.0.104

dcw329 commented 9 months ago

@hacf-fr @Quentame @starkillerOG . im happy to help troubleshoot if you give me anything additional to run/test/look for

Ascendor commented 9 months ago

@IncognitoTGT is that the local IP of your router, seems weird.... I would expect something like "192.168.1.1" or "192.168.1.0" or at least something starting with "192"....

@starkillerOG: 10. is a perfectly fine address range for local area network (while not everything "starting with 192" is). See https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses

That said: I have the same issues with a netgear GC110 with an IP address from the 192.168. range.

IncognitoTGT commented 9 months ago

This issue's finally active after 1.5 months

issue-triage-workflows[bot] commented 6 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core