Alan Perrow

Thank you! I looked up ways to force ipv4 protocol for Java applications and ended up getting it to work by supplying the launcher with this jvm argument: -Djava.net.preferIPv4Stack=true

Hello, I started experiencing this crash a while back and have not been able to play with any recent Forge versions since. I would like to be as detailed as possible with this post as I spent quite some time iterating through Forge versions to find out where things stopped working for me. I managed to track the issue's introduction back to Minecraft 1.19, Forge 41.0.63. Previous to this version, Minecraft was able to run fine alongside Forge. To help demonstrate the issue, I disabled all mods besides Forge itself and ran the MultiMC launcher with several different Minecraft and Forge versions. I have attached all relevant logs below: MC: 1.19 Forge: 41.0.61 LWJGL: 3.3.1 This version works fine, a few errors as Minecraft is loading but still works. MC: 1.19 Forge: 41.0.62 LWJGL: 3.3.1 This version throws a few errors on load (maybe the same/similar errors as v41.0.61), but Minecraft still manages to open and run. MC: 1.19 Forge: 41.0.63 LWJGL: 3.3.1 This version fails on DOWNLOAD_MOJMAPS task; "Failed to run processor: java.net.ConnectException:Connection timed out: connect". All subsequent Forge versions (41.0.63 onwards) fail to start and crash with same error i.e.: MC 1.19, Forge 41.1.0 This includes newer MC versions as well i.e. with latest: MC 1.19.3, Forge 44.1.0 I of course investigated a multitude of similar forum posts before deciding to post this - none of them were able to be resolved from what I saw. In each post, someone mentioned posting a hosts file, so here is that as well to show that nothing is strange on my end: I hope this is able to get some traction and/or is able to be explained somehow! Thank you.