Issues with nnrpd and tls

I will tell you the whole procedure I performed.
I want to have port 119 in clear and port 563 with tls.
As soon as I installed inn2 on ubuntu22.04 I had port 119 in clear.
To also have port 563 instead for tls I added the option -S to nnrpdflags in etc/news/inn.conf.
Result both ports 119 and 563 support tls.
So wanting to manage the two processes independently of each other, I remove the option -S from nnrpdflags in etc/news/inn.conf and create an init file for nnrpd with systemd, ExecStart=/usr/lib/news/bin/nnrpd -p 563 -b 0.0.0.0 -S, which however does not work. I see with systemctl status inn-nrrpd that the script failed due to binding on busy port 563 and .... killall nnrpd.
After this command nnrpd is really dead, even adding -S to nnrpdflags again I was not able to start it anymore, not even with a server reboot. It was only with the command sudo -u news /usr/lib/news/bin/nnrpd -S -D -p 563 that nnrpd is "resurrected" and with which it is now active.
I removed the nnrpdflags -S option from etc/news/inn.conf but port 119 is still not exactly clear

$ openssl s_client news.tcpreset.net:119
Connecting to 2a01:4f8:c0c:2f94::1
CONNECTED(00000003)
depth=2 C=US, O=Internet Security Research Group, CN=ISRG Root X1
verify return:1
depth=1 C=US, O=Let's Encrypt, CN=R11
verify return:1
depth=0 CN=news.tcpreset.net
verify return:1
---

Any help appreciated
Best regards

Gabx