> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trymondo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

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-down)
* [Deployment Failures](#deployment-failures)
* [Configuration Errors](#configuration-errors)
* [Authentication Issues](#authentication-issues)
* [Contact Support](#contact-support)

***

## Service Down

<Accordion title="Symptoms">
  * Service is not responding
  * 5xx errors in logs
  * Health checks failing
</Accordion>

**Steps to Diagnose:**

1. Check service status with:
   ```sh theme={null}
   systemctl status mops-service
   ```
2. Review recent logs:
   ```sh theme={null}
   journalctl -u mops-service --since "10 minutes ago"
   ```
3. Ensure dependencies (database, network) are operational.

***

## Deployment Failures

<Accordion title="Common Causes">
  * Incorrect environment variables
  * Build errors
  * Insufficient permissions
</Accordion>

**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

<Accordion title="Symptoms">
  * Service starts but behaves unexpectedly
  * Error messages about missing config
</Accordion>

**Steps to Diagnose:**

1. Validate your configuration file syntax.
2. Ensure all required fields are present.
3. Restart the service after changes.

***

## Authentication Issues

<Accordion title="Symptoms">
  * Users cannot log in
  * 401/403 errors
</Accordion>

**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](mailto:techsupport@trymondo.com) with:

* A description of the problem
* Steps you've tried
* Relevant logs or screenshots

***

<Callout type="info">
  Continually add new troubleshooting topics below as new issues are discovered!
</Callout>