sintonia/docs/admin-manual/troubleshooting.md

---
title: Troubleshooting
sidebar_position: 90
---

This guide walk you though the steps required to troubleshoot LibreTime.

## FAQ

### I cannot login the interface "Oops! Something went wrong!"

You might be accessing the interface from an invalid URL. Make sure that the URL in your browser and the one set in your configuration file in `[general.public_url]` are the same.

Make sure to check the legacy logs at `/var/log/libretime/legacy.log`.

References:

- https://discourse.libretime.org/t/version-3-0-1-debian-oops-something-went-wrong/1400

## Logs

The first place to search for details on potential errors are the log files.

The `/var/log/syslog` file contains most of the system logs combined. This log file may contain information that the application logger wasn't able to log, such as early startup errors. You can follow the logs using:

```bash
sudo tail -n 100 -f "/var/log/syslog"
# Filter the logs
sudo tail -n 100 -f "/var/log/syslog" | egrep 'libretime|nginx|php.*-fpm'
```

On a common setup, to access LibreTime specific logs you should search for the following files:

- The `/var/log/libretime/analyzer.log` file contains logs from the analyzer,
- The `/var/log/libretime/api.log` file contains logs from the api,
- The `/var/log/libretime/legacy.log` file contains logs from the legacy app,
- The `/var/log/libretime/liquidsoap.log` file contains logs from liquidsoap,
- The `/var/log/libretime/playout.log` file contains logs from playout.
- The `/var/log/libretime/worker.log` file contains logs from the worker.

For some LibreTime services, you can set a higher log level using the `LIBRETIME_LOG_LEVEL` environment variable, or by running the service by hand and using a command line flag:

```bash
sudo -u libretime libretime-analyzer --config /etc/libretime/config.yml --log-level debug
```

The `/var/log/nginx/libretime.error.log` file contains logs from the web server.

## Services status

The next reflex is to verify whether the services are running.

In the web interface, go to **Settings** > **Status** to see the state of the services.

![](./troubleshooting-status-page.png)

Or directly from a terminal:

```bash
sudo systemctl --all --plain | egrep 'libretime|nginx|php.*-fpm'
```

If a service isn't running, you should search for details using the tool running those services.
On a common setup, you should use the systemd service status:

```bash
sudo systemctl status libretime-worker
```

:::note

Be sure to replace the service name with the problematic one.

:::

## Test the stream inputs

To test or debug your input streams, you can use the [`tools/test-stream-input.py`](https://github.com/libretime/libretime/blob/main/tools/test-stream-input.py) script to send a test sound to your stream inputs.

To test the `main` input stream, you can run the following command:

```bash
./tools/test-stream-input.py \
    --host radio.example.org \
    --port 8001 \
    --mount main \
    --user source \
    --password hackme

# Or using the --url option
./tools/test-stream-input.py --url source:hackme@radio.example.org:8001/main
```

If you are hitting `HTTP error 401 Unauthorized` on the main input stream, make sure that you have configured a user and password in the **Settings** > **Streams settings** page.

If you are connected but don't hear anything streaming, make sure that the main input stream is connected and enabled. In addition, to automatically turn on/off the stream on connect/disconnect you can configure the input stream auto switch in the **Settings** > **Streams settings** page.