When authentication fails, the path from problem to solution isn’t always obvious. A token that worked perfectly yesterday might fail today for reasons that aren’t immediately apparent. This guide provides a systematic approach to diagnosing and resolving authentication issues, helping you move from confusion to clarity when things go wrong.

​
Common Errors

​
401 Unauthorized – Token Not Validated

Occurs when Monime can’t recognize your token. This can happened due to one of the reasons:
  1. Expired token – check the token’s lifetime.
  2. Malformed token – ensure the full string is sent with no extra spaces.
  3. Revoked token – Check if token may have been disabled, deleted, or the associating Monimeer itself offboarded.
  4. Environment mismatch – mon_ for production, mon_test_ for sandbox.

​
403 Forbidden – Permission Intersection Failed

  1. Token is valid but lacks permissions for the operation.
  2. Check declared token permissions set at creation.
  3. Check Monimeer’s role in the Space—role changes can reduce access.
    Remember: effective permissions = token permissions ∩ Monimeer’s role permissions
  4. Check if token was bounded to a different space than the one in context.
  5. Check if IP allowlisting was configured for the token during creation.

​
Network & Environment Issues

  1. Verify connectivity to Monime endpoints.
  2. Check TLS certificates, system clock, and DNS resolution.
  3. Watch for proxy/firewall stripping Authorization or Monime-Space-Id headers.
  4. In containerized environments, ensure secrets are mounted and networking is correct.

​
When to Escalate

Contact Monime support or your Space admin if:
  1. Standard troubleshooting fails.
  2. The issue seems platform-side.
Most authentication problems are simple — expired tokens, wrong permissions, or misconfiguration. Check the basics first before diving deeper.