Node running on Synology NAS DSM 7.2 shows only US sessions with low earnings and "Unknown"

[aalejaandro]

_myst-node_logs (2).txt

I'm running a Mysterium node on a Synology NAS DS920+ (DSM 7.2) using Docker / Portainer.
The node was working properly in the past, but after a recent update (not sure which one, probably DSM or node update), the node stopped behaving as before.

It still goes Online and shows Great quality, but:

• It only receives US sessions.
• All sessions show “Unknown” under Service type in the UI.
• However, when exporting the session list, the serviceType field shows quic_scraping.
• Earnings are extremely low and traffic volume is minimal.
• Node quality sometimes fluctuates to Poor or Monitored Failed depending on port mode (bridge/host).

Environment

• Hardware: Synology NAS DS920+
• System: DSM 7.2
• RAM: 8192 MB

Docker runtime: via Portainer

Container name: mysterium-node

• Node version: 1.35.5 (also tested 1.33, 1.34, 1.35)
• UI version: 3.1.1
• Node ID: 0x324d604c7414ee381a5445b7233cef0afc766d08
• NAT Status: Moderate

Docker Run Command

docker run --cap-add NET_ADMIN \
  --restart=always \
  --device=/dev/net/tun \
  -d \
  -p 4449:4449 \
  -p 42049-42070:42049-42070/udp \
  --name mysterium-node \
  -v /volume1/docker/myst:/var/lib/mysterium-node \
  --entrypoint /bin/sh \
  mysteriumnetwork/myst:latest \
  -c "ln -sf /sbin/iptables-legacy /sbin/iptables && \
      ln -sf /sbin/ip6tables-legacy /sbin/ip6tables && \
      myst service --agreed-terms-and-conditions"

Observed Behavior

• Node goes Online.
• Status and Quality show as Great.
• Sessions appear, but only from the US region.
• Each session shows Unknown service, even though the JSON export lists serviceType: quic_scraping.
• No visible errors in logs.
• Tried running the container from scratch (clean volume) — same result.

Tried both bridge and host networking modes — same result.

Tried with different port ranges — same result.

Logs during startup show no iptables-related errors, but older builds showed messages related to nft vs legacy

_myst-node_logs (2).txt

EDIT:

I still with the issue with iptables after all, but I dont know why node seems great and online.

2025-10-08T01:24:10.558756306Z 2025-10-08T01:24:10.558 ERR ../../core/service/session_manager.go:199 > Session failed, disconnecting error="cannot get provider config for session 80157405-61bd-42b6-9a02-810007cfc6ed: failed to setup NAT/firewall rules: error calling IPTables: "/usr/sbin/iptables -I PREROUTING 1 --source 10.182.2.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"

2025-10-08T01:24:10.558895014Z 2025-10-08T01:24:10.558 DBG ../../session/pingpong/invoice_tracker.go:685 > Stopping invoice tracker for session 80157405-61bd-42b6-9a02-810007cfc6ed

2025-10-08T01:24:10.558945360Z 2025-10-08T01:24:10.558 INF ../../core/service/session_manager.go:193 > session ref decr for "channel:0xc005f64180"

2025-10-08T01:24:10.559046523Z 2025-10-08T01:24:10.558 ERR ../../p2p/channel.go:437 > Handler "p2p-session-create" internal error error="cannot start session: : cannot get provider config for session 80157405-61bd-42b6-9a02-810007cfc6ed: failed to setup NAT/firewall rules: error calling IPTables: "/usr/sbin/iptables -I PREROUTING 1 --source 10.182.2.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"

[aalejaandro]

Only US connections and Unknow Service

[aalejaandro]

same with 1.36.5...

[stale]

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.