Where Does NoMachine Store Connections and State?
NoMachine keeps per-user state in ~/.nx on Linux and Mac. Server config and logs live in the install folder instead.
Last updated
NoMachine splits state by side. The client keeps connections and caches in ~/.nx under your home. The server keeps its own config and logs in the install directory.
Client fixes usually mean touching ~/.nx. Stale locks from crashed sessions cause the classic refuses-to-connect loop. Clear locks with the client stopped and most of those clear up.
Where NoMachine stores this, by platform
~/.nx
Client connections, caches, and locks. Back up for migration, prune locks for repair. Same on Mac builds.
~/.nx
Same per-user state folder as Linux. Server side on Mac lives in its own install paths.
Frequently asked questions
How do I migrate NoMachine connections?
Stop the client and copy ~/.nx to the new machine. Connection entries travel with it. Server-side settings stay on the server and need separate handling.
Where are NoMachine logs?
Server logs sit under the install dir, commonly /usr/NX/var/log on Linux. Client logs sit in ~/.nx. Check the matching side for the error you see.
Can I delete ~/.nx to fix connection errors?
Yes for stale locks after crashes. Delete lock files inside ~/.nx while nothing runs. Live sessions keep state there too, so never wipe it mid-session.
Notice an outdated path? Let us know.