Settings

The Settings page is where host and user administration live after initial setup: a Hosts card and a Users card, each with per-row actions.

The Hosts card

Each host row has four actions.

Sync polls that host right now instead of waiting for the next scheduled check. It runs the same poll cycle the schedule does, so a forced sync and a scheduled one never disagree about what they find, it can take a few seconds to return since it waits for the node to actually answer.

Rotate replaces a host’s stored API token, its SSH key, or both. A new API token is verified against the node before it replaces the old one, so a mistyped token can’t take the host offline with no way back. Rotating the SSH key hands you a new public key to authorize on the node, the same step as SSH key enrollment, since the old key stops working the moment the new one is generated.

Tasks shows the node’s own task list and lets you open any task’s log, including work Proxploy didn’t start itself, useful for answering “why did my container restart at 3am” when the answer isn’t in Proxploy’s own job history.

Remove forgets a host and everything Proxploy cached about it: every app row, VM cache row, and stored credential, gone. The node itself is never touched. A host that still has apps on it is refused until you either uninstall them or explicitly choose to forget those app rows too, so you can’t lose track of a running container by accident. Removing a host asks you to type its name back first.

The Users card

Each user row has three actions, all admin-only.

Deactivate locks an account out immediately, every one of its live sessions is revoked the moment you do it, not just new logins going forward. Reactivating is the same button. You can’t deactivate your own account, and you can’t deactivate the last active owner, promote someone else first.

Reset password sets a new password for someone else’s account without needing their old one, meant as a recovery path, not routine account sharing. Every session of theirs is revoked, same as deactivation, but their two-factor enrollment is left alone: 2FA belongs to the user, not the admin resetting their password.

Delete removes the account and its team memberships outright. Prefer deactivating instead when you can, a deleted user’s past actions in the audit log become unattributable, a deactivated one’s don’t. You can’t delete your own account or the last owner.