public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Core 151 Testing feedback
Date: Mon, 12 Oct 2020 13:14:04 +0200	[thread overview]
Message-ID: <8fb10748-21dc-020a-a189-bd6426e263a1@gmail.com> (raw)
In-Reply-To: <7BCB8028-8FF5-4306-9A82-B0BA76530A31@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

Hi Michael,

Both pages come up with a page with an internal server error.
Erik mentioned it for the OpenVPN WUI and Peter mentioned it for both the OpenVPN and IPSec pages. Peter mentioned bug #12491 as tracking the issue.

Regards,
Adolf.

On 12/10/2020 12:14, Michael Tremer wrote:
> 
> 
>> On 11 Oct 2020, at 12:29, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>>
>> Hallo All,
>>
>> Other than the OpenVPN and IPSec page issues mentioned by other people I have not found any other problems.
> 
> Which are those?
> 
>>
>> I can confirm that the bacula update to 9.6.6 works fine in Core 151, with a successful backup carried out.
>>
>>
>> Regards,
>>
>> Adolf
>>
> 

  reply	other threads:[~2020-10-12 11:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 11:29 Adolf Belka
2020-10-12 10:14 ` Michael Tremer
2020-10-12 11:14   ` Adolf Belka [this message]
2020-10-12 13:10     ` Michael Tremer
  -- strict thread matches above, loose matches on Subject: below --
2020-10-09 11:46 Core 151 testing feedback ummeegge
2020-10-09 14:26 ` Michael Tremer
2020-10-09 20:56   ` ummeegge
2020-10-10 11:52     ` Michael Tremer
2020-10-11  5:27       ` ummeegge
2020-10-11  7:52         ` ummeegge
2020-10-11  8:00           ` Matthias Fischer
2020-10-11 11:57             ` ummeegge
2020-10-11 16:29               ` Matthias Fischer
2020-10-09 19:31 ` Peter Müller
2020-10-11 11:18   ` Adolf Belka
2020-10-11 11:58     ` Adolf Belka

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=8fb10748-21dc-020a-a189-bd6426e263a1@gmail.com \
    --to=ahb.ipfire@gmail.com \
    --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