2.5.x version starts but 2.6 oder 2.7 crashes (Hetzner) (solved)

Hallo,
I try to install a Rancher 2.7.x on a dedicated Host (Hetzner) using docker-ce.
The problem:
Starting der rancher ends with an error like
[FATAL] k3s exited with: exit status
I found out that rancher 2.5 latest version is working. Has anyone a hint wher to search to solve this problem.

Ralf

2023/10/14 12:26:54 [INFO] Rancher arguments {ACMEDomains: AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2023/10/14 12:26:54 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:26:56 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:26:58 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:27:00 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:27:02 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:27:04 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:27:06 [INFO] Waiting for server to become available: Get “https://127.0.0.1:6444/version?timeout=15m0s”: dial tcp 127.0.0.1:6444: connect: connection refused
2023/10/14 12:27:11 [FATAL] k3s exited with: exit status 2
[root@outdoor ~]#

Hallo,
solution
modprobe ip_tables
echo ‘ip_tables’ >> /etc/modules-load.d/rancher.conf
reboot
iptable -L should give you a result as a check that it is working