Troubleshooting

If your questions are not answered on this page or within the FAQ, please submit a support ticket and our support team will respond as soon as possible!

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.

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

chmod +x floating-server

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:

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

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:

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

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:

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

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

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