GDLauncher
GDLauncher copied to clipboard
gorilla-devs
Updating modpack stuck at downloading mods 0%
Describe the bug Sometimes when updating modpacks, it becomes stuck at downloading mods 0 percent
To Reproduce Steps to reproduce the behavior:
-
Go to update a modpack to a newer version (happened on multiple modpacks)
-
Stuck at 0 percent downloading mods
Expected behavior For the Modpack to start updating and downloading the mods
Possible solutions Some ideas of how you would solve this issue, if possible
Screenshots
Operating System:
- OS: [e.g. Windows]
- 10
- Java Version: 8 and 17
- Minecraft Version: 1.16.5 and 1.18.1
- Mod Loader: both forge and fabric
Additional context Add any other context about the problem here.
I seem to be having the same issue as of now. Just updated AllTheMods 6 from 1.8.15 to 1.8.16.
https://i.imgur.com/RfVbyiy.png
Both seem to be Issuers with the GDLauncher api throwing code 400 and 504, failing the download.
Some form of check should be made to be sure that when a file fails to download, it starts over. And (if not already implemented) maybe even compare file checksums to make sure nothing got corrupted.
Best you can do for now is retry the update (maybe even backup the instance to be safe) a few times until it works?
I also get 400 / 504 when trying to dowload any mods (valhesia vanilla wnhansed)
Failed to load resource: the server responded with a status of 400 ()
instrument.ts:130 Error: Request failed with status code 400
at t.exports (createError.js:16)
at t.exports (settle.js:17)
at XMLHttpRequest.d.onreadystatechange (xhr.js:62)
at XMLHttpRequest.n (helpers.ts:88)
(anonymous) @ instrument.ts:130
addons-ecs.forgesvc.net/api/v2/addon/495693/file/3550299:1 Failed to load resource: the server responded with a status of 504 ()
createError.js:16 Uncaught (in promise) Error: Request failed with status code 504
at t.exports (createError.js:16)
at t.exports (settle.js:17)
at XMLHttpRequest.d.onreadystatechange (xhr.js:62)
at XMLHttpRequest.n (helpers.ts:88)
I'm having the same issue,on try download or repair the modpack Odyssey 2,some others modpacks have the same issues here but the lasted is Odyssey 2, i put the full log in the attachment -1642002972698.log
This seems to be more of a Curseforge issue, sadly. wonder if it's to do with the switch to Overwolf and the new mod policy...
Also getting this issue on multiple clients (ATLauncher as well), oddly MultiMC is fine. I did notice going to the URLs failing via Curl does work but takes a good 5 to sometimes 10 seconds and wondering if it is a really small timeout set on the clients. I also could be paranoid but could also be CurseForge silently dropping GDLauncher and ATLauncher requests
It happens very frequently too and takes many many tries to update a modpack :/
This seems to be more of a Curseforge issue, sadly. wonder if it's to do with the switch to Overwolf and the new mod policy...
This is exactly what I get from the console as well.
Same symptoms. Recommended workaround: provide a way to cancel an install/update (potentially rolling back the modpack to the previous state - if there's any - by doing update in temp folder and replacing folders later) For 504 codes, if it appears, sleep a thread for a while, then re-try the download again. I'm pretty sure it could be a badly implemented throttling mechanism.
Still getting this on the TNP 5 pack for 1.18.1
My Log: https://pastebin.com/4K5a15Nn
Still not working. I really hope this is on the top priority right now. Friends can't join my server as they are not able to download ANY modpack atm. All packs get stuck to 0%
I just use curseforge as an alternative at this point as it can take more than 10 attempts to redownload a modpack
I just use curseforge as an alternative at this point as it can take more than 10 attempts to redownload a modpack
Yeah, that wasn't even enough for my friends. +20 tries and not working. Used multimc to download and copied all the mods and configs to GD launcher folder and now it works.
Yeah, I did the CurseForge route as well and copied my instances over...sheesh...please fix.
I self-deployed the launcher from the master branch and I have absolutely no problems at all.
I self-deployed the launcher from the master branch and I have absolutely no problems at all.
looking at the recent commits it seems like they are fixing it hope a beta or something comes out soon..
I self-deployed the launcher from the master branch and I have absolutely no problems at all.
looking at the recent commits it seems like they are fixing it hope a beta or something comes out soon..
You can download a build from the master branch here at the bottom.
Ok thank you this https://github.com/gorilla-devs/GDLauncher/suites/5107500519/artifacts/152971137 works well
it was all working fine yesterday until this morning more 504 errors even in the latest master branch build lol
https://paste-bin.xyz/36592 also the whole thing is not working even cant search mods
Had a similar error except it self-resolved... ironically, at the same time I opened this github page. Same 400 error in the logs.
Anyone try hitting cancel when it says error can't connect on this message? I did, and it deleted all of my saved games and backups...
Has anyone found a fix for this temporarily? I haven't had a single successful installation yet. Been trying "multiple times"
Edit: GDLauncher installed today with latest binary
I am getting the same issue. Worked fine a couple days ago with the official release, then that stopped working so I downloaded the build linked in this thread, that hasn't worked for me... any updates on where this is at?
As a note in case it matters, I have tried both downloading directly within the launcher as well as downloading a zip from curseforge's website and then importing that into the launcher but neither have worked.
@GooberMcNugget @jkwphysics use the gdlauncher beta for now because the beta use the new curseforge api
