Troubleshooting

The SSH connection fails

Confirm the same host, port, user and key work from your terminal. If they do not, the problem is between you and the server, not in MihraOps.

A connection that times out is usually a firewall or security group. A connection that is refused usually means nothing is listening on that port. Authentication that is rejected usually means the key is not in the server authorized_keys, or the private key has a passphrase you have not entered.

Host key verification failed

The fingerprint no longer matches what was recorded on the first connection. If you rebuilt or restored the server, this is expected: forget the stored fingerprint in the server settings and reconnect.

If you did not change the server, do not skip past this. Investigate before connecting again.

The certificate is not issued

Check the A record resolves to the server, from outside your own network. Check ports 80 and 443 are open and not already taken by another web server on the machine. A certificate authority has to reach the domain over the public internet, so a firewall rule that allows only your IP will block issuance.

The webhook does not deploy anything

A 401 means the token or signature did not match — check that the secret in your pipeline is the one shown when you created the trigger. A 404 means the trigger name in the URL does not exist or is disabled.

If the request succeeds but nothing changes, the image tag you deployed probably has not actually been updated in the registry; a redeploy pulls the same digest and correctly does nothing.

A blue-green deploy keeps failing

The candidate container is not becoming healthy. Deploy the same image without a domain and read its logs: the health check is either failing for a real reason, or it is stricter than the application needs — for example a start period shorter than the application takes to boot.

License activation errors

“License not found” almost always means a copy-paste problem: copy the key exactly as it appears in the license email, with no leading or trailing space.

“Activation limit reached” means the license is already active on another device. Deactivate it from that machine License screen, then activate the new one.

The Linux AppImage does not start

chmod +x mihraops-latest.AppImage