Admin user can't access users/groups
-
@NogBadTheBad Hir sir, I already installed the package of system patches and when I click fetch button it says Patch Failed. My box has the current version 2.4.4-RELEASE-p3. Thanks
-
The fetch failed.
So, what are you fetching ?
-
@Gertjan I am trying to fix this issues because I cant add another user. This is the issue from user manager, but when i click the fetch button it says Patch Fetch Failed. This is the thing that i want to patch https://github.com/pfsense/pfsense/commit/cf529cbe33ae53f3f95b37a227da141b97465f20.patch
-
The URL you used is just fine.
When I clicked on "Fetch", it was successful..
On your system, pfSense can't go outside (== loading something from https://github.com/.... ), you should investigate that issue.
-
@Gertjan Thank you very much sir.
-
I have this issue too but I'm not familiar with patching a pfSense. I added the system patch package. However, I need a little guidance on what to do with the link to the patch above and the respective fields.
Thanks in advance for your assistance.
-
I have another symptom but not sure if it is related to this patch.
I created a new user, User1, and added the user to the ADMIN group.
I login with User1 and it appears I can do some administration but when I try to add VLANs or edit new assignments, I end up at the WAN assignment page. However, when I use the admin account, it works as I would expect it to.
I look forward to some guidance on how to apply this patch.
-
@pfsense16v said in Admin user can't access users/groups:
I look forward to some guidance on how to apply this patch.
To apply the patch you need the patch package - and the URL as shown above.
The rest is a 3 click procedure.I guess it's worth applies the patch - at best it solves your issue - at worst you found another issue.
-
@NogBadTheBad
Awesome and worked like a charm!
Thanks, saved me a ton of time and was going round in circles!!! -
Just wanted to say thank you for this!
-
What I'd like to know is this: I'm on 2.4.4-RELEASE-p3 now. Why wasn't/isn't this issue already patched and included in the release I'm on?
-
Because it was only introduced in 2.4.4p3. It will be fixed in the next release.
Steve
