Bug #7851
closedHAProxy Frontend bug - pfSense 2.3.2-RELEASE
0%
Description
Hi Support,
I encountered a bug while trying to add an ACL entry on the HAProxy frontend. When I click save the “client timeout” entry I the error on screenshot_1 . The field had values before I clicked on save but disappears soon after I click on it. (screenshot_2)
Kindly assist
Files
Updated by Jim Thompson over 6 years ago
- Assignee set to Jim Pingle
assigned to Pingle for evaluation.
Updated by Jim Thompson over 6 years ago
- Priority changed from Very High to Normal
Updated by Jim Thompson over 6 years ago
- Subject changed from HAProxy Frontend bug - pfsesne 2.3.2-RELEASE to HAProxy Frontend bug - pfSense 2.3.2-RELEASE
Updated by Jim Pingle over 6 years ago
- Status changed from New to Feedback
What exact value did the field have?
I can't reproduce any problem here. If I put in a number and save, it saves the number and it's there when I reload the page. If I open an existing entry with a value and save, it's still there and still saves OK. If I put invalid input, it says it's invalid and it's still in the field so I can correct it.
The only way I can reproduce anything that looks like your situation is if I put spaces in the field and try to save that, which is both invalid and looks empty.
Also, update to 2.3.4-p1 and make sure you are on the most recent version of the package.
Updated by Peter Omolo over 6 years ago
The value I had was/is 1000000
Is there a limit in the number of entries I can add under the "Actions" section of the HAProxy Frontend? (I have numerous entries) It used to be seemless until now. I will also try the upgrade to 2.3.4-p1.
Updated by Jim Pingle over 6 years ago
- Status changed from Feedback to Not a Bug
- Affected Version deleted (
2.3.2) - Affected Architecture added
- Affected Architecture deleted (
amd64)
That value works for me, I can't reproduce this at all. I can create new entries with that or edit existing entries. No errors, and the value is there every time.
For this and other unrelated questions, please post on the forum, reddit, or mailing list for a discussion until a bug can be identified.