Help
Troubleshooting
Fixes for the messages you’re most likely to see, from network permission to certificates and consoles.
Couldn’t reach a server on your local network
What you see: Couldn’t reach…, Local Network Access Blocked or Waiting for Local Network Access.
Why: macOS asks before an app may connect to devices on your network. This often happens after an update, because macOS may treat the new version as a new app.
Fix: open System Settings › Privacy & Security › Local Network (the Open Privacy & Security button goes there) and turn Moxie Prox on. If it’s already on, turn it off and on again. If it isn’t listed, drag Moxie Prox from Applications into the list. Moxie Prox connects by itself as soon as it’s allowed.
Couldn’t connect
Moxie Prox retries timeouts and refused connections quietly for a while before it shows Couldn’t connect with Try Again. Check that the address and port are right, that the host is up, and that your Mac can reach it (for example over your VPN).
“Invalid URL” when adding a cluster
In version 1.1, the Host field takes only a host name or IP address. Remove https:// and the port, and put the port in Port, or update to version 1.2, which accepts a pasted URL.
Sign-in refused
Include the realm in the user name, for example root@pam or alice@pve. The OpenID realm field is only for OpenID Connect sign-ins. For an API token, the Token ID is user@realm!tokenname.
A certificate prompt appears
- Unverified certificate: compare the fingerprint with Node › System › Certificates in Proxmox before you trust it.
- Certificate changed: expected after a certificate renewal. If you didn’t renew it, someone may be intercepting the connection: don’t trust it until you’ve checked with whoever runs the server.
Coming in the next version.
To check a certificate yourself, choose Settings › Connections › Check Certificate… on a cluster’s row (on a Mac or iPad, it’s also in the cluster’s menu). It reads the server’s certificate now and says whether it’s the one the cluster trusts. If it changed, you see both fingerprints and nothing changes until you choose Trust New Certificate. A certificate your device already trusts (Let’s Encrypt, for example) is never pinned; if the cluster still pins an old one, Stop Pinning… lets your device’s trust decide from then on.
A menu item is dimmed
Moxie Prox shows why. Most often your login lacks a permission (for example Needs the VM.Console permission), the object is in the wrong state (Start the VM to open its serial terminal), or Proxmox doesn’t allow it (Proxmox pools can’t be renamed or moved). Ask your Proxmox administrator for the permission it names.
Consoles time out behind a load balancer
A VM’s screen is set up in two steps that must reach the same Proxmox host. If your cluster’s address is a load balancer that sends each request to a different host, the console times out. Make the balancer keep each client on one host (source-IP stickiness), or add the cluster by one host’s own address.
The VM’s pointer doesn’t line up
Choose Turn On Tablet in the screen’s notice. It adds a USB tablet device, which takes effect at the VM’s next restart.
SPICE does nothing
Install a SPICE viewer app. Without one, Moxie Prox shows No SPICE Viewer and Get a SPICE Client.
Two-factor with a security key
Security keys and passkeys can’t be used from the app. Add an authenticator app (TOTP) or recovery keys to your Proxmox user in Proxmox’s web page.
Known issues in 1.3
- Moving a guest to a folder may need Move pressed twice.
Checked against Moxie Prox 1.3. Updated November 9, 2026.