Elytrium / Elytrium/LimboHub

Velocity LimboHub as a fallback server

Open
#5 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
42
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Hello, can you help me please?

I wanna use the LimboHub as a fallback server (try) server, but I can't config it.

Situation:
I can try connect to parkour server from LimboHub lobby, but my server under maintenance and can't connect it.

Problem:
Always kicking the player from the HUB / Velocity server, can't connect automatically for LimboHub.

---

_First try:_
Result message: Unable to connect you to parkour. Please try again later.

Velocity config:
```
[servers]
parkour = "x.x.x.x:25565"
hub = "127.0.0.1:25565"

try = []
```

Logs:
```
proxy-main_1 | [17:04:42 INFO] [geyser]: /W.X.Y.Z:38814 tried to connect!
proxy-main_1 | [17:04:43 INFO] [geyser]: Player connected with username userfoobar
proxy-main_1 | [17:04:44 INFO] [geyser]: userfoobar (logged in as: userfoobar) has connected to the Java server
proxy-main_1 | [17:04:44 INFO] [floodgate]: Floodgate player who is logged in as userfoobar 00000000-0000-0000-0000-00000000 joined
proxy-main_1 | [17:04:46 INFO] [limboapi]: userfoobar (/W.X.Y.Z:0) has connected to the LimboHub Limbo
proxy-main_1 | [17:05:06 INFO] [limboapi]: userfoobar (/W.X.Y.Z:0) has disconnected from the LimboHub Limbo
proxy-main_1 | [17:05:07 ERROR]: [connected player] userfoobar (/W.X.Y.Z:0): unable to connect to server parkour
proxy-main_1 | java.net.UnknownHostException: server-parkour: Name or service not known
[...]
proxy-main_1 | [17:05:07 INFO]: [connected player] userfoobar (/W.X.Y.Z:0) has disconnected: Unable to connect you to parkour. Please try again later.
proxy-main_1 | [17:05:07 INFO] [floodgate]: Floodgate player logged in as userfoobar disconnected
proxy-main_1 | [17:05:07 INFO] [geyser]: userfoobar has disconnected from the Java server because of Unable to connect you to parkour. Please try again later.
```

---

_Second try:_
Result message: You are already connected to this proxy!

Velocity config:
```
[servers]
parkour = "x.x.x.x:25565"
hub = "127.0.0.1:25565"

try = ["hub"]
```

```
proxy-main_1 | [17:10:12 INFO] [geyser]: /W.X.Y.Z:38814 tried to connect!
proxy-main_1 | [17:10:14 INFO] [geyser]: Player connected with username userfoobar
proxy-main_1 | [17:10:14 INFO] [geyser]: userfoobar (logged in as: userfoobar) has connected to the Java server
proxy-main_1 | [17:10:14 INFO] [floodgate]: Floodgate player who is logged in as userfoobar 00000000-0000-0000-0000-00000000 joined
proxy-main_1 | [17:10:16 INFO] [limboapi]: userfoobar (/W.X.Y.Z:0) has connected to the LimboHub Limbo
proxy-main_1 | [17:10:33 INFO] [limboapi]: userfoobar (/W.X.Y.Z:0) has disconnected from the LimboHub Limbo
proxy-main_1 | [17:10:33 ERROR]: [connected player] userfoobar (/W.X.Y.Z:0): unable to connect to server parkour
[...]
proxy-main_1 | [17:10:33 INFO]: [server connection] userfoobar -> hub has connected
proxy-main_1 | [17:10:33 INFO]: [connected player] userfoobar (/127.0.0.1:46992) has disconnected: You are already connected to this proxy!
proxy-main_1 | [17:10:33 INFO]: [server connection] userfoobar -> hub has disconnected
proxy-main_1 | [17:10:33 ERROR]: [connected player] userfoobar (/W.X.Y.Z:0): disconnected while connecting to hub: You are already connected to this proxy!
proxy-main_1 | [17:10:33 INFO]: [connected player] userfoobar (/W.X.Y.Z:0) has disconnected: Unable to connect to hub: You are already connected to this proxy!
proxy-main_1 | [17:10:33 INFO] [floodgate]: Floodgate player logged in as userfoobar disconnected
proxy-main_1 | [17:10:33 INFO] [geyser]: userfoobar has disconnected from the Java server because of Unable to connect to hub: You are already connected to this proxy!
```

Thank you!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the failed parkour connection with the two shown Velocity [servers] configurations and compare the LimboHub and Velocity disconnect logs. Trace the fallback connection path from the reported LimboHub disconnect through Velocity's server connection handling; done means a maintenance-time failure returns the player to the configured hub without disconnecting them.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.