Fabric server does not register itself
kxmpxtxnt opened this issue · 2 comments
Stacktrace
Actions to reproduce
When creating a fabric server (1.20.2) it does not appear in the servers list when typing /server (using velocity)
After adding it to the servers section in the velocity.toml it appears and everything works after installing Fabricproxy-lite and configuring it.
CloudNet version
[13.11 23:14:45.139] INFO: CloudNet Blizzard 4.0.0-RC10-SNAPSHOT 61dbda8
[13.11 23:14:45.139] INFO: Discord: https://discord.cloudnetservice.eu/
[13.11 23:14:45.139] INFO:
[13.11 23:14:45.139] INFO: ClusterId: a74b21a8--4fc4--c22aee346529
[13.11 23:14:45.139] INFO: NodeId: Node-1
[13.11 23:14:45.139] INFO: Head-NodeId: Node-1
[13.11 23:14:45.140] INFO: CPU usage: (P/S) 10.74/27.42/100%
[13.11 23:14:45.140] INFO: Node services memory allocation (U/R/M): 14848/14848/17864 MB
[13.11 23:14:45.140] INFO: Threads: 42
[13.11 23:14:45.140] INFO: Heap usage: 127/456MB
[13.11 23:14:45.140] INFO: JVM: Eclipse Adoptium 20 (OpenJDK 64-Bit Server VM 20.0.2+9)
[13.11 23:14:45.140] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: nightly
Other
No response
Issue uniqueness
- Yes, this issue is unique. There are no similar issues.
if you can show me the code where the server should be registered I can have a look at it
Can you please provide the log of your proxy & fabric service? I just tested creating a fabric service and it got registered without any problems