Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The systemd unit's ExecStart and WorkingDirectory determine which binary runs, which config is used and how relative paths resolve.
- A filename extension does not prove the content format; check the running Realm binary, its help and documentation for that release.
- Back up the unit and config and confirm a maintenance path before edits; daemon-reload and service restart change the running relay.
- A TCP listener does not prove VLESS client, authentication, encryption or UDP forwarding passed end-to-end checks.
Find out which configuration the service actually loads
If a Realm service is active but has no expected listener, or the listener differs from the configuration, first inspect the actual systemd command. ExecStart may point to another Realm binary or an old config path; WorkingDirectory affects relative paths. Active only describes process state, not whether the expected file was read or every forward was created.
Do not infer the parser from config.toml, config.json or a filename alone. Realm branches, releases and packages can differ in command-line options and configuration syntax. Use the version of the binary that is running, its help output and documentation for that release. If the unit points to a fork, do not assume upstream examples apply unchanged.
Read the unit, process and current listener
Use systemd to inspect the unit file, ExecStart, WorkingDirectory, user and startup result, then check the process and the expected TCP listener. Replace unit and port placeholders with actual values. systemctl cat may reveal paths or arguments, and journals may include domains and upstream addresses; redact them before sharing.
Also read the current Realm binary's version and help to confirm its supported flags and config entry points. Do not inspect several ambiguous binaries at once, and do not run an install script or download a new installer during diagnosis.
Read Realm unit, process and port state
shUNIT='REPLACE_WITH_REALM_SYSTEMD_UNIT'
systemctl cat "$UNIT"
systemctl show "$UNIT" -p ExecStart -p WorkingDirectory -p User -p ActiveState -p SubState
systemctl status "$UNIT" --no-pager
ss -ltnp | grep -E ':(REPLACE_WITH_CONFIGURED_PORT)([[:space:]]|$)'
Match the binary version, config path and actual format
Confirm that ExecStart points to the Realm binary currently installed, then read the version and help it reports. Open the absolute config path referenced by the unit and check that the file exists, is nonempty and uses TOML or JSON syntax actually supported by that release. File extensions do not convert TOML, JSON or YAML into one another; renaming a file is not a format conversion.
If the working directory differs from expectation, a relative path may resolve somewhere else. Use the exact absolute path in the unit or configure the working directory consistently in the service. Before editing, confirm the target and that the service account can read it. Do not print or paste the whole configuration if it contains proxy usernames, passwords, private keys, node addresses or UUIDs.
Correct the smallest confirmed mismatch with a backup
If the unit references the wrong config, correct only that path. If the syntax is unsupported by the binary, convert it to the structure documented for the matching release. Do not upgrade the binary, rewrite every relay rule and change ports in the same edit. Keep recoverable copies of the unit and config, and confirm that local management remains available before applying changes.
After editing a systemd unit, run daemon-reload so systemd reads it again; restart interrupts active connections. If validation or startup fails, restore the backed-up unit and config, run daemon-reload and start the original service. Do not hide a broken unit by manually launching another Realm process.
Check the referenced config file
shCONFIG='/ABSOLUTE/PATH/REFERENCED/BY/EXECSTART'
test -s "$CONFIG" && stat -c '%s %n' -- "$CONFIG"
head -n 20 "$CONFIG"
Verify the listener and application protocol separately after restart
After recovery, confirm the unit is active, the process command line references the expected binary and config, and the correct process owns the target TCP port. Then establish an actual application-protocol session from an authorized client and send a permitted test request. A TCP handshake proves only that a listener accepted the transport connection; it does not prove VLESS client protocol, account parameters or encryption settings match.
If UDP relay is required, test it separately with a real client and destination that produce UDP traffic. A TCP listener or HTTP response does not prove UDP works. If VLESS, UDP or sustained-run checks have not been performed, state that those scopes remain unverified.
Version scope, rollback and sensitive config boundaries
Realm upstream releases, third-party forks and local packages can expose different command-line behavior. Record the exact binary version, source, systemd target and config format, then follow the matching release documentation. Do not present an old TOML example or fork-specific argument as universal syntax for current Realm.
If the binary, unit manager, relative-path behavior or sensitive fields are unclear, stop and ask the maintainer to verify them before changing state. Roll back by restoring the saved unit and config, then start through systemd. Protect relay addresses, user credentials, tunnel settings and real server paths; do not include them in public tutorials or logs.
Sources
Frequently Asked Questions
Does an active systemd unit prove the Realm config is correct?
No. Check ExecStart, WorkingDirectory, process arguments and the expected listener, then confirm the actual config was read.
Can I fix a format mismatch by renaming config.toml to config.json?
No. An extension does not convert contents. Confirm the format supported by the running binary and convert to the documented structure.
Does a TCP listener prove a VLESS client works?
No. Verify the protocol handshake, parameters and destination request with the actual client. Test UDP separately if required.
Why run daemon-reload after editing a unit?
systemd must reread the unit file. Restarting the service interrupts connections, so back up the unit and config and prepare rollback first.