Troubleshooting

Activation email

If the activation message is missing, confirm the spelling of the signup address, check spam and company quarantine, then request a fresh link from the verification page. Use the newest message because a resend invalidates older unused links.

An expired or already used link cannot be reused. If the account is already active, return to sign in. Never send the activation URL to support.

Server connection

Reproduce the connection from an authorized terminal before changing Tnion.SH settings:

ssh -p 22 deploy@203.0.113.10

Check the host, port, username, password, firewall, provider security group, and SSH service. If the fingerprint changed, confirm whether the server was rebuilt before accepting the new destination.

If metrics fail after a successful connection test, confirm the stored password is current and the deployment account can read the required system information.

Provisioning

Open the latest deployment and find the first failing step. Common causes include insufficient privileges, unavailable package repositories, low disk space, conflicting ports, Docker or Nginx configuration problems, and a hostname that does not reach the intended server.

Do not repeatedly submit Provision while another deployment is active. Correct the underlying server condition, then retry through the supported action.

GitHub and module deployments

If repositories are missing, review the GitHub App installation and selected repository access. Reconnect a suspended installation. Confirm that the configured branch exists and that the target instance has already been provisioned.

For an Odoo module update failure, review the deployment log and repository structure. Each addon must include a valid __manifest__.py, and its dependencies must be available to the target Odoo environment.

Backups and restores

A backup requires a provisioned instance and adequate disk space on the registered server. Check the recorded error, remote capacity, and service state.

Restores accept successful restorable full archives. Confirm that the artifact still exists on the server. Wait for any active deployment to finish before retrying.

Contact support

Provide:

• Workspace slug.
• Project and environment.
• Approximate time and time zone.
• Action you attempted.
• Visible error and relevant deployment-log excerpt.
• Whether the issue is repeatable.

Do not provide passwords, private keys, database administrator credentials, activation links, reset links, invitation links, session cookies, or GitHub tokens. Contact support@tnion.com during the MVP domain phase or use the contact page.