Hi,

Occasionally (December 14 2023, and February 12 2024) I have found that
prayer has stopped working (fixed by a restart), and I find in the
paniclog entries like:

Dec 14 03:03:18 [20888] No HTTP or HTTPS ports active
Feb 12 03:03:17 [529] No HTTP or HTTPS ports active

(note a very similar timestamp)

I suspect this relates to a restart run by cron when the underlying TLS
certificate has changed? But the configuration file does have specified
ports, and it's not that there's a problem reading the TLS key/cert (as
that produces more useful errors in the log).

Regards,

Matthew

Dear submitter,

as the package prayer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1063872

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)