Hi All,
I have tested Core Update 156 in my vm testbed.
When I selected Core Update 156 to upgrade, it carried out the upgrade but then when returning to the pakfire WUI page it came up with the following error message:-
Forbidden You don't have permission to access this resource.
Here is the output from the httpd/error_log
[Mon Apr 19 18:40:40.188611 2021] [core:error] [pid 2565:tid 130746513614400] (13)Permission denied: [client 192.168.200.10:37244] AH00035: access to /cgi-bin/speed.cgi denied (filesystem path '/srv/web') because search permissions are missing on a component of the path, referer: https://ipfire.domain:444/ [Mon Apr 19 18:40:56.536729 2021] [core:error] [pid 2565:tid 130746505221696] (13)Permission denied: [client 192.168.200.10:37244] AH00035: access to /cgi-bin/speed.cgi denied (filesystem path '/srv/web') because search permissions are missing on a component of the path, referer: https://ipfire.domain:444/ [Mon Apr 19 18:40:56.539067 2021] [core:error] [pid 2565:tid 130746480043584] (13)Permission denied: [client 192.168.200.10:37248] AH00035: access to /cgi-bin/pakfire.cgi denied (filesystem path '/srv/web') because search permissions are missing on a component of the path
Refreshing IPFire in the browser came back to the home page and Core Update 156 had been installed.
I did a fresh vm clone twice more and each time the same thing happened.
After reboot I checked through the WUI pages.
The Live Graphs worked well.
All WUI pages I accessed all worked as I would expect them too.
No problems found anywhere at this point in time.
Should I raise a bugzilla entry for the install problem I found?
Regards, Adolf.
On 19/04/2021 11:50, IPFire Project wrote:
IPFire Logo
there is a new post from Michael Tremer on the IPFire Blog:
*IPFire 2.25 - Core Update 156 available for testing*
Another update is available for testing: IPFire 2.25 - Core Update 156. As usual for this time of the year, it is a spring clear release that updates lots of software and brings a new exciting feature: Live Graphs.Click Here To Read More https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testing
The IPFire Project Don't like these emails? Unsubscribe https://people.ipfire.org/unsubscribe.
Hi All,
I updated my reference vm build that I clone from, adding some addons and having most services except IPSec VPN running. Then I cloned from this updated Core 155 version and ran the update to 156 and this time there was no screen with Forbidden. It just went back to the normal Pakfire screen.
So it looks like the problem I had below was related to something about the setup of my reference vm that I clone from.
Regards,
Adolf.
On 19/04/2021 18:48, Adolf Belka wrote:
Hi All,
I have tested Core Update 156 in my vm testbed.
When I selected Core Update 156 to upgrade, it carried out the upgrade but then when returning to the pakfire WUI page it came up with the following error message:-
Forbidden You don't have permission to access this resource.
Here is the output from the httpd/error_log
[Mon Apr 19 18:40:40.188611 2021] [core:error] [pid 2565:tid 130746513614400] (13)Permission denied: [client 192.168.200.10:37244] AH00035: access to /cgi-bin/speed.cgi denied (filesystem path '/srv/web') because search permissions are missing on a component of the path, referer: https://ipfire.domain:444/ [Mon Apr 19 18:40:56.536729 2021] [core:error] [pid 2565:tid 130746505221696] (13)Permission denied: [client 192.168.200.10:37244] AH00035: access to /cgi-bin/speed.cgi denied (filesystem path '/srv/web') because search permissions are missing on a component of the path, referer: https://ipfire.domain:444/ [Mon Apr 19 18:40:56.539067 2021] [core:error] [pid 2565:tid 130746480043584] (13)Permission denied: [client 192.168.200.10:37248] AH00035: access to /cgi-bin/pakfire.cgi denied (filesystem path '/srv/web') because search permissions are missing on a component of the path
Refreshing IPFire in the browser came back to the home page and Core Update 156 had been installed.
I did a fresh vm clone twice more and each time the same thing happened.
After reboot I checked through the WUI pages.
The Live Graphs worked well.
All WUI pages I accessed all worked as I would expect them too.
No problems found anywhere at this point in time.
Should I raise a bugzilla entry for the install problem I found?
Regards, Adolf.
On 19/04/2021 11:50, IPFire Project wrote:
IPFire Logo
there is a new post from Michael Tremer on the IPFire Blog:
*IPFire 2.25 - Core Update 156 available for testing*
Another update is available for testing: IPFire 2.25 - Core Update 156. As usual for this time of the year, it is a spring clear release that updates lots of software and brings a new exciting feature: Live Graphs.
Click Here To Read More https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testing
The IPFire Project Don't like these emails? Unsubscribe https://people.ipfire.org/unsubscribe.
Hello development folks,
Core Update 156 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testi...) is running here for about 24 hours by now, with no issues known so far.
Tested IPFire functionalities in detail: - IPsec (N2N connections only) - Squid (authentication enabled, using an upstream proxy) - OpenVPN (RW connections only) - IPS/Suricata (with Emerging Threats community ruleset enabled) - Guardian - Quality of Service - DNS (using DNS over TLS) - Dynamic DNS - Tor (relay mode)
Looking forward to this Core Update.
Thanks, and best regards, Peter Müller
Hi All,
It has been found that if IPFire has the wio addon installed and has one of the themes darkdos, ipfire-legacy or maniac selected in Core Update 155 and then the upgrade to Core Update 156 is carried out, that after reboot when you select Status - Who is Online? that you get an Internal server error message screen.
It was flagged up in the forum by someone with ipfire-legacy. I have confirmed that it occurs with darkdos and maniac as well.
ipfire and ipfire-rounded are confirmed to not show the problem.
From the error log it looks like wio is trying to access a directory that no longer exists after the upgrade. The error log is in the bug report.
This has been raised as bug#12612.
Regards,
Adolf.
On 20/04/2021 23:14, Peter Müller wrote:
Hello development folks,
Core Update 156 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testi...) is running here for about 24 hours by now, with no issues known so far.
Tested IPFire functionalities in detail:
- IPsec (N2N connections only)
- Squid (authentication enabled, using an upstream proxy)
- OpenVPN (RW connections only)
- IPS/Suricata (with Emerging Threats community ruleset enabled)
- Guardian
- Quality of Service
- DNS (using DNS over TLS)
- Dynamic DNS
- Tor (relay mode)
Looking forward to this Core Update.
Thanks, and best regards, Peter Müller
Hello,
I have assigned this ticket to Stephan. He didn’t respond to my last emails where I asked him to fix a couple of things about the updated “ifconfig” command. So I am not sure if he will fix it in time.
So far the update seems to not cause any trouble and we could look at a release as early as next week.
Best, -Michael
On 21 Apr 2021, at 13:25, Adolf Belka adolf.belka@ipfire.org wrote:
Hi All,
It has been found that if IPFire has the wio addon installed and has one of the themes darkdos, ipfire-legacy or maniac selected in Core Update 155 and then the upgrade to Core Update 156 is carried out, that after reboot when you select Status - Who is Online? that you get an Internal server error message screen.
It was flagged up in the forum by someone with ipfire-legacy. I have confirmed that it occurs with darkdos and maniac as well.
ipfire and ipfire-rounded are confirmed to not show the problem.
From the error log it looks like wio is trying to access a directory that no longer exists after the upgrade. The error log is in the bug report.
This has been raised as bug#12612.
Regards,
Adolf.
On 20/04/2021 23:14, Peter Müller wrote:
Hello development folks,
Core Update 156 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testi...) is running here for about 24 hours by now, with no issues known so far.
Tested IPFire functionalities in detail:
- IPsec (N2N connections only)
- Squid (authentication enabled, using an upstream proxy)
- OpenVPN (RW connections only)
- IPS/Suricata (with Emerging Threats community ruleset enabled)
- Guardian
- Quality of Service
- DNS (using DNS over TLS)
- Dynamic DNS
- Tor (relay mode)
Looking forward to this Core Update.
Thanks, and best regards, Peter Müller
-
Adolf Belka -
Michael Tremer -
Peter Müller