From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Error 500 @ https://blog.ipfire.org/
Date: Sun, 16 Apr 2023 12:03:36 +0100 [thread overview]
Message-ID: <C54DC5CE-C982-4243-9E78-8869A554EAE7@ipfire.org> (raw)
In-Reply-To: <800e11d3-d65f-43b0-a3e7-099451fc4afa@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Thank you. I restarted the service and the blog is back.
> On 16 Apr 2023, at 12:02, Charles Brown <cab_77573(a)yahoo.com> wrote:
>
> https://blog.ipfire.org/
>
> returns ...
>
> *IPFire* Blog <https://blog.ipfire.org/>
>
>
> Error 500
>
>
> oops, something went wrong
>
prev parent reply other threads:[~2023-04-16 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <800e11d3-d65f-43b0-a3e7-099451fc4afa.ref@yahoo.com>
2023-04-16 11:02 ` Charles Brown
2023-04-16 11:03 ` 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=C54DC5CE-C982-4243-9E78-8869A554EAE7@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