Cant chage ssh port whatever I do

Webmin
21

I use ufw on all boxes.
Can this post be relevant even if it say its from 22.10

22

You should just check? How are we to know whether your system is using socket-based activation for this service or not?

23

old

changed

OK. 5504 seems allowed.
Note it changes from ssh (as listed in /etc/services) to 5504

It looks like it makes it right to the box on that port, so, don’t know.

root@main:~# traceroute  -p 5504 xxxx.18.255.34
traceroute to xxx.18.255.34 (xxx.18.255.34), 30 hops max, 60 byte packets
 1  10.255.255.253 (10.255.255.253)  0.823 ms * *
 2  lo-0.gw-distdh-a.slr.lxa.us.oneandone.net (14.208.1.50)  0.648 ms  0.611 ms  0.581 ms
 3  ae-1.bb-b.ud.mkc.us.net.ionos.com (14.208.1.97)  2.595 ms  2.566 ms  2.532 ms
 4  ae57.edge3.chicago10.level3.net (4.1.48.241)  12.453 ms  12.409 ms  12.323 ms
 5  ae2.3207.edge6.dus1.neo.colt.net (171.75.9.223)  118.521 ms  118.406 ms  118.362 ms
 6  GIGA-HOSTIN.ear2.Dusseldorf1.Level3.net (62.67.20.82)  111.599 ms  111.616 ms GIGA-HOSTIN.edge6.Dusseldorf1.Level3.net (62.67.22.194)  111.969 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  *xxxcharken.org (xxx.18.255.34)  112.048 ms  112.508 ms
24

Anyway I have decided to reinstall the box to see

Thanks anyway

25

You might try two installs. One without changing to UFW. If that works, then reinstall and change.

26

You reinstalled your OS to (maybe) avoid reading a few lines of documentation about systemd socket-activation? That seems extreme.