View logs (Linux)
To view logs:
sudo journalctl -u mysterium-node.service
To monitor logs in real time:
sudo journalctl -fu mysterium-node.service
Export logs (Linux)
To export logs from the node service:
sudo journalctl -u mysterium-node.service > node.log
This will save logs to a file named node.log in your current directory.
You can then share this file with support via email, chat or community channels.
View logs (Docker)
If your node is running in Docker, use:
docker logs myst
To monitor logs in real time:
docker logs -f myst
Export logs (Docker)
To save logs to a file:
docker logs myst > node.log
This will create a node.log file in your current directory.
If you don’t know the container name
Run:
docker ps
Look for the MystNode container (commonly named myst) and use that name in the commands above.
Submit issue via API (no UI required)
You can report an issue directly from your node using the local API.
Basic command
curl -X POST --data '{"description":"Your issue here"}' localhost:4050/feedback/issue Example
curl -X POST --data '{"email":"[email protected]","description":"Node is not visible on discovery even though it shows as online and receives test sessions"}' localhost:4050/feedback/issueemailis optional but recommendeddescriptionshould clearly explain the issue
Notes
The API runs locally on port 4050, so this must be executed on the same machine as the node
Make sure the node service is running before submitting the request
Logs provide more context, so include them when possible