Meshly Meshly
Verification

Checklist for a Meshly-ready Matrix node.

Run through these checks before you hand the node to real users. They focus on what Meshly currently needs most: a reachable client API, a matching Matrix domain, and a working login flow.

DNS and firewall

  • The homeserver host resolves to the VPS from outside your network.
  • Ports 80, 443, and 8448 are open on the VPS firewall.
  • The Matrix host is DNS-only in Cloudflare if federation matters.

Client API checks

curl https://your-homeserver.example/_matrix/client/versions
curl https://your-homeserver.example/_matrix/client/v3/login \
  -H 'Content-Type: application/json' \
  -d '{"type":"m.login.password","identifier":{"type":"m.id.user","user":"your-user"},"password":"your-password"}'

If login succeeds, keep the access_token and use it to test whoami. 

curl https://your-homeserver.example/_matrix/client/v3/account/whoami \
  -H "Authorization: Bearer <access-token>"

Meshly app checks

  • Connect with homeserver URL plus username and password.
  • Create or join a room.
  • Restart the app and verify the session restores cleanly.
  • Send a message and confirm sync still works after relaunch.

Safe defaults to keep

  • Use PostgreSQL, not SQLite, for any serious deployment.
  • Keep the Admin API off the public internet.
  • Only leave open registration enabled if you are ready to moderate abuse.
  • Back up the Synapse data directory and database together.