Connection Errors During Direct Proxy-to-Proxy Transfer Between Two Velocity Instances

[Jackcharled]

Client connection failures occur when traversing from Proxy-1 (Velocity) to servers behind Proxy-2 (Velocity), triggering unrecoverable errors.

[p0t4t0sandwich]

Do you mean two unrelated Velocity proxies, or do you mean a proxy behind a proxy?
Please provide the necessary information required to reproduce the issue (full logs, modlist, etc)

[Jackcharled]

a proxy behind a proxy
velocity version: velocity-3.4.0-SNAPSHOT-522
Server version: mohist-1.20.1-2eb79df
Ambassador version: Ambassador-Velocity-1.4.5-all
I removed the mods and tested in a mod-free environment, but this error still occurred. Then I used the Paper server and added Ambassador, yet the issue persisted—confirming that it is a plugin-related problem.
No error logs are recorded on the server backend, while the client displays this message and remains unable to join the server.

[p0t4t0sandwich]

A proxy behind a proxy is not supported officially by Velocity due to complicating things unnecessarily, so you shouldn't expect Ambassador to work correctly. Ambassador assumes the server behind the proxy is a regular server, not another proxy.

Please test with one proxy and Ambassador to see if that works as expected. If it does, then you know that the error is caused by not following best practices when proxying MC.

[p0t4t0sandwich]

You also decided not to share any logs, modlist, plugin list, or the fork of Velocity you're using to support proxy-behind-proxy connections, so it's impossible to replicate the issue anyway.