Geyser don't start on standalone ViaProxy

[Cremen2342]

Describe the bug

My server and viaproxy work through docker, game version 1.21. When starting containers, the Geyser issues strange logs, and does not start completely. When trying to log in to the server from Bedrock, the "Failed to connect to the world" bar is displayed. The number of players and server ping are not visible from the menu. At the same time, the server itself is fully operational and accessible from Java. Via Proxy logs, docker-compose file and config files for both ViaProxy and Geyser are attached.

latest.log

To Reproduce

1. Run docker-compose up -d.
2. Wait until it creates all the directories.
3. Replace viaproxy.yml in /via-proxy-data/ with the attached version.
4. Replace config.yml in /via-version-data/plugins/Geyser/ with the attached version.
5. Run the docker-compose up -d again

Expected behaviour

All containers are running, the server, ping and the number of players are visible by the IP address and port from Bedrock, while players can log in from Java (one IP address each) and from Bedrock (using the IP address and port)

Screenshots / Videos

Server Version and Plugins

Server running on 1.21 Fabric

Geyser Dump

No response

Geyser Version

2.6.1-b767 (git-master-fd4c805)

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

Here is configs and docker-compose files:
(https://drive.google.com/drive/folders/1eaaDRfqqzLajNpp_t_HRvYCE9cR1u2LR?usp=sharing)

[eclipseisoffline]

It seems your docker compose file, viaproxy.yml and Geyser config.yml files haven't been attached, could you please try to send them again?

[Cremen2342]

It seems your docker compose file, viaproxy.yml and Geyser config.yml files haven't been attached, could you please try to send them again?

Hi! Github does not allow attaching .yml-files, so i upload them on a google drive: https://drive.google.com/drive/folders/1eaaDRfqqzLajNpp_t_HRvYCE9cR1u2LR?usp=sharing

[juster-0]

@Cremen2342 if I understand yml correctly then you've added additional spaces in config.yml at line 44 and there should not be any address there.
Your:

  remote: 172.17.0.1

but should be:

remote:

[onebeastchris]

Yeah, this looks like a bungled Geyser config - odd that there wasn't an earlier error about that.

[onebeastchris]

Closing as this appears to have been a config issue