Bug 12917 - CU170 Testing - When enabling ipblocklist WUI page a blank screen is shown.
Summary: CU170 Testing - When enabling ipblocklist WUI page a blank screen is shown.
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: Will affect most users Minor Usability
Assignee: Peter Müller
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-19 10:04 UTC by Adolf Belka
Modified: 2022-09-16 09:22 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adolf Belka 2022-08-19 10:04:34 UTC 
Selecting enabled for the ipblocklist page and/or selecting a blocklist, eg DShield, then pressing save results in a blank page which stays there.

Re-selecting the IPFire WUI and going to the ipblocklist page shows that it is not enabled and no blocklists selected.

This problem only happens with the update from CU169 to CU170 Testing master/ef7d41ef

When I downloaded master/ef7d41ef as an iso and did a fresh install then enabling the ipblocklist page and selecting an ipblocklist and pressing save resulted in a page that had the message to go and update the Firewall Rules. I did that and then went back to the ipblocklist page and it is enabled with the previously selected blocklist enabled.

It looks like the problem only occurs when doing an update and not a fresh install.

I have kept the fresh install and the updated versions of the vm's so can do any checking etc that might be required.
Comment 1 Adolf Belka 2022-08-19 10:51:47 UTC 
Should have mentioned in the initial bug submission that this was identified by other people and flagged up in the forum.

https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
Comment 2 siosios 2022-08-19 17:35:10 UTC 
change the owner and group to nobody on /var/ipfire/ipblocklist folder so it can write the settings file.

chown nobody:nobody /var/ipfire/ipblocklist

verified as working afterwards by others
Comment 3 Adolf Belka 2022-08-19 18:00:15 UTC 
Moved back to assigned as it is only marked as modified once a patch has been accepted and merged/committed into the git repository.
Comment 4 siosios 2022-08-19 18:07:05 UTC 
(In reply to Adolf Belka from comment #3)
> Moved back to assigned as it is only marked as modified once a patch has
> been accepted and merged/committed into the git repository.

got it, sorry!
Comment 5 Charles Brown 2022-08-20 22:47:48 UTC 

I gather from the discussion that something like the following needs to be done as part of the Core 170 upgrade process: 
.
"chown nobody:nobody /var/ipfire/ipblocklist/"
.
However, this bug is showing as "assigned" but it is currently assigned only to "nobody"
Comment 10 Adolf Belka 2022-09-15 21:42:22 UTC 
Tested on my vm testbed - cloned a CU169 system, upgraded to CU170 and rebooted and the ipblocklists entry is fully accessible as expected.

Confirm that the fix has fixed the bug.