connection to a server randomly becomes good as long as i don't log off the server, becomes none after relogging

[TheKuba]

since i switched to  1.18 forge, i was unable to join any server more than once. my guess is that this is because of my internet connection, and i would've gave up a long time ago if that was true, because there's always the first time that i try to join- i get about 50ms the whole time, i can freely interact with the world and play the game. but the moment i log off, that is gone, i cannot return to that server ever again, for whatever reason i always start falling into the void with no chunks being able to load around me while my connection says i have 0ms. but why is this first time so easy on me? i'd like to know, but no one was really able to answer this question. please help, maybe there's a chance that if i can recreate this, i can play on servers normally?

[warjort]

Your question is unanswerable without more information, e.g. the logs/debug.log from the client and server

Edited October 14, 2022 by warjort

[TheKuba]

server latest.log: https://pastebin.com/SY7ZLkQ9

server debug.log: https://pastebin.com/6eQU5SfU

client latest.log: https://pastebin.com/kGFpGG47

if you have an idea of what might be happening but you need more information, just ask

[warjort]

It looks like one of your mods has broken networking.

Quote

[18:49:04] [Render thread/INFO]: Connecting to packsmp.ga, 25565

[18:49:06] [Render thread/WARN]: Unknown custom packed identifier: minecraft:register

But it is impossible to tell which one.

* You don't show the debug.log for the client so there is minimal information

* The client log you do show is for 12 minutes after the server log

* It is not even the full log

 

You can try adding the following system property to your java/jvm parameters to see if it gives more information but it will only be useful if you post the debug.log

-Dforge.logging.mojang.level=debug

Otherwise you will have to experiment with removing mods or search your mod's issues pages for known issues.

Edited October 14, 2022 by warjort

[TheKuba]

problem is- i didn't have any mods installed on either the server or the client at the time of creating those logs. as for the client's debug.log, i am absolutely confused as to why it isn't generating. is there some option i have to turn on for it to do so?

[warjort]

The debug.log is enabled by default unless your launcher turns it off. See my footer.

[TheKuba]

alright, i think this should be enough:

client debug.log: https://pastebin.com/qjUWVNF7

client latest.log: https://pastebin.com/8TvQeK2a

server debug.log: https://pastebin.com/89YuUzLw

server latest.log: https://pastebin.com/Lm1Dvfqk

i deleted a huge chunk of the server logs because i forgot to use a new world when i created those and the world that was used had mods installed, thus creating an absolute monster of an error message.

[warjort]

Those new logs don't show the same problem.

There are no errors during the login.

Server side says you are logged in.

Quote

[14Oct2022 20:44:40.449] [Server thread/INFO] [net.minecraft.server.players.PlayerList/]: kuba26039[/37.7.174.132:53667] logged in with entity id 71 at (-7.5, 110.0, 5.5)

Client side also says connected.

Quote

[14Oct2022 20:44:39.460] [Netty Client IO #1/INFO] [net.minecraftforge.network.NetworkHooks/]: Connected to a modded server.

But then there is a network timeout 1 minute later on the server.

Quote

[14Oct2022 20:45:40.516] [Server thread/INFO] [net.minecraft.server.network.ServerGamePacketListenerImpl/]: kuba26039 lost connection: Timed out

This seems to be from the keep alive ping not getting a response from the client.

 

I don't see any DEBUG messages for the mojang/minecraft code on either the client or server.

Did you set that property I mentioned above?

 

I also think you should try it with a fresh world on the server.

Besides the errors you deleted from the server log, there are messages saying the world cannot be loaded properly.

Quote

14Oct2022 20:38:25.454] [Server thread/ERROR] [net.minecraft.world.level.chunk.storage.ChunkSerializer/]: Recoverable errors when loading section [-4, 19, 22]: (Unknown registry key in ResourceKey[minecraft:root / minecraft:worldgen/biome]: biomesoplenty:scrubland -> using default)

Removing worldgen mods like biomesoplenty from a world that uses them generally doesn't work well.

[TheKuba]

well, sorry for that and also the late response. i think i added the argument you gave me now to the list, so here they are, now fixed:

server latest.log: https://pastebin.com/Kz3SFMha

server debug.log: https://pastebin.com/b6H8EY6N

client latest.log: https://pastebin.com/hsSYGj9p

client debug.log: https://pastebin.com/bs0zR2v6

[warjort]

You have a different error in the server log now. It just says disconnected instead of timeout.

The randomness of these different networking errors suggests there could be something wrong with your network card or internet connection.

Do you have a way to test using a different connection method? e.g. tethering to your phone or using a friend's internet.

 

I still don't see any vanilla debug messages? Here's some more information:

For the client it depends which launcher you are using. For the vanilla launcher:

Launcher -> Installations -> Edit the Forge Profile you are using -> More Options -> Add the Argument to the JVM Arguments

For curseforge there is an "Additional Arguments" in the minecraft settings.

For the server you put it in the user_jvm_args.txt

[TheKuba]

i have no clue why that happens, from what you told me i think there's some issue with something in my server and then there's  my not-so-good internet interfering from time to time. with what you found, do you have any idea what the issue might be?

[warjort]

Unfortunately not.

The errors seem to be different each time but all network related. This is why I want you test using a different network/device.

And Mojang's logging for networking (including errors) is mostly at DEBUG level so unless you change that system property mentioned above, I can't see it.

[TheKuba]

i know this isn't really your problem, so i need to say that you helping me means a lot.  i enabled the debugging on the client at last, so it might be a lot more helpfull:

https://drive.google.com/file/d/15wvcy-xRgTpxwAkGuLMMfNiSn0A-kzC4/view

i did four attempts: two with my home internet and two with my phone's data router or whatever it's called. miraculously, the net 2 attempt has resulted in a stable connection with the server, so we might learn something from that one. if you'd like, i can also ask a friend to join the server and share his logs

[warjort]

Please upload the files to a proper file sharing site.

It won't let me open those files on google and when I try to download the whole zip file it says it is not a valid zip file.

[warjort]

Quote

 two with my home internet and two with my phone's data router

Can you give more details on how these connections work. e.g. are they both wireless or is one or both using cables

If both are wireless you are not really testing anything different since it might be your wireless card that has the problem.

 

Also, does your friend see the same problem? If they do, this could mean the problem is server side.

[TheKuba]

my friend has no such issues, he can play normally on the server. but i do know one person who has the same issue as me, so i'll try to get their logs as well.

the first two are using an ethernet cable with the router, the second two use a wireless connection.

and sorry for the file problem: https://drive.google.com/drive/folders/1N3aYiCWzTtrFUHTboG7j1eau_v9eVpty?usp=sharing

[warjort]

There is little new information in those logs except all the failed ones timeouts about 1 minute after logging in.

Quote

[15Oct2022 15:59:57.089] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: kuba26039 joined the game

[15Oct2022 16:00:51.625] [Server thread/INFO] [net.minecraft.server.network.ServerGamePacketListenerImpl/]: kuba26039 lost connection: Timed out

Which means the server closes the connection.

Quote

[15Oct2022 16:00:51.060] [Netty Client IO #1/DEBUG] [net.minecraft.network.Connection/]: Failed to sent packet
java.net.SocketException: Connection reset
    at sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:394) ~[?:?]
    at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:426) ~[?:?]

 

The one difference I can see between net2 (which worked) and the others is the net2 client log is doing stuff like processing sounds

while the 3 that fail all have no logging for 30 seconds or longer before you get disconnected. e.g. from net1

Quote

[15Oct2022 16:00:19.840] [Render thread/DEBUG] [net.minecraft.client.sounds.SoundEngine/SOUNDS]: Removed channel net.minecraft.client.sounds.ChannelAccess$ChannelHandle@6f5869b because it's not playing anymore

 

-- 30 seconds of nothing here --

[15Oct2022 16:00:50.932] [Render thread/INFO] [net.minecraft.advancements.AdvancementList/]: Loaded 0 advancements

 

One obvious candidate when I see this kind of thing is very long "stop the world" garbage collections done by java.

How much memory do you have allocated to minecraft compared with your total system memory?

If you open up TaskManager, do you see it doing lots of "paging" and/or memory being close to 100% usage after you connect to the server?