From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire Blog Error 500
Date: Tue, 18 Oct 2022 10:51:25 +0100 [thread overview]
Message-ID: <8C2FB926-E526-466E-8AC7-D5EC5BDE28B1@ipfire.org> (raw)
In-Reply-To: <16d9c55f-3701-6700-14e7-aa3c4b58843a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Thank you for making me aware.
I rebooted the web server and we are back again…
> On 18 Oct 2022, at 08:49, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael and Peter,
>
> FYI, in case you haven't noticed it yet, the IPFire Blog site is giving an
>
>
> Error 500
> oops, something went wrong
>
> message.
>
> Regards,
> Adolf.
>
> --
> Sent from my laptop
>
prev parent reply other threads:[~2022-10-18 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 7:49 Adolf Belka
2022-10-18 9:51 ` Michael Tremer [this message]
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=8C2FB926-E526-466E-8AC7-D5EC5BDE28B1@ipfire.org \
--to=michael.tremer@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