-
-
Notifications
You must be signed in to change notification settings - Fork 310
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
Conflicting iptables rules #88
Labels
Comments
Just fyi, this issue reflects the same behavior found in issue #49 . |
This was
linked to
pull requests
Feb 21, 2020
Closed
wow, i was trying for months to get a connection ! Thank u so much my friend @bmeneguele |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems some startup services may add conflicting rules to the system against Nipe:
A solution I found was to completely flush iptables rules before nipe set its own rules:
One problem with this solution is the possible future conflicts we may have against other apps on the system. I'm don't really know how iptables works, so any help is welcome!
The text was updated successfully, but these errors were encountered: