Outage of some of our services



we just want to inform you about the outage of some of our services. One of our physical server probably went to a silicon heaven. I will report some more details in the morning CEST: Whether we will be able to restore the server functionality or we will move affected services to another one.

Affected services are:

  • Turris:Sentinel data collection
    • Collected data is safe, but no new data is received
  • Foris e-mail notifications
    • “SMTP provider Turris” will not generate an account so newly configured notifications will not be delivered by Turris e-mail server
    • Already configured notifications is not affected
  • Cloud backups
    • Uploaded backups are safe but the service is not available
  • gov.turris.cz website


Unreachable: https://repo.turris.cz/omnia/lists/base.lua:

The server was raised from the dead and services are coming back to normal


still having problems delivering mail to @turris.cz here, for example, this bounced today:

<support@turris.cz>: host mail.nic.cz[] said: 550 5.1.1
    <support@turris.cz>: Recipient address rejected: User unknown in virtual
    mailbox table (in reply to RCPT TO command)

Here’s the entire bounce message:

Return-Path: <>
X-Original-To: anarcat@orangeseeds.org
Delivered-To: anarcat@orangeseeds.org
Received: by marcos.anarc.at (Postfix)
	id BD4FE10E0A8; Wed, 12 Jun 2019 12:51:07 -0400 (EDT)
Date: Wed, 12 Jun 2019 12:51:07 -0400 (EDT)
From: MAILER-DAEMON@anarc.at (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: anarcat@orangeseeds.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
Content-Transfer-Encoding: 8bit
Message-Id: <20190612165107.BD4FE10E0A8@marcos.anarc.at>

This is a MIME-encapsulated message.

Content-Description: Notification
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

This is the mail system at host marcos.anarc.at.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<support@turris.cz>: host mail.nic.cz[] said: 550 5.1.1
    <support@turris.cz>: Recipient address rejected: User unknown in virtual
    mailbox table (in reply to RCPT TO command)

Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; marcos.anarc.at
X-Postfix-Queue-ID: 5F5B110E07A
X-Postfix-Sender: rfc822; anarcat@orangeseeds.org
Arrival-Date: Wed, 12 Jun 2019 12:51:04 -0400 (EDT)

Final-Recipient: rfc822; support@turris.cz
Original-Recipient: rfc822;support@turris.cz
Action: failed
Status: 5.1.1
Remote-MTA: dns; mail.nic.cz
Diagnostic-Code: smtp; 550 5.1.1 <support@turris.cz>: Recipient address
    rejected: User unknown in virtual mailbox table

Content-Description: Undelivered Message Headers
Content-Type: text/rfc822-headers
Content-Transfer-Encoding: 8bit

Return-Path: <anarcat@orangeseeds.org>
Received: by marcos.anarc.at (Postfix, from userid 1000)
	id 5F5B110E07A; Wed, 12 Jun 2019 12:51:04 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orangeseeds.org;
	s=marcos; t=1560358264;
Received: by curie.anarc.at (Postfix, from userid 1000)
	id EBE86120077; Wed, 12 Jun 2019 12:51:03 -0400 (EDT)
From: =?utf-8?Q?Antoine_Beaupr=C3=A9?= <anarcat@orangeseeds.org>
To: support@turris.cz
Subject: wifi card not detected in mox
Date: Wed, 12 Jun 2019 12:51:03 -0400
Message-ID: <87pnniycg8.fsf@curie.anarc.at>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="



Thanks for reporting as I said on IRC, where you told me where did you find it. We will fix it.
//EDIT: Fixed.

We have these two addresses where you can reach us:

  • info@turris.cz
  • tech.support@turris.cz

BTW: The email server is not on the server which Vojta mentioned.

Unreachable: https://repo.turris.cz/omnia/lists/base.lua
closed #5

This topic was automatically closed after 32 hours. New replies are no longer allowed.

opened #6


Cloud backups had issues until now (14.6. 10:00 CEST). It should be alright now.