From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.25 - Core Update 156 available for testing
Date: Tue, 20 Apr 2021 09:54:33 +0200 [thread overview]
Message-ID: <34048b2d-55aa-bf04-8586-3c0e210ff1c0@ipfire.org> (raw)
In-Reply-To: <564fb301-b04c-d3f2-3c15-2dd794706890@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3021 bytes --]
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>.
>>
--
Sent from my laptop
next prev parent reply other threads:[~2021-04-20 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <161882580503.27807.11098110518344373131.ipfire@ipfire.org>
2021-04-19 16:48 ` Adolf Belka
2021-04-20 7:54 ` Adolf Belka [this message]
2021-04-20 21:14 ` Core Update 156 (testing) report (was: Re: IPFire 2.25 - Core Update 156 available for testing) Peter Müller
2021-04-21 12:25 ` Adolf Belka
2021-04-21 14:26 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34048b2d-55aa-bf04-8586-3c0e210ff1c0@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox