Open pablorodz opened 3 years ago
I've also run into this same issue. Seems the people behind this may have given up working on it. So I'm going to dig a little further & see if I can figure it out. I can only guess that as the equipment this code is built for is owned by the ISP that they may have added something within the firmware to block external scripts/code from communication.
I'll add info as/when I can figure it out.
Just seeing if either of you got anywhere with this please?
I haven't tried anything, sorry.
Same Error. If someone with any sort of networking experience can help debug this, would be greatly appreciated.
FWIW, I'm seeing the same error printed out after each command but the commands themselves actually seem to work 🤔. I was able to update my port forwarding rules successfully.
Looking a bit more closely at the traceback, the error occurs when attempting to log out as part of exiting the Hub
context manager. As far as I can tell, what happens is:
Hub
tries to log out and gets a 500 response from the router.Hub
instance. Clearing the credentials occurs in a finally
block and so always runs.It seems to me, since attempting to log out induces a 500 response from the router, that there might be a problem at the router's end?
For now, I'm happy to ignore the errors as it doesn't appear to be causing a problem 🤷 .
I'm getting the following warning and error:
The only difference I see from Supported Routers is the firmware version.
Steps to reproduce
Result