Lavalink Node is not connecting despite Lavalink Server responding

[Dave187420]

Bug description

Description: I am encountering an issue where my Lavalink node is not connecting to the Lavalink server, even though the server is running and responding. When I run a curl request to check the version (http://localhost:2333/version), I get the correct response (4.0.8), indicating that the server is working. However, the node shows as isAlive: false, and no communication is happening between the client and the server.

Verified that the Lavalink server is running and accessible at localhost:2333 by checking the version.
Checked the application.yml file for correct configuration (server password, port, etc.).
Attempted to restart the Lavalink server.
Tried to connect the node with the correct authorization token.
Adjusted only the .env file to match the required credentials.

Steps to reproduce

Steps to Reproduce:

Start the Lavalink server on localhost:2333 with the correct password (youshallnotpass).
Configure the Lavalink node to connect to localhost:2333 with the same password.
The only change I made was to adjust the .env file with the necessary bot and server credentials.
Start the application or bot that is supposed to interact with the Lavalink node docker compose.

Operating System

Ubuntu 20.10

Node.js version

LTS

java version

No response

Application/Library version

Releases 33 v4.6.7

Error logs or screenshots

Expected Result: The Lavalink node should connect to the Lavalink server successfully and start interacting with it.

Actual Result: The node does not connect and is marked as isAlive: false. Despite receiving the correct version response from the server (4.0.8), the following error is shown in the logs:
heartBeatPingTimestamp: 0, heartBeatPongTimestamp: 0, heartBeatInterval: undefined, pingTimeout: undefined, isAlive: false, ...
Additionally, there are errors related to the server not finding the correct node:
Error: No available Node was found, please add a LavalinkNode to the Manager via Manager.NodeManager#createNode
Logs:
[12/27/2024] [8:49:27 PM] [shard.js] [Lavamusic] › ▶ start [CLIENT] Shard 0 connected to Discord's Gateway. [12/27/2024] [8:50:51 PM] [InteractionCreate.js] [Lavamusic] › ✖ error Error: No available Node was found, please add a LavalinkNode to the Manager via Manager.NodeManager#createNode
Network Check:

When running the following curl command:

curl -X GET "http://localhost:2333/version" -H "Authorization: youshallnotpass"
I receive the correct response:
4.0.8
Configuration: The Lavalink node is configured with the following settings:
{ "id": "Local Node", "host": "localhost", "port": 2333, "authorization": "youshallnotpass", "secure": false, "retryAmount": 5, "retryDelay": 60000, "heartBeatInterval": 30000, "closeOnError": true }
.env File: The only modification I made was to adjust the .env file with the following:

TOKEN="your-bot-token" PREFIX="!" OWNER_IDS=["your-discord-id"] GUILD_ID="your-guild-id" PRODUCTION="true"
Steps Taken:

Additional context

No response