-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UPnP Error #185
Comments
I have to guess what happens here, as this error is forwarded from the router. The message also is a bit misleading: the action is known, otherwise a FritzActionError (401) should get raised. So I suppose the user has not the proper rights to execute the (btw. the |
Thank you for your reply. Yes, I know that the ACTION variable was not really the best choice. I have corrected it. I am struggling to find the reason.
Do I need to enable other options in my FritzBox (7.50) such as UPNP or other options for this to work? What is a good service + action to check if a login with the given username and password was successful and which rights or options are missing? Thanks for your help. |
I suppose one (WANIPConn1) is the UPnP- and the other (WANIPConnection1) the TR-064 interface and both seems to support a common subset of settings.
If setting a checkmark to "FRITZ!Box Settings – Users with this right can view and edit all FRITZ!Box settings." does not work, I have also no idea whether there are more hidden settings. The AVM documentation about TR-064 remote access notes that "There are some actions which are not completely supported for the remote access". I don't know whether this is also true for PortMappings and LAN access (may be for security reasons).
For my knowledge there is none. Some actions will just not work. |
Hello, |
Two times the same input but different outputs, depending on whether the request was sent from a Pi 4 or 5 – do I understand this right? This would be odd. The error itself is forwarded from the router. So in one case the router accepts the arguments and in the other case does not. The only idea I have is that there must be subtle differences by the requests. |
i assume both PIs has its own IP address, those -from fritzbox point of view- are different network clients and have their own configuration in the fritzbox. With this it might also be possible, that you have disallowed the "create port openings for its own" for one of the PIs? |
This was the crucial hint! Many thanks. I tested only for ports linked to the Pi5. Now I tested with several ports that are linked to Pi4 and Pi5 and I can maintain via |
Interesting. For me the error message was misleading. Glad that it works for you now. |
Hey. I am struggling with this error. I already read some issues in this repo and some other forums but i cant really figure out how to solve it.
Basically I want an easy on / off switch for port forwarding in my fritzbox.
Thus I did this:
respectivly this to delete it:
But all I get are these errors.. i had 401,402 and 403 so far, but this UPnPError pops up everytime...
What can I do?
Or is there a much easier way to activate / disable port mappings without deleting them everytime?
Thanks.
The text was updated successfully, but these errors were encountered: