Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Richmond <dnomhcir@gmx.com>
To: info-gnus-english@gnu.org
Subject: Re: Error message Process nntpd not running
Date: Tue, 20 Jul 2021 12:31:29 +0100	[thread overview]
Message-ID: <47e572e9-7e96-227f-025e-c23fbef873e2@gmx.com> (raw)
In-Reply-To: <m2h7gpjkfk.fsf@codeisgreat.org>

Pankaj Jangid wrote:
> Richmond <dnomhcir@gmx.com> writes:
>
>>> Could you please try removing the other params from your configuration
>>> if the previously mentioned restart also doesn’t fix the issue.
>> This change does fix the issue. However it means not using TLS. I want
>> to use TLS. I was using TLS before the server was upgraded without any
>> problems. And I use other servers with TLS without getting this error.
> Then probably wait for a couple of days. The guys at aioi.org must be in
> the process of restoring the certificates.
>
> If the issue persists then report it to them that TLS isn’t working.

I have already reported it to them. They say there is nothing wrong

their end.

Notice this command works and allows interaction with the server:

gnutls-cli nntp.aioe.org:563



_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2021-07-20 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 10:16 Richmond
2021-07-20 10:57 ` Pankaj Jangid
2021-07-20 11:15   ` Richmond
2021-07-20 11:26     ` Pankaj Jangid
2021-07-20 11:31       ` Richmond [this message]
2021-07-20 12:24         ` Pankaj Jangid
2021-07-20 12:44           ` Richmond
2021-07-20 13:50             ` Pankaj Jangid
2021-07-20 17:35               ` Richmond
2021-07-20 17:55                 ` Richmond
2021-07-20 19:12                   ` Eric Abrahamsen
2021-07-21  3:19                 ` Pankaj Jangid

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=47e572e9-7e96-227f-025e-c23fbef873e2@gmx.com \
    --to=dnomhcir@gmx.com \
    --cc=info-gnus-english@gnu.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;
as well as URLs for NNTP newsgroup(s).