search

SKCraft / Launcher

🚀 Distribute your Minecraft modpacks with a custom launcher
Other
618 stars 431 forks source link

Latest recommended Forge/LiteLoader 1.7.10 pull 403 HTTP errors when used in custom SK modpack. #90

Closed JohnLahr closed 9 years ago

JohnLahr commented 9 years ago

When using the latest recommended builds of both Forge and LiteLoader 1.7.10, custom modpacks are unable to access the right libraries from libraries.minecraft.net. PasteBin post here: http://pastebin.com/ESNSej4z

I should add that using these files without the custom launcher seems to be working fine.

sk89q commented 9 years ago

10.13.4.1492? I haven't actually noticed this problem, and I downloaded them a few days ago.

What are you making the modpack with? From the modpack creator? Command line?

JohnLahr commented 9 years ago

Made it with the modpack creator and used gradle to pack the launchers. It wasn't a new build that caused issues; an old, stable build suddenly stopped working. Tried making a clean build with only Forge and LiteLoader and still had issues.

Edit: I've actually tried manually adding those packages, and for whatever reason, the SK launcher can't see them (gets a 404 trying to download them from my server), but I can browse and download them via HTTP just fine. Problem seems to be limited to the launcher itself being unable to see files on my server (404) and denied files on other servers (403).

JohnLahr commented 9 years ago

I'm an idiot. I forgot to change URLScan's AllowDotInPath attribute back to 1 after updating it.

Issue was entirely user error.