XML syntax errors about netgear_exporter HOT 6 CLOSED

That's very odd... Debug didn't show the full request/response?

I don't know much about the Netgear server side of things, but in my limited experience it has always at least provided valid XML. To see misbalanced tags would make me suspect even the Netgear fat client app would also fail (perhaps worth a try as an added data point?)

from netgear_exporter.

For now, since I cannot replicate this and I'm not sure we'd be able to deal with it, I'll go ahead and close the issue. Maybe more information can come from the --clientdebug parameter to at least identify what's misbalanced, but as mentioned... if Netgear is producing invalid XML, I don't know what the client can do to fix that (short of not parsing it as XML)

from netgear_exporter.

I got the same error.

While sending request to http://10.0.0.1/soap/server_sa/, I got html instead of xml and the response code is 401.

I'm not sure if it is related to custom url, bacause the Host header of request is routerlogin.net rather than 10.0.0.1.

from netgear_exporter.

Thanks, @imrebuild - does the content of the response indicate anything helpful?

from netgear_exporter.

Sorry I made a mistake. Changing port to 5000 solved this issue.

from netgear_exporter.

More context for anyone else dealing with the R7000: Bump the timeout. Although on a local network, the router can take longer than the default 2 seconds to return data. Setting NETGEAR_EXPORTER_TIMEOUT to 10 helped here.

from netgear_exporter.