Skip to main content
This page helps you diagnose and resolve common problems with MOPS services. If your issue isn’t listed, please reach out to our support team.

​
Table of Contents

​
Service Down

  • Service is not responding
  • 5xx errors in logs
  • Health checks failing
Steps to Diagnose:
  1. Check service status with: 
    systemctl status mops-service
  2. Review recent logs: 
    journalctl -u mops-service --since "10 minutes ago"
  3. Ensure dependencies (database, network) are operational.

​
Deployment Failures

  • Incorrect environment variables
  • Build errors
  • Insufficient permissions
Steps to Diagnose:
  1. Review deployment logs for errors.
  2. Verify all required environment variables are set.
  3. Check permissions for deployment user.

​
Configuration Errors

  • Service starts but behaves unexpectedly
  • Error messages about missing config
Steps to Diagnose:
  1. Validate your configuration file syntax.
  2. Ensure all required fields are present.
  3. Restart the service after changes.

​
Authentication Issues

  • Users cannot log in
  • 401/403 errors
Steps to Diagnose:
  1. Confirm authentication service is running.
  2. Check user credentials and permissions.
  3. Review authentication logs for errors.

​
Contact Support

If you can’t resolve your issue, please contact support with:
  • A description of the problem
  • Steps you’ve tried
  • Relevant logs or screenshots
Continually add new troubleshooting topics below as new issues are discovered!