Appendix · Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Dashboard does not open | Service stopped, or wrong port. | Start ProximaConnect-<tenant> in Windows Services; check the port with --list. |
| Setup says the sign-in could not be saved | Wrong tenant code, user or password, or no network. | Enter it on the dashboard: Settings › Proxima sign-in › Test sign-in, then Save sign-in. |
| Proxima connection test fails | Licence ended, user lacks the Integration User role, or wrong address. | Check the licence and role with your administrator; check the address opens in a browser on the server. |
| Zoho token invalid | Code expired (10 minutes, one use), wrong domain or a missing scope. | Generate a new code with the current scope list and Connect again. |
| Nothing is being sent | Dry run or Test mode is on, the switch is off, or locations are not confirmed. | Check Settings, What to sync and Locations; read the latest Events. |
| A document was not sent | Before the minimum date, an opening-balance type, or held. | Search it in Transactions; fix and Retry failed rows. |
| Duplicate customer in the accounting package | Different name or GSTIN in the two systems. | Merge in the accounting package; align account number and GSTIN. |
When asking for help, send the latest log file from <data folder>\logs and the relevant Events lines, with passwords and secrets removed.
Still stuck?
Message our support team on WhatsApp in English, Tamil, Malayalam or Hindi.