From: ck@claudiokuenzler.com   
      
   > I just checked and this works fine for me on trixie, so I need more   
   > information about your server configuration.  For example, are you using   
   > ListenAddress, or anything else that might affect how sshd tries to bind   
   > its listen socket?   
   >   
      
   Hey Colin,   
      
   Thanks for checking in on this report.   
      
   It's a standard SSH config, without manual config changes.   
      
   root@debian13:~# grep -i listen /etc/ssh/sshd_config   
   #ListenAddress 0.0.0.0   
   #ListenAddress ::   
      
   root@debian13:~# systemctl reload ssh   
   Job for ssh.service failed because the control process exited with error   
   code.   
   See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for   
   details.   
      
   To give more context: This is a LXC container running Debian 13 on a Debian   
   12 host. Maybe this is an important information needed in this context.   
      
   I just tried to reproduce the same reload error on another LXC container   
   which was upgraded from Debian 12 to 13 (Host running Debian 12) but here I   
   did not get any errors.   
      
   I have to dig deeper into this to find the differences.   
      
   

I just   
   checked and this works fine for me on    
   trixie, so I need more 
   
   information about your server configuration.  For example, are you using 
   
   ListenAddress, or anything else that might affect how sshd tries to bind 
   
   its listen socket?

Hey Colin   
   

Thanks for checking in on this report.   
   /div>

It's a standard SSH config, without manual config   
   changes.

root@debian13:~# grep -i listen /etc/ssh/sshd_config
#ListenAddress   
   0.0.0.0
#ListenAddress ::

root@debian13:~# systemctl reload ssh
Job for   
   ssh.service failed because the control process exited with error code.
See   
   "systemctl status ssh.service" and "journalctl -xeu   
   ssh.service" for details.
<   
   div class="gmail_quote gmail_quote_container">
To give more context:    
   This is a LXC container running Debian 13 on a Debian 12 host. Maybe this is   
   an important information needed in this context.

I just tried to    
   reproduce the same reload error on another LXC container which was upgraded   
   from Debian 12 to 13 (Host running Debian 12) but here I did not get any   
   errors.

I have to dig deeper into this to find the difference   
   .
   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)