Repository navigation
Description
As suggested in the team chat, this issue collects my node findings, fixes and test results in one place, so nothing gets lost in chat. Each item links to its own issue or PR; I'll keep this list up to date.
How I work: trace the cause in the source, write a regression test that fails on the current release, build the fix on top of the official code, run it on my own nodes, then report here. Every change is reviewed for possible attack vectors. One fix per commit / PR.
Fixed and released
- Provider signs quality metrics with a foreign or empty identity → "Failed to sign metrics event" #6220 Metrics signing with the wrong identity ("Failed to sign metrics event: authentication needed") — fixed in fix: sign provider quality metrics with the correct identity #6221, released in 1.39.8
- Session price check (accept only prices listed by discovery) + price-check nil guard — Price nil guard #6227, released in 1.39.8
- Per-session WireGuard traffic stops while P2P remains responsive; paired consumer traces on 1.39.5-derived builds #6218 Provider kept answering keepalive pings for sessions it had closed — fixed in fix: validate session in keepAliveLoop and add corresponding tests #6228, released in 1.39.9. 24 h field results: Per-session WireGuard traffic stops while P2P remains responsive; paired consumer traces on 1.39.5-derived builds #6218 (comment)
In progress
- Provider blocks a handler goroutine forever on payment messages after a session is closed #6232 Late payment messages after a session is closed were still queued into a channel nobody reads, blocking a handler goroutine forever. Fix + regression test in PR fix: do not queue payment messages without an active session #6233 (on top of 1.39.9). 24 h on my node: 127 sessions, 1,827 payment messages handled normally, 0 queue timeouts, 0 panics. Waiting for review.
Checked / answered
- Bump github.com/klauspost/compress from 1.18.0 to 1.18.7 #6224 Dependabot klauspost/compress 1.18.0 → 1.18.7: builds, all packages pass on 1.39.8 (only e2e needs the docker env) — looks safe to merge
- Improve the Performance of the Discovery API #5626 Discovery API performance: answered — api/v4 + gzip + server-side filters cover the original request (Improve the Performance of the Discovery API #5626 (comment))
- no upgarde to 1.39.7 -> 1.39.5 olny #6223 Upgrade stuck on 1.39.5: not a node bug (an older .deb was reinstalled)
- [v1.38.1] Registration stuck InProgress forever — transactor failure blocks identity permanently #6190 Registration stuck "in progress": the error comes from the transactor queue, not the node — needs a check on the transactor side
- Please Update Mystnode only one API or Auth key access type and dont need go gui localhost for auth #6230 Link a node to mystnodes.com with only an API key, without the web UI: answered —
--mmn.api-keyclaims the node automatically (Please Update Mystnode only one API or Auth key access type and dont need go gui localhost for auth #6230 (comment)) - Monitoring failed #6202 Monitoring failed (
internet_failon 1.39.9): answered with the node-side checks (Monitoring failed #6202 (comment)). The team traced it to a 1280 MTU limit on the reporter's path and adjusted monitoring on their side; the node is Online since 6 Nov (Monitoring failed #6202 (comment)). Still open: very little traffic per session; asked about the path MTU and--wireguard.mtu(Monitoring failed #6202 (comment)) - Monitoring failed persists on Oracle Cloud nodes after ruling out iptables, rate-limit, NAT and firewall — WireGuard sessions drop after ~1-2s handshake #6209 Monitoring failed on Oracle Cloud: solved and closed. Oracle's default
/etc/iptables/rules.v4ends the FORWARD chain with an unconditional-A FORWARD -j REJECT, which blocked the forwarding rules the node adds for its VPN subnet: the tunnel came up but passed no traffic (ip_connectivity_fail). After removing that rule both nodes are Online and earning. The "Failed to sign metrics event" part from the comments is Provider signs quality metrics with a foreign or empty identity → "Failed to sign metrics event" #6220, fixed in 1.39.8
Issue cleanup proposal (all open issues, checked against 1.39.9)
Every open issue in this repo was read in full (body and all comments) and checked against release 1.39.9 (ad20e9d). Each row gives the status, the evidence in the source where there is any, and a proposed action. Closing is the maintainers' decision; this list is only meant to save time.
Issue numbers are written without "#" on purpose, so this list does not add a cross-reference to dozens of old issues.
Actions: close (done / not a bug / no info) · answer (short reply, then close if the reporter agrees) · keep (still valid) · team (needs a decision or backend access) · other component (NodeUI, mystnodes.com, apps, docs — not node code).
| Count | |
|---|---|
| Bugs | 7 |
| Feature requests that already exist (fully or partly) | 10 |
| Still valid, found while checking | 2 |
| Requests for other components | 31 |
| Outdated | 9 |
| Still-valid feature requests | 19 |
| Already answered (5626) / tracking (6231, 6232) | 3 |
| Total open issues | 81 |
Proposed to close now or after a short answer: 6218, 6223, 5370, 5931, 5236, 1623, 1654, 2475, 4551, 5637, 5739, 5746, 5953 (and 6230 once the reporter confirms).
1. Bugs (7)
| Issue | Title | Status on 1.39.9 | Evidence | Action |
|---|---|---|---|---|
| 6218 | WireGuard traffic stops while P2P stays responsive | Fixed | Keepalive handler rejects pings for closed/unknown sessions (6228, core/service/session_manager.go). Not auto-closed because 6228 isn't linked. |
close |
| 6223 | No upgrade to 1.39.7, stays on 1.39.5 | Not a bug | An older .deb saved by wget (.deb.3) was reinstalled. Answered in the issue. |
close |
| 5370 | Bandwidth limit removed after restart/update (2022, Docker) | Can't reproduce on a normal install | NodeUI saves the limit via POST /config/user → SaveUserConfig (tequilapi/endpoints/config.go:169) into config-mainnet.toml, loaded on every start. Survived many restarts and version changes on 1.39.9. Lost only if the config dir is lost (e.g. a container recreated without a volume). |
answer, then close |
| 6190 | Registration stuck "InProgress" | Server side | "could not queue entry: registration in progress" is not in node code; it comes from the transactor and is forwarded (tequilapi/endpoints/transactor.go). The node re-checks registration on-chain (registry_contract.go). |
team (transactor queue entry) |
| 6202 | Monitoring failed (+ internet_fail on 1.39.9) |
Cause found, follow-up open | internet_fail comes from the quality oracle (core/quality/mysterium_morqa.go). The team traced it to a 1280 MTU limit on the reporter's path and adjusted monitoring on their side; node Online since 6 Nov. Very little traffic per session is still open. |
keep until the reporter answers |
| 6209 | Monitoring failed on Oracle Cloud | Solved, closed | An unconditional -A FORWARD -j REJECT in Oracle's default /etc/iptables/rules.v4 blocked the node's VPN forwarding; removed by the reporter, both nodes Online. Not a node bug. The "Failed to sign metrics event" part is 6220, fixed in 1.39.8. |
closed |
| 6006 | WebUI session tied to IP, not IP:port | Bug, node-side cause | The login cookie has a fixed name token (core/auth/jwt.go:42) while each node signs its login with its own key; browsers separate cookies per host, not per port, so two nodes opened through one IP overwrite each other's login. The reporter's two nodes use separate internet lines; only the management IP is shared. A port in the cookie name would not help his Docker setup (both containers use 4449 inside); the name has to be unique per node |
keep — small fix possible |
2. Feature requests that already exist (fully or partly) (12)
| Issue | Request | Status on 1.39.9 | Evidence | Action |
|---|---|---|---|---|
| 5931 | Fixed local port for a consumer in proxy mode | Exists | myst connection up --proxy <port> (cmd/commands/connection/command.go), since Jan 2022 |
answer, then close |
| 6230 | Add a node to mystnodes.com with only an API key | Exists | --mmn.api-key; the node claims itself on service start (mmn/mmn.go). Answered. |
close once the reporter confirms |
| 6157 | Debian 13 (Trixie) support | Works in practice | Official .deb (amd64, arm64) installs and runs on Debian 13; only a Debian-named PPA build is missing. |
answer |
| 5236 | Automatic reconnect for consumers | Exists in the CLI | --auto-reconnect (2021) and --keep-connected-on-fail (2021). Apps are separate. |
answer, then close |
| 4590 | Auto-connect to a chosen region | Partly | myst connection up --country XX with --auto-reconnect; no connect-on-daemon-start. |
answer; keep only for connect-on-start |
| 3924 | Kill switch active from consumer start | Partly | --firewall.killSwitch.always (Linux only) |
keep |
| 5611 | Fall back to userspace mode | Partly | --userspace exists but must be set by hand |
keep |
| 5636 | No sudo when already root | Partly | sudo is hard-coded in kernel mode (nat/factory_linux.go, firewall/iptables/iptables.go, utils/cmdutil/command.go) without a root check |
keep — small fix possible |
| 5528 | Quality in myst connection proposals |
Partly | connection up sorts by quality by default; proposals has no quality column |
keep — small CLI change |
| 3144, 3853 | Run a node / consumer behind a national firewall via a proxy | 3853 option (b) exists: consumer proxy mode myst connection up --proxy <port> (cmd/commands/connection/command.go). Proxying the node's own traffic (3144, 3853 option a) does not exist |
The HTTP transport sets no Proxy (requests/transport.go), and the broker is NATS over plain TCP (nats://broker.mysterium.network, metadata/network.go). An HTTP proxy setting alone would not get a node working behind such a firewall; the broker connection needs a proxy route too |
answer 3853 about --proxy; team for the design (3144) |
| 4653 | Kill switch when the IP doesn't change | Still valid | On IPNotChanged the node only reports the status (core/connection/manager.go, checkSessionIP) |
keep |
3. Requests for other components (31)
| Issue | Request | Component | Note | Action |
|---|---|---|---|---|
| 1605 | Review the tech documentation | Docs | — | other component |
| 2053 | Android app on F-Droid | Mobile app (node library involved) | The app pulls the node library as a versioned dependency (mobile-release.yml); F-Droid would need that library built from source too (mobile/mysterium) |
other component |
| 3355 | Install guide for Arch Linux | Docs | install.sh supports apt-based systems only (install.sh:128-133); Docker is the route on Arch |
answer, docs |
| 3700 | Chrome extension | Apps | A consumer proxy mode exists (--proxy <port>) |
other component |
| 4149 | Smart reconnect in desktop/mobile apps | Apps | The CLI already has it | other component |
| 4382 | Better in-app issue reports | Support tooling | — | other component |
| 4545 | Tiering for node runners | NodeUI / mystnodes | Business decision | other component |
| 4551 | Better identity backup instructions | Docs | A docs PR was linked in 2022 | other component, probably close |
| 4595 | MikroTik v7 | Docs / community | — | other component |
| 4624 | 2FA for NodeUI / mystnodes | NodeUI, mystnodes | — | other component |
| 4636 | Speedtests for node runners | NodeUI | No speedtest in the node | other component |
| 4658 | Sort columns on "My Nodes" | mystnodes | — | other component |
| 4681 | Country advice for the "verified partner traffic" setting | NodeUI / T&Cs | The setting exists in the node (access-policy.list, access-policy.fetch) |
other component |
| 4782 | Keystore backup/restore in NodeUI | NodeUI | The node API supports it: POST /identities/export (localhost only), POST /identities-import |
other component |
| 4963 | EUR/USD value of transactions for tax filing | mystnodes / NodeUI | — | other component |
| 4972 | Hide the tray icon | Desktop app | — | other component |
| 5582 | Staking reward statistics | Stats / docs | — | other component |
| 5823 | Connect by region | Apps | The CLI has --country |
other component |
| 5824 | Browser extension | Apps | Same request as 3700 | other component |
| 5825 | Earnings per day instead of per session start | NodeUI | — | other component |
| 5828 | Android node app: import/export identity | Mobile app | The node API supports it (see 4782) | other component |
| 5829 | Android node app: background permission | Mobile app | — | other component |
| 5831 | Android node app: permanent notification | Mobile app | — | other component |
| 5844 | Config for UniFi UDM / Pro / SE | Docs / community | — | other component |
| 5852 | Android: backup/restore buttons | Mobile app | The node API supports it (see 4782) | other component |
| 5860 | Sort history data | NodeUI | — | other component |
| 5862 | Change the email on mystnodes | mystnodes | A workaround is in the comments | other component |
| 6005 | WebUI login: focus on the password field | NodeUI | — | other component |
| 6020 | 2FA / passkey | NodeUI, mystnodes | Same request as 4624 | other component |
| 3799 | LAN access while connected (Windows consumer) | Unclear | No CLI option found; Windows routing not checked in depth | unclear — team |
| 6023 | Slower node ID rotation for Mysterium Dark | Unclear | Probably discovery / the Dark app; not checked in node code | unclear — team |
4. Outdated (9)
| Issue | Request | Status on 1.39.9 | Evidence | Action |
|---|---|---|---|---|
| 1590 | More developer-friendly Go API (RFC) | No activity since 2020 | — | team (close or keep as design topic) |
| 1623 | Put the device in a separate VLAN | Concern covered | Consumer traffic to private networks is blocked by default: firewall.protected.networks = 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,127.0.0.0/8 (config/flags_node.go:104-108) |
answer, then close |
| 1654 | Choose auto-update at startup | Declined in 2020 | Maintainer comment in the issue | close |
| 2475 | Securing CI services (redis) | Probably resolved | In docker-compose.e2e-basic.yml redis only uses expose, no published port |
close (team confirms) |
| 4374 | Servers inside the network (like onion services) | Roadmap question, never answered | — | team (answer or close) |
| 5637 | SysV init script | Exists | The package ships bin/package/installation/initd.sh; post-install.sh installs it when systemctl is missing |
answer, then close |
| 5739 | "node identity id to an ip address" | No description | Title only | close |
| 5746 | IP banned by services / price per GiB | Answered by the community | Nodes can accept verified partner traffic only (access-policy.list) |
answer, then close |
| 5953 | Why do datacenter nodes earn less? | Answered by the community | — | close |
5. Still-valid feature requests (19)
| Issue | Request | Status on 1.39.9 | Evidence | Action |
|---|---|---|---|---|
| 1164 | Docker image security check in CI | Not done | No image scanner in .github/workflows |
keep (CI) |
| 1178 | Lock unused identities | Not done | Only PUT /identities/:id/unlock, no lock endpoint (tequilapi/endpoints/identities.go) |
team |
| 2041 | Securing the Web UI (RFC) | Partly | Security topic | team |
| 2485 | Password-protect the private keys | Partly | --identity.passphrase exists; payout to another address via beneficiary; no separate password-protected withdrawal identity |
keep (epic) |
| 3580 | Option to block torrent traffic | Not done | No port/protocol blocking for consumer traffic; only LAN protection | team (policy) |
| 4058 | Monthly data cap for providers | Not done | Only a speed limit (shaper.enabled, shaper.bandwidth) |
keep |
| 4068 | Mysterium for the whole home network (consumer) | Not done | Linux consumer can connect; routing a whole network is not provided | team (design + docs) |
| 4341 | Encrypted DNS (DoH/DoT) on nodes | Not done | The provider DNS proxy forwards to the system resolver (dns/sytemcfg_unix.go:29) |
keep |
| 4596 | Multihop by geo-location | Not done | Large design | team |
| 4710 | pfSense package | Not done | No FreeBSD build | team (packaging) |
| 4737 | Better security measures | Partly | LAN protection exists; no metrics endpoint for Prometheus/Grafana | keep |
| 5153 | Accept connections only from chosen countries | Not done | No consumer-country filter (location.* flags describe the node itself) |
team (policy) |
| 5529 | Graceful upgrade with active sessions | Not done | — | team |
| 5570 | Port mapping (inbound ports via a node) | Not done | Large design | team |
| 5843 | Port forwarding behind CGNAT | Not done | Same request as 5570 | team |
| 5910 | Failover / redundancy for node runners | Not done | Large design | team |
| 6097 | Let the consumer choose its tunnel IP | Not done | The provider assigns one subnet per session from 10.182.0.0/16 (config/flags_service_wireguard.go:36) |
team (protocol) |
| 6211 | nftables support | Not done | The node configures iptables (nat/service_iptables.go) |
team |
| 6214 | AmneziaWG instead of WireGuard | Not done | Large change | team |
Activity