Template Debian 12 und SSH Port ändern?

H

hackmann

Renowned Member
Proxmox Subscriber
Jan 6, 2013
226
13
83
Guten morgen,
ich habe ein CT Debian 12 installiert und eine Vm mit Debian 12. Bei der Template Version CT kann der SSH Port "sshd_config" zwar geändert werden, allerdings wird die Änderung nicht übernommen, wobei bei der VM geht das. Hätte da jemand einen ""openssh-server Version 1:9.2p1-2""

danke lieben gruss
 
Hi,

hast du den Service nach der Änderung auch neugestartet mittels systemctl restart ssh? Gibt es im syslog journalctl -b irgendwelche Fehlermeldungen o.ä.?

Ansonsten, kannst du mal bitte genau die Änderung posten, die du in /etc/ssh/sshd_config vorgenommen hast?
 
Guten morgen,
ja, das habe ich alles durchgeführt. Habe das auch schon so seit Jahren am laufen!

Bei der VM und bei dem Template

Code: 
   1  apt update
    2  apt upgrade
    3  apt install vim
    4  update-alternatives --config editor
    5  vi /usr/share/vim/vim90/defaults.vim
    6  vi /etc/ssh/sshd_config
    7  reboot
    8  apt install nmap
    9  dpkg-reconfigure tzdata
  
----------------------------------------------------------
cat /etc/ssh/sshd_config | grep 60022
Port 60022
----------------------------------------------------------
Das Template!

