Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Forge (1.13.2 / 25.0.219) Libraries failed to download help!

Vareq

By Vareq
in Support & Bug Reports

 Share

Recommended Posts

Vareq Tree Puncher

Vareq

Posted
Posted (edited)

Error: https://gyazo.com/1c588799c5ecb200d9ce30ec198caa05

 

Things I have tried:
- Updating Java

- Using '-Djava.net.preferIPv4Stack=true -jar forge-1.13.2-25.0.219-installer.jar' in command prompt in the correct directory

- Reinstalling Minecraft (deleting .minecraft folder included)

- Using another (slightly older) version of the 1.13.2 forge installer

- Allowing java through private network in firewall

 

4a524bab2913257077dbe0eb2ef8aab8.png

 

I have included the installer log because it seems useful for problem solvers.

What should I do? Please and thank you!

forge-1.13.2-25.0.219-installer.jar.log

Edited by Vareq
Link to comment
Share on other sites
Ian8705 Tree Puncher

Ian8705

Posted
Posted (edited)

I have tried doing the exact same things for 1.13.2. I have tried all of your solutions already. Right now, I am actively trying to find a solution to this problem and will tell you what I find if I do. I am able to run forge in already-installed forge profiles. When I get to the "Install Client" part, right at the end of downloading the following error appears (see attached). This error is not for just forge too by the way, it's the exact same thing for another mod loader (Rift), which also has a similar error installing.

 

Failed to download file. Rift-jitpack-SNAPSHOT.jar
Name: Rift-jitpack-SNAPSHOT.jar
URL: https://www.jitpack.io/com/github/Chocohead/Rift/jitpack-SNAPSHOT/Rift-jitpack-SNAPSHOT.jar
Error details: HTTP 404: 
Filename on disk: Rift-jitpack-SNAPSHOT.jar
Path: C:\Users\[My real name]\AppData\Roaming\.minecraft\libraries\com\github\Chocohead\Rift\jitpack-SNAPSHOT\Rift-jitpack-SNAPSHOT.jar
Exists: false

 

Whatever problem I'm having is also the same for a few people on forge 1.14.2. This does not explain why Rift doesn't work though. This error seems to be specifically for the version 1.13.2, as I managed to install forge for 1.12 just now.

Error.png

Edited by Ian8705
Link to comment
Share on other sites
Mythblood Tree Puncher

Mythblood

Posted
Posted

I had  this problem, and looking at the log file in the OP it has the same error I had about PKIX path build.

 

The issue is the ssl cert for the sites aren't in the jave keystore. I fixed it by following these steps

https://stackoverflow.com/questions/18378869/pkix-path-building-failed-in-java-application


If you don't want to use Open SSL to dl the root cert you can view the site


https://files.minecraftforge.net


in your browser. Click on the lock icon, and export the cert from there. Then import that into the java keystore using the steps in the SO answer (this is less secure than accepting the root cert obviously).

 

Anyway, after that everything downloaded just fine .. then I ran into other problems

Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

That was not the issue, the issue was that the Forge servers were only providing their own certificate when they needed to provide the whole chain of certificates leading back to the root certificate that is trusted. Please do not modify your Java security settings unless you know exactly what you are doing.

 

That being said the issue should be fixed now.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to comment
Share on other sites
Lava Smith Tree Puncher

Lava Smith

Posted
Posted
On ‎6‎/‎12‎/‎2019 at 7:59 PM, DaemonUmbra said:

That was not the issue, the issue was that the Forge servers were only providing their own certificate when they needed to provide the whole chain of certificates leading back to the root certificate that is trusted. Please do not modify your Java security settings unless you know exactly what you are doing.

 

That being said the issue should be fixed now.

 

Hi there,

 

I am still having this issue. I am not very clued up when it comes to Java coding etc, but I really want to just be able to play the game with world edit ran via Forge again. Is there a way I can solve this problem? I have gone ages without Forge as when the game updated it stopped working. I would rather have just stayed in 1.12 than have the update, but the problem is I can't run my worlds on 1.12 forge as it just crashes. I was just wondering if there was anything you could suggest? 

 

Many thanks :)

Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Please do not hijack threads, if you have an issue please make your own.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept