Two Bungeecord Errors

[Plooper12]

BungeeCord-Bootstrap:1.13-SNAPSHOT:367a127:222 by md_5

https://pastebin.com/8BBQaY6d

I do not know how to reproduce the error.

[spannerman79]

java.lang.IllegalArgumentException: Unexpected packet received during server login process!

Are they logging in with vanilla mc or with rift?

NB: There is no official forge release for 1.13 yet. Read the statement made by LexManos here

[Plooper12]

java.lang.IllegalArgumentException: Unexpected packet received during server login process!

Are they logging in with vanilla mc or with rift?

NB: There is no official forge release for 1.13 yet. Read the statement made by LexManos here

Hello I do not know what it means "rift"
they are only users entering with versions between 1.7 and 1.8

[Plooper12]

another bug but this sometimes appears on my bungee console
https://pastebin.com/0YD2LLRC

[Plooper12]

another bug
https://pastebin.com/buqAAdnv

[spannerman79]

#236 (comment)

Same issue as you.

Basically Hexacord needs to restore the patch that enabled modded 1.7.10 clients to connect that @dogboy21 proposed awhile ago.

https://github.com/HexagonMC/BungeeCord/releases/tag/v181

[Plooper12]

Hi, exactly what should I download from this link?
https://github.com/HexagonMC/BungeeCord/releases/tag/v181

[cuervito]

@spannerman79 hello, it would help me, as the kicked users that come with the version 1.7.10 solve .. the only version of hexa that walks me is the 198. but it's very old, try all the new versions and kick my users from 1.7.10 when another user comes in with version 1.8 forge .. which patch should I apply thanks

[Zilacon]

This is also an issue for me. I wanted to update my vanilla server to 1.13.2 which also acts as my HUB but no one can connect to my 1.7.10 modpack servers now. Will there ever be a fix for this?

[johnfriedrich]

@Zilacon This is likely a spigot issue, because by default, there are not enough channels. Here is the soloution:
ProtocolSupport/ProtocolSupport#488

[Zilacon]

@i9hdkill Its not. I tried over 20 versions from your releases page and only version 140 and below ended up working. I ended up having to go back to my dev's patched 1.12.2 version of hexacord to join my 1.7.10 server again.

Also i have no errors on either server about too many channels registered. Players connect, bungeecord confirms connection, but never sends the connection to 1.7.10. This DOES NOT happen with the 1.12.2 or the 1.11.2 versions im using. After about 15 seconds the connection times out on the 1.7.10 Thermos server.

[dogboy21]

another bug but this sometimes appears on my bungee console
https://pastebin.com/0YD2LLRC

This issue is probably caused by BungeeMSG, not Hexacord.

This is also an issue for me. I wanted to update my vanilla server to 1.13.2 which also acts as my HUB but no one can connect to my 1.7.10 modpack servers now. Will there ever be a fix for this?

Which Hexacord version are you using? We're using a variety of servers from Thermos 1.7.10 to Spigot 1.13.2 and don't have any problem.

[Zilacon]

@dogboy21 @i9hdkill Im using the latest 225 release, the most recent one on the releases page. I just tested it again to make sure.
Still does not work.

With official hexacord 225:

With my developers 1.12.2 hexacord version:

No problems connecting to the 1.7.10 modpack server on my dev's version. Connections to it on 225 hexacord simply time out.

[Zilacon]

This is a major problem because ive updated my Vanilla/HUB server to 1.13.2, along with updating all of the plugins for it. And right now no one can join it because i have to use a 1.12.2 hexacord version instead of 1.13.2...

[cuervito]

Hi, It's not going well, keep kicking users for ERROR PROXY DISCONNECTED. and it is not that you have to enter with 1.7.10. when a user with version 1.8 forge comes in, there he kicks the connected users with version 1.7

[Zilacon]

I dont have a single modpack or server with 1.8, so none of my users have 1.8. So i cannot give any input on that. All i know is the current version simply does not support 1.7.10.

[dogboy21]

I'm not able to reproduce any of these issues on v225.

As you can see, I'm on the server with Infinity Evolved 1.7.10 and there's also a player online with 1.8.

I'm also able to join a 1.7.10 server

[cuervito]

if I mean that since the version of hexacoord 1.98 onwards never again went well, when a player enters with 1.8 forge and there is a user 1.7 disconnects it from the server.

[Zilacon]

@dogboy21 Are you using Thermos for 1.7.10? Because i cannot connect at all using 225 on my end.

[dogboy21]

Yes, latest Thermos version

[Zilacon]

@dogboy21 Could you send me your bungeecord jar? Because it does not work for me from the version im using from the releases page.

Also what modpack are you using for the 1.7.10 server?

[dogboy21]

I'm using v225 from the releases page.
Modpack is Infinity Evolved

[Zilacon]

Hmm i have no idea why its working for you and not me.

[Sharkske]

i look into this in the past awhile back i think i found it to be a prob with cofh mod in the modpacks thats if i recall correctly its been awhile i gave up lol i kinda was looking on here hoping for a fix lol

[spannerman79]

Modpack is Infinity Evolved

The exact versions listed with https://www.feed-the-beast.com/projects/ftb-infinity-evolved/files/2484483 or have you updated any of TeamCOFH mods @dogboy21 ?

[dogboy21]

Yes. We use Infinity Evolved 3.0.2 without any changes.

EDIT: Is forge_support enabled in your Bungee config?

[Sharkske]

im about to run a test on my network with the new ver of hexacord, using Thermos

[Sharkske]

yea it works fine, i just get a error "Display name cannot be longer than 16 characters" i forgot how to edit it,
Edit: all fixed