node icon indicating copy to clipboard operation
node copied to clipboard

Monitoring Failed

Open lanfeust13 opened this issue 6 months ago • 4 comments

Hello Team,

I update 1.34.1 to 1.35.4 my docker

error 1 :

ERR ../../core/service/session_manager.go:199 > Session failed, disconnecting error="cannot get provider config for session eaaea791-6551-4d1d-a8e2-82ea5091d04b: failed to setup NAT/firewall rules: error calling IPTables: "/usr/sbin/iptables -I PREROUTING 1 --source 10.182.0.2/24 --jump MYST --table nat": exit status 4 output: iptables v1.8.11 (nf_tables): Could not fetch rule set generation id: Invalid argument\n: exit status 4"

Error 2 :

WRN ../../nat/service_iptables.go:60 > Error detected, clearing up rules that were already setup

Error 3 :

iptables v1.8.11 (nf_tables): Could not fetch rule set generation id: Invalid argument

Can you help me ?

Best regards

lanfeust13 avatar Jul 21 '25 14:07 lanfeust13

similar issue

2025-08-18T14:13:06.936993372Z [90m2025-08-18T14:13:06.936[0m [33mDBG[0m [1m../../nat/service_iptables.go:229 [0m[36m >[0m "/usr/sbin/iptables --new MYST --table nat" output:

2025-08-18T14:13:06.937161950Z

2025-08-18T14:13:06.993211092Z [90m2025-08-18T14:13:06.992[0m [33mDBG[0m [1m../../nat/service_iptables.go:229 [0m[36m >[0m "/usr/sbin/iptables -A MYST --destination 10.0.0.0/8 --jump DNAT --to-destination 240.0.0.1 --table nat" output:

2025-08-18T14:13:06.993315214Z Warning: Extension DNAT revision 0 not supported, missing kernel module?

2025-08-18T14:13:06.993348755Z iptables v1.8.11 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain MYST

any ideas?

kthemall avatar Aug 18 '25 14:08 kthemall

no ideas? thx tom

kthemall avatar Aug 20 '25 12:08 kthemall

Hello Team,

I update 1.34.1 to 1.35.4 my docker and i have similar issue on synology docker.

This is because of the switch to nftables (iptables-nft) which is not compatible with dsm 7.x which only supports iptables legacy.

vinz94f avatar Aug 25 '25 22:08 vinz94f

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Nov 25 '25 19:11 stale[bot]