> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/floating-server/floating-server-v1/deployment-methods/executable/troubleshooting.md).

# Troubleshooting

{% hint style="info" %}
If your questions are not answered on this page or within the [**FAQ**](/floating-server/faq.md), please [**submit a support ticket**](https://licensespring.zendesk.com/hc/en-us/requests/new) and our support team will respond as soon as possible!
{% endhint %}

<details>

<summary>Missing or Incorrect Configuration File</summary>

**Solution**: Ensure the `config.yaml` file is created and placed in the correct directory. By default, the Floating Server looks for the configuration file in the `config` directory located in the same folder as the executable. If the file is located elsewhere, use the `-config` argument when starting the server:

`./floating-server.exe -config /path/to/config.yaml`

Make sure the `config.yaml` file is correctly formatted, and all required fields (like the database type and API keys) are present.

</details>

<details>

<summary>Floating Server Not Starting</summary>

**Solution**: Ensure the server is running with sufficient permissions. On Linux/macOS, you may need to give execution rights to the binary:

```bash
chmod +x floating-server
```

</details>

<details>

<summary>Unable to Connect to Redis</summary>

**Solution**: Verify that Redis is running and that the connection details in the `config.yaml` file are correct. Make sure the Redis instance is accessible from the machine running the Floating Server:

```yaml
database:
  type: redis
  addresses:
    - localhost:6379
```

If Redis is running on a different machine, ensure the correct IP address and port are provided.

</details>

<details>

<summary>Floating Server Port Not Available</summary>

**Solution**: If the Floating Server is not accessible on the specified port, ensure that the port is not already in use by another application. You can specify a different port in the `config.yaml` file:

```yaml
port: 8080
```

Make sure any firewall or security settings allow incoming connections on the chosen port.

</details>

<details>

<summary>Logs Not Generated</summary>

**Solution**: Ensure the log file location is correctly specified in the `config.yaml` file. The default log file location is `logs/floating-server.log`, but you can specify a custom path:

```yaml
logFile: /path/to/log/file.log
```

Verify that the directory for the log file exists and that the server has write permissions for that directory.

</details>

<details>

<summary>File-Based Database Not Working</summary>

**Solution**: If you're using a file-based database and encountering issues, ensure the `config.yaml` file is set up correctly:

```yaml
database:
  type: file
  addresses:
    - ./database
```

Make sure the specified directory for storing the database files exists and has the appropriate permissions.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.licensespring.com/floating-server/floating-server-v1/deployment-methods/executable/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
