PID limit on Pterodactyl (HAProxy)

Expected Behavior

Server should operate normally as excepted even with HAProxy enabled

Actual Behavior

With HAProxy enabled on Pterodactyl panel a server randomlly loops and takes up all the avaliable CPU (with PID limit disabled). If PID limit is enabled it gets hit and server is killed.

It loops with players online or with no players. Looping is random. Sometimes it takes a few days, sometimes just a few minutes.

With HAProxy enabled. About 6 endpoints are opened at the start up process. Sometimes velocity is unable to even close with endpoints and server needs to be hard shutdown (killed) in order to restart.

Steps to Reproduce

Run Velocity server on Pterodactyl server
Enable HAproxy in the .toml configuration file
Wait

Plugin List

AutoUodateGeyser
CleanPing
Custom F3 Brand
FooodGate
ForceResourcePack
Geyser
JPremium
LuckPerms
mdMOTD
plan
SkinsRestorer
Sonar
Tebex
Velocity-hub
Voicechat
VotifierPlus

Velocity Version

[11:14:35 INFO]: Velocity 3.4.0-SNAPSHOT (git-8f65a814-b558)

Additional Information

No response

Start by running the reported Velocity server on Pterodactyl with HAProxy enabled in the .toml configuration, then observe CPU, PID usage, and endpoint shutdown behavior. Compare runs with and without HAProxy; done means the random loop and failure to close endpoints are reproducibly understood and no longer occur.