-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Error: control/filtering/set_rules | Failed to read request body #2675
Comments
The same problem exists for the "disallowed clients" list… I think the allowed http body size should not be so low if you are logged in |
Merge in DNS/adguard-home from 2675-larger-requests to master Updates #2675. Squashed commit of the following: commit 2b45c9b Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 13:38:44 2021 +0300 home: imp names commit dad39ae Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 13:31:53 2021 +0300 home: imp large req handling
Should be fixed as of snapshot aebcd74. Can you please check if our solution fixes the issue for you? |
Good morning, Mr. Garipov, Sorry for writing so late, but I confirm the problem was fixed. I updated my AdGuard Home to version v0.105.1 and everything is fully functional again. The list of custom filters can be edited again, no problems so far. Thank You and all the developers so much for the fix and your time. I am sorry I could not help you more. I am beginner in programming, so I tried to report this issue at least. |
Merge in DNS/adguard-home from 2675-larger-requests to master Updates AdguardTeam#2675. Squashed commit of the following: commit 2b45c9b Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 13:38:44 2021 +0300 home: imp names commit dad39ae Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 13:31:53 2021 +0300 home: imp large req handling
Issue Details
Hello everyone,
I have installed AdGuard Home on 21 August 2020 on my router Turris Omnia. I have been using it without any issues whatsoever since then. The filtering or blocking worked (and still works) as expected. So, I created my own set of rules in a tab Filters - Custom filtering rules which worked great until yesterday (12.02.2021). When I tried to add an exception and unblock a domain, I received an error message:
Error: control/filtering/set_rules | Failed to read request body: attempted to read more than 65536 bytes | 400
The error prevents me from editing my Custom filtering rules. I cannot add, remove or change anything. When I click on the Apply button after making some change, it returns an error message described as above. The blocking or allowing a certain domain (from my Custom filtering rules) is, however, still fully functional.
The error message appeared right after the new update (v0.105.0). There was no such error before this update. I realize my file could be quite large (907 KB in .txt) and has approximately more than 41 500 lines, but everything worked before the update. The router does not have full storage, it has more than 3 GB of space remaining. The router itself is not overloaded and does not report any issues. I edit the list only via Copy and Paste from a plain .txt file stored in my computer using web interface of AdGuard Home from web browser. Rebooting does not help.
Kernel Version: 4.4.199-a890a5a94ebb621f8f1720c24d12fef1-1
Expected Behavior
I would like to know if this issue could be fixed - So I could edit my custom filters again, if possible.
Actual Behavior
The current error prevents me from editing my Custom filtering rules. I cannot remove a line with a domain or add another one (for both rules - block and unblock). However, the Custom filtering rules are still working - they still allow or block particular domain according to their rules.
Screenshots
Additional Information
Unfortunately, I am not a programmer or an IT specialist so I cannot help you much more, without additional help from you. I would be very grateful if someone would have read this message and will try to help me or fix the issue in the next build. Thank you very much for your time and attention.
The text was updated successfully, but these errors were encountered: