Slight Issue Regarding 1.18+ Instances

[Electrobob99]

Basically as the subject line states, I have a bit of an issue when it comes to any minecraft instance in 1.18 or newer version which use forge as the mod loader.
Where it would seem the session is almost always invalid, skin not showing up, unable to join servers, etc. Only happening when forge is installed, fabric and vanilla are unaffected which is weird.

Here is the current log to see if a solution can be found for these versions. Which I hope so, since it's kind of unnerving to play as Alex or Steve on Java.
https://controlc.com/e7f82cc1
 

I appreciate any help to get this resolved, thank you.
 

Edited December 11, 2022 by Electrobob99
Forgot to add the details of the issue

[ChampionAsh5357]

It seems like you are using reauth which is currently the only thing even close to erroring. Your report does not show there is an authentication issue.

[Electrobob99]

Okay then does this log show any potential reason this could be happening, removed reauth just in case.
https://controlc.com/b3559e32

This new log is for my mostly vanilla instance, only forge and a couple simple mods.

Something I did notice was forge failed to process update information, and that I am not the only one who has experienced this broken session bug in 1.18 and newer instances with forge. Seemingly around the same time in november of 2022.  Makes me think some windows update might have changed around some thing making code used to connect fail. Or something.
 

[ChampionAsh5357]

You can try running `ping authserver.mojang.com` and see if you get a response. I can't reproduce the issue with Windows, so I cannot say anything there. Otherwise you may need to check your proxy settings.

[Electrobob99]

Okay I decided to take your advice. 
I pinged the authserver.  To which I got an immediate response back, which does make sense since only some minecraft versions have this issue for me.
1.12.2 Works,  1.17 works, Older Versions work.  Unmodded/fabric for 1.18/1.19 work.
But forge for 1.18/1.19 "Invalid Session".
This has definitely not been a "just me" sort of issue, there is another person who posted here with the exact same issue.  Which I imagine there is a correlation, haven't tried a different computer on the same network like that guy did, but I would imagine it's the same.
All I can say is, it seems like while the access token is being properly given to forge, it's not being handed off to mojang, or mojang is just not accepting that access token from them. Like it expires before it can reach them.

I wonder if it has something problematic with using openjdk's java instead, it never caused this problem back in october.

[warjort]

Quote

[13:27:53] [main/INFO]: ModLauncher running: args [--username, Dr_NeonChrome, --version, 1.19.2, --gameDir, ..\..\instances\Minecraft vanilla, --assetsDir, ..\..\datastore\assets, --assetIndex, 1.19, --uuid, faef772dc7624e399b770c27284e00a8, --accessToken, ????????,

--clientId, ${clientid}, --xuid, ${auth_xuid},

--userType, mojang, --versionType, release, --launchTarget, forgeclient, --fml.forgeVersion, 43.2.0, --fml.mcVersion, 1.19.2, --fml.forgeGroup, net.minecraftforge, --

hmmmm

[Electrobob99]

21 hours ago, warjort said:

hmmmm

Uh, is that a good or a bad sign?

[warjort]

2 minutes ago, Electrobob99 said:

Uh, is that a good or a bad sign?

It's a sign that your launcher is not passing the correct authentication details to forge/minecraft.

That's usually the kind of thing cracked launchers do.

[Electrobob99]

On 12/15/2022 at 12:10 PM, warjort said:

It's a sign that your launcher is not passing the correct authentication details to forge/minecraft.

That's usually the kind of thing cracked launchers do.

That is weird, I've been using the GDLauncher for years it's never had this issue before.

[Electrobob99]

Okay so... Strange update with the issue....
After I switched the port I plugged my ethernet cable in the router to the other one, it managed to allow the session to work again...
Despite other instances working prior to that..
Weird, any ideas on why doing that would have fixed things?

*Seems to stop working if I ever exit the launcher again, but fixes anytime I switch the router port I plugged into*

Edited December 17, 2022 by Electrobob99

[Electrobob99]

Decided to update this post with a comparison Log, between the working instance with Fabric and the non-Working Instance with Forge.

Fabric: https://controlc.com/5d1cdebe

Forge: https://controlc.com/0b109358

Only thing I noticed was the presence of the "Connection Timed Out" error in the forge instance log.
Makes me wonder if Forge is being slower at sending data to Mojang, could there be a JVM argument that could be added in the launcher/instance to then give it more time to then test this theory?

[Electrobob99]

Okay thanks to an oversight, a long over looked one I FINALLY found out the cause.
So... Long story short.. ipv6...   
Someone posted about before.
Add the following to the JVM Arguments in the launcher you are using "-Djava.net.preferIPv4Stack=true".
Seems that after 1.18 Forge manages to use ipv6 by default if your PC has it enabled, but this argument can force your game's launcher to use IPv4 instead.
It squashed the problem instantly for me.