root@experpsy:~# nmap -p 22 192.168.50.58
Starting Nmap 7.93 ( https://nmap.org ) at 2023-07-26 11:47 CEST
Nmap scan report for intern (192.168.50.58)
Host is up (0.000062s latency).

PORT   STATE SERVICE
22/tcp open  ssh

Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds

root@experpsy:~# nmap -p 60022 192.168.50.58
Starting Nmap 7.93 ( https://nmap.org ) at 2023-07-26 11:47 CEST
Nmap scan report for intern (192.168.50.58)
Host is up (0.000053s latency).

PORT      STATE  SERVICE
60022/tcp closed unknown ??? In der sshd_config steht der Port 60022 !

AUSZUG

----------
Port 60022

MaxStartups 3:30:10
#Diese Beschränkung ist äu▒~_erst effektiv, aber etwas kompliziert zu verstehen: Die Werte im Beispiel bedeuten,
#da▒~_ 2 (= 1. Wert minus 1) "unauthenticated" (also im Login-Stadium befindliche) sshd-Verbindungen immer erlaubt sind.
#Ab der 3. (= 1. Wert) Verbindung wird mit einer Wahrscheinlichkeit von 30% (2. Wert) die Verbindung abgelehnt.
#Diese Wahrscheinlichkeit steigt linear an, bis bei 10 (3. Wert) offenen Verbindungen jeder weitere Verbindungsversuch zu 100% abgelehnt wird.
#MaxAuthTries = nach einem versuch (falsches pw) wird die verbindung getrennt.
MaxAuthTries 2

---------------------------------------------------------------------------------------

Müsste eigentlich der Port 60022 sein!

die VM

nmap -p 60022 192.168.50.61
Starting Nmap 7.93 ( https://nmap.org ) at 2023-07-26 11:45 CEST
Nmap scan report for testdebian.zone-intern (192.168.50.61)
Host is up (0.000093s latency).

PORT      STATE SERVICE
60022/tcp open  unknown

Syslog bei dem Template ist leer! und bei der VM habe ich keine syslog?

Code: 
root@testdebian:~# ls /var/log/
alternatives.log  apt  btmp  dpkg.log  faillog  installer  journal  lastlog  private  README  runit  wtmp

ich habe leider keine IDDEE.

Ich setzte seit Jahren die Debian Server immer gleich auf.

danke
 
Hast du eine/die Firewall konfiguriert? Wenn ja, evtl. da mal alle Rules checken? Klingt für mich danach gerade ..

Könntest du auch noch bitte die Ausgabe von pveversion -v, pct config <vmid> (für den Container) und qm config <vmid> posten, wobei <vmid> die ID des betreffenden Containers/VM ist?

hackmann said:
Syslog bei dem Template ist leer! und bei der VM habe ich keine syslog?
Click to expand...
Hast du journalctl -b benutzt?
 
Danke

kurz vorweg, es geht jetzt!

openssh-server deinstalliert und neu installiert!

Code: 
root@hauptserver:~# pct config 101
arch: amd64
cores: 1
features: nesting=1
hostname: experpsy
memory: 20000
nameserver: 192.168.50.250
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.50.253,hwaddr=22:29:03:13:AE:                                                                                                                                                             EE,ip=192.168.50.58/24,type=veth
ostype: debian
rootfs: experpsy:subvol-101-disk-0,size=600G
searchdomain: zone-intern
swap: 10000
unprivileged: 1

Code: 
root@hauptserver:~# qm config 300
boot: order=scsi0;ide2;net0
cores: 1
cpu: x86-64-v2-AES
ide2: local:iso/debian-12.0.0-amd64-netinst.iso,media=cdrom,size=738M
memory: 7232
meta: creation-qemu=8.0.2,ctime=1690271101
name: testdebian
net0: virtio=E2:5F:9D:80:C7:23,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-zfs:vm-300-disk-0,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=47dfb332-0d47-4440-9ed4-573d906f0779
sockets: 1
vmgenid: c4b5759a-c6f0-4914-9e83-50d2e98a5a89


Code: 
root@hauptserver:~# pveversion -v
proxmox-ve: 8.0.1 (running kernel: 6.2.16-4-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.3
pve-kernel-6.2.16-4-pve: 6.2.16-5
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.6
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.4
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.1-1
proxmox-backup-file-restore: 3.0.1-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.2
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

Nur von der CT

Code: 
root@experpsy:~# journalctl -b
Jul 26 12:33:44 experpsy systemd-journald[49]: Journal started
Jul 26 12:33:44 experpsy systemd-journald[49]: Runtime Journal (/run/log/journal/ed07257968d64572a521ceb5ec198ba6) is 8.0M, max 1.4G, 1.4G free.
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
Jul 26 12:33:44 experpsy systemd-journald[49]: Time spent on flushing to /var/log/journal/ed07257968d64572a521ceb5ec198ba6 is 2.372ms for 3 entries.
Jul 26 12:33:44 experpsy systemd-journald[49]: System Journal (/var/log/journal/ed07257968d64572a521ceb5ec198ba6) is 484.5K, max 4.0G, 3.9G free.
Jul 26 12:33:44 experpsy systemd[1]: Finished systemd-sysusers.service - Create System Users.
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev...
Jul 26 12:33:44 experpsy systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
Jul 26 12:33:44 experpsy systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Jul 26 12:33:44 experpsy systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems.
Jul 26 12:33:44 experpsy systemd[1]: Reached target local-fs.target - Local File Systems.
Jul 26 12:33:44 experpsy systemd[1]: Starting networking.service - Raise network interfaces...
Jul 26 12:33:44 experpsy systemd[1]: systemd-binfmt.service - Set Up Additional Binary Formats was skipped because of an unmet condition check (ConditionPathIsReadWrite=/proc/sys).
Jul 26 12:33:44 experpsy systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id).
Jul 26 12:33:44 experpsy systemd[1]: systemd-sysext.service - Merge System Extension Images into /usr/ and /opt/ was skipped because no trigger condition checks were met.
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-tmpfiles-setup.service - Create Volatile Files and Directories...
Jul 26 12:33:44 experpsy systemd[1]: systemd-udevd.service - Rule-based Manager for Device Events and Files was skipped because of an unmet condition check (ConditionPathIsReadWrite=/sys).
Jul 26 12:33:44 experpsy systemd[1]: Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
Jul 26 12:33:44 experpsy systemd[1]: systemd-timesyncd.service - Network Time Synchronization was skipped because of an unmet condition check (ConditionVirtualization=!container).
Jul 26 12:33:44 experpsy systemd[1]: Reached target time-set.target - System Time Set.
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
Jul 26 12:33:44 experpsy systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
Jul 26 12:33:44 experpsy systemd[1]: Reached target sysinit.target - System Initialization.
Jul 26 12:33:44 experpsy systemd[1]: Started postfix-resolvconf.path - Watch for resolv.conf updates and restart postfix.
Jul 26 12:33:44 experpsy systemd[1]: Started apt-daily.timer - Daily apt download activities.
Jul 26 12:33:44 experpsy systemd[1]: Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
Jul 26 12:33:44 experpsy systemd[1]: Started dpkg-db-backup.timer - Daily dpkg database backup timer.
Jul 26 12:33:44 experpsy systemd[1]: Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
Jul 26 12:33:44 experpsy systemd[1]: fstrim.timer - Discard unused blocks once a week was skipped because of an unmet condition check (ConditionVirtualization=!container).
Jul 26 12:33:44 experpsy systemd[1]: Started logrotate.timer - Daily rotation of log files.
Jul 26 12:33:44 experpsy systemd[1]: Started man-db.timer - Daily man-db regeneration.
Jul 26 12:33:44 experpsy systemd[1]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
Jul 26 12:33:44 experpsy systemd[1]: Reached target paths.target - Path Units.
Jul 26 12:33:44 experpsy systemd[1]: Reached target timers.target - Timer Units.
Jul 26 12:33:44 experpsy systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket.
Jul 26 12:33:44 experpsy systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket.
Jul 26 12:33:44 experpsy systemd[1]: Reached target sockets.target - Socket Units.
Jul 26 12:33:44 experpsy systemd[1]: systemd-pcrphase-sysinit.service - TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41>
Jul 26 12:33:44 experpsy systemd[1]: Reached target basic.target - Basic System.
Jul 26 12:33:44 experpsy systemd[1]: Started cron.service - Regular background program processing daemon.
Jul 26 12:33:44 experpsy systemd[1]: Starting dbus.service - D-Bus System Message Bus...
Jul 26 12:33:44 experpsy systemd[1]: Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots...
Jul 26 12:33:44 experpsy systemd[1]: getty-static.service - getty on tty2-tty6 if dbus and logind are not available was skipped because of an unmet condition check (ConditionPathExists=!/usr/bin/dbus-daemon).
Jul 26 12:33:44 experpsy systemd[1]: Started postfix-resolvconf.service - Copies updated resolv.conf to postfix chroot and restarts postfix..
Jul 26 12:33:44 experpsy cron[84]: (CRON) INFO (pidfile fd = 3)
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-logind.service - User Login Management...
Jul 26 12:33:44 experpsy systemd[1]: systemd-pcrphase.service - TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c>
Jul 26 12:33:44 experpsy cron[84]: (CRON) INFO (Running @reboot jobs)
Jul 26 12:33:44 experpsy systemd[1]: Started dbus.service - D-Bus System Message Bus.
Jul 26 12:33:44 experpsy systemd[1]: postfix-resolvconf.service: Deactivated successfully.
Jul 26 12:33:44 experpsy systemd-logind[88]: New seat seat0.
Jul 26 12:33:44 experpsy systemd[1]: Started systemd-logind.service - User Login Management.
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-networkd.service - Network Configuration...
Jul 26 12:33:44 experpsy systemd-networkd[97]: Failed to increase receive buffer size for general netlink socket, ignoring: Operation not permitted
Jul 26 12:33:44 experpsy systemd-networkd[97]: eth0: Link UP
Jul 26 12:33:44 experpsy systemd-networkd[97]: eth0: Gained carrier
Jul 26 12:33:44 experpsy systemd-networkd[97]: lo: Link UP
Jul 26 12:33:44 experpsy systemd-networkd[97]: lo: Gained carrier
Jul 26 12:33:44 experpsy systemd-networkd[97]: Enumeration completed
Jul 26 12:33:44 experpsy systemd[1]: Started systemd-networkd.service - Network Configuration.
Jul 26 12:33:44 experpsy systemd-networkd[97]: eth0: Lost carrier
Jul 26 12:33:44 experpsy systemd-networkd[97]: eth0: Gained carrier
Jul 26 12:33:44 experpsy systemd[1]: e2scrub_reap.service: Deactivated successfully.
Jul 26 12:33:44 experpsy systemd[1]: Finished e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots.
Jul 26 12:33:44 experpsy systemd[1]: Finished networking.service - Raise network interfaces.
Jul 26 12:33:44 experpsy systemd[1]: Reached target network.target - Network.
Jul 26 12:33:44 experpsy systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Jul 26 12:33:44 experpsy systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions...
Jul 26 12:33:44 experpsy systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions.
Jul 26 12:33:44 experpsy systemd[1]: Started console-getty.service - Console Getty.
Jul 26 12:33:44 experpsy systemd[1]: Started container-getty@1.service - Container Getty on /dev/tty1.
Jul 26 12:33:44 experpsy systemd[1]: Started container-getty@2.service - Container Getty on /dev/tty2.
Jul 26 12:33:44 experpsy systemd[1]: Reached target getty.target - Login Prompts.
Jul 26 12:33:44 experpsy sshd[132]: Server listening on :: port 22.
Jul 26 12:33:44 experpsy systemd[1]: Started ssh.service - OpenBSD Secure Shell server.
Jul 26 12:33:45 experpsy systemd[1]: Finished ifupdown-wait-online.service - Wait for network to be configured by ifupdown.
Jul 26 12:33:45 experpsy systemd[1]: Reached target network-online.target - Network is Online.
Jul 26 12:33:45 experpsy systemd[1]: Starting postfix@-.service - Postfix Mail Transport Agent (instance -)...
Jul 26 12:33:45 experpsy postfix[184]: Postfix is using backwards-compatible default settings
Jul 26 12:33:45 experpsy postfix[184]: See http://www.postfix.org/COMPATIBILITY_README.html for details
Jul 26 12:33:45 experpsy postfix[184]: To disable backwards compatibility use "postconf compatibility_level=3.6" and "postfix reload"
Jul 26 12:33:45 experpsy systemd-networkd[97]: eth0: Gained IPv6LL
Jul 26 12:33:45 experpsy postfix/postfix-script[273]: starting the Postfix mail system
Jul 26 12:33:45 experpsy postfix/master[275]: daemon started -- version 3.7.6, configuration /etc/postfix
Jul 26 12:33:45 experpsy systemd[1]: Started postfix@-.service - Postfix Mail Transport Agent (instance -).
Jul 26 12:33:46 experpsy systemd[1]: Starting postfix.service - Postfix Mail Transport Agent...
Jul 26 12:33:46 experpsy systemd[1]: Finished postfix.service - Postfix Mail Transport Agent.
Jul 26 12:33:46 experpsy systemd[1]: Reached target multi-user.target - Multi-User System.
Jul 26 12:33:46 experpsy systemd[1]: Reached target graphical.target - Graphical Interface.
Jul 26 12:33:46 experpsy systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Jul 26 12:33:46 experpsy systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Jul 26 12:33:46 experpsy systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Jul 26 12:33:46 experpsy systemd[1]: Startup finished in 2.145s.
Jul 26 12:33:52 experpsy login[130]: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)
Jul 26 12:33:52 experpsy login[130]: pam_systemd(login:session): Failed to create session: Seat has no VTs but VT number not 0
Jul 26 12:33:52 experpsy login[284]: ROOT LOGIN  on '/dev/tty1'
Jul 26 12:34:20 experpsy sshd[296]: Accepted password for root from 192.168.50.52 port 57264 ssh2
Jul 26 12:34:20 experpsy sshd[296]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jul 26 12:34:20 experpsy systemd-logind[88]: New session 5 of user root.
Jul 26 12:34:20 experpsy systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Jul 26 12:34:20 experpsy systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Jul 26 12:34:20 experpsy systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Jul 26 12:34:20 experpsy systemd[1]: Starting user@0.service - User Manager for UID 0...
Jul 26 12:34:20 experpsy (systemd)[299]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Jul 26 12:34:20 experpsy systemd[299]: Queued start job for default target default.target.
Jul 26 12:34:20 experpsy systemd[299]: Reached target paths.target - Paths.
Jul 26 12:34:20 experpsy systemd[299]: Reached target sockets.target - Sockets.
Jul 26 12:34:20 experpsy systemd[299]: Reached target timers.target - Timers.
Jul 26 12:34:20 experpsy systemd[299]: Reached target basic.target - Basic System.
Jul 26 12:34:20 experpsy systemd[1]: Started user@0.service - User Manager for UID 0.
Jul 26 12:34:20 experpsy systemd[1]: Started session-5.scope - Session 5 of User root.
Jul 26 12:34:20 experpsy sshd[296]: pam_env(sshd:session): deprecated reading of user environment enabled
Jul 26 12:34:20 experpsy systemd[299]: Reached target default.target - Main User Target.
Jul 26 12:34:20 experpsy systemd[299]: Startup finished in 238ms.
Jul 26 12:39:01 experpsy CRON[315]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 26 12:39:01 experpsy CRON[316]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 26 12:39:01 experpsy CRON[315]: pam_unix(cron:session): session closed for user root

Eine Firewall läuft da nicht dazwischen. ich habe die Grundeinstellungen so gelassen um die CT zu installieren.
Wollte die CT mal auf einem Proxmox 7.4 zurückspielen

Code: 
recovering backed-up configuration from 'local:backup/vzdump-lxc-101-2023_07_26-12_42_24.tar.zst'
restoring 'local:backup/vzdump-lxc-101-2023_07_26-12_42_24.tar.zst' now..
extracting archive '/var/lib/vz/dump/vzdump-lxc-101-2023_07_26-12_42_24.tar.zst'
Total bytes read: 734423040 (701MiB, 85MiB/s)
Detected container architecture: amd64
merging backed-up and given configuration..
TASK ERROR: unable to restore CT 300 - unsupported debian version '12.1'

Ich hatte mal auf dem Proxmox 8 das Template Debian 11 probiert! GING auch nicht ABER!!

Code: 
apt-get --purge remove openssh-server
reboot
apt-get install openssh-server

JETZT GEHTS mal auf Debian 11!

Code: 
apt  --purge remove openssh-server

reboot

apt install openssh-server

JETZT GEHTS  auf Debian 12 auch!!

Bei dem Proxmox 7.x konnte ich die Debian Templates installieren und den SSH Port ändern, da ging alles.

danke nochmal für deine Antwort.
 
Exakt die gleiche Vorgeschichte und dieselben Probleme und 2 Tage damit verbracht, eine Ursache zu finden...
Danke für die Lösung @hackmann - die zwar einwandfrei funktioniert aber doch wohl eigentlich nicht sein kann...

apt remove --purge openssh-server
apt install openssh-server

Danach wieder alle gewünschten Änderungen in der "sshd_config" gemacht und ein abschliessendes
systemctl restart ssh && systemctl restart sshd

"reboot" war in meinem Fall nicht notwendig.

Weitere Infos:
Das verwendete LXC-Template ist das debian-12-standard-12.0-1_amd64.tar.zst
Die openssh-server Version war die 1:9.2p1-2 und ist NACH der Neuinstallation ebenfalls die 1:9.2p1-2
Wie sich anderweitige Änderungen in der "sshd-config" auswirkten, kann ich nicht mehr nachvollziehen, deffinitiv aber blieb die Änderung des PORT wirkungslos.
 
Last edited:
Hi :
I hit the same problem at ct image debian11
sshd won't accept my change ssh port at sshd_config
after I edited sshd_config and restart sshd service I got new ssh port
but when I reboot ct , it will back to 22port

it seems this bug from ct image debian10,11 and debian12 still has this bug
ct image debian9 has no problem

by the way ct image debian11 has another problem
nohup won't work
tmux , screen the same
anything you wanna run in background won't work
after you logout background process was kill
 
Last edited:
try this 3 commands may solve your ssh port problem

systemctl disable ssh.socket systemctl stop ssh.socket reboot
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back