Skip to content

[Bug]On Debian 12, installing Fail2ban via the Script Library may fail to start if the SSH port is not set to 22 #9107

@verkyer

Description

@verkyer

Contact Information

No response

1Panel Version

v2.0.1

Problem Description

debian12系统,通过【脚本库】,安装【Fail2ban】起不来!
SSH端口是非22的,之前安装完正常,修改成非22就起不来了。
v1版本都没有问题

Steps to Reproduce

debian12系统,通过【脚本库】,安装【Fail2ban】起不来!

Image
Image
Image

The expected correct result

No response

Related log output

root@spartan-vm-bf20-e3-2c1g-sea:/# bash -c "$INIT_SCRIPT"
Detected system: debian 12
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease                                             
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                     
Hit:4 https://download.docker.com/linux/debian bookworm InRelease                                 
Reading package lists... Done                                                                     
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  mailx system-log-daemon monit sqlite3
The following NEW packages will be installed:
  fail2ban
0 upgraded, 1 newly installed, 0 to remove and 64 not upgraded.
Need to get 0 B/451 kB of archives.
After this operation, 2,180 kB of additional disk space will be used.
Selecting previously unselected package fail2ban.
(Reading database ... 30973 files and directories currently installed.)
Preparing to unpack .../fail2ban_1.0.2-2_all.deb ...
Unpacking fail2ban (1.0.2-2) ...
Setting up fail2ban (1.0.2-2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/fail2ban.service → /lib/systemd/system/fail2ban.service.
Processing triggers for man-db (2.11.2-2) ...
× fail2ban.service - Fail2Ban Service
     Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2025-06-16 10:41:31 CST; 2s ago
   Duration: 152ms
       Docs: man:fail2ban(1)
    Process: 827590 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
   Main PID: 827590 (code=exited, status=255/EXCEPTION)
        CPU: 130ms

Jun 16 10:41:31 spartan-vm-bf20-e3-2c1g-sea systemd[1]: Started fail2ban.service - Fail2Ban Service.
Jun 16 10:41:31 spartan-vm-bf20-e3-2c1g-sea fail2ban-server[827590]: 2025-06-16 10:41:31,489 fail2ban.configreader   [827590]: W…'auto'
Jun 16 10:41:31 spartan-vm-bf20-e3-2c1g-sea fail2ban-server[827590]: 2025-06-16 10:41:31,501 fail2ban                [827590]: E…d jail
Jun 16 10:41:31 spartan-vm-bf20-e3-2c1g-sea fail2ban-server[827590]: 2025-06-16 10:41:31,507 fail2ban                [827590]: E…failed
Jun 16 10:41:31 spartan-vm-bf20-e3-2c1g-sea systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
Jun 16 10:41:31 spartan-vm-bf20-e3-2c1g-sea systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
2025-06-16 10:41:34,357 fail2ban                [827613]: ERROR   Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

Additional Information

No response

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions