Sign in to follow this  
Followers 1
spaceranger

Error starting 1.16.3-forge-34.1.0 client

By spaceranger, in Support & Bug Reports

Recommended Posts

spaceranger    0

spaceranger
Posted (edited)

Hello, first time trying out Forge on Ubuntu 18.04 based linux distro.

I've successfully installed minecraft-launcher for java and I can launch a stock minecraft 1.16.3 game as a client no problem.

I appear to have successfully installed 1.16.3-forge-34.1.0 in that I can see everything I'd expect to see under the /home/(myuseraccount)/.minecraft folder.

When I attempt to launch 1.16.3-forge-34.1.0 from minecraft-launcher, I get the following popup error:

  

Failed to start download.
Name: 1.16.3-forge-34.1.0.jar
URL: https://launcher.mojang.com/v1/objects/1321521b2caf934f7fc9665aab7e059a7b2bfcdf/client.jar
Error details: Permission denied
Couldn't open file for download
Filename on disk: 1.16.3-forge-34.1.0.jar
Path: /home/(myuseraccount)/.minecraft/versions/1.16.3-forge-34.1.0/1.16.3-forge-34.1.0.jar
Exists: Nonexistent

 

In the ./.minecraft/versions/1.16.3-forge-34.1.0 folder, I can only see a 1.16.3-forge-34.1.0.json and no other contents.

It appears that the forge installer placed the 1.16.3-forge-34.1.0.jar file in the following folder, along with the client and universal jar files:

 

./.minecraft//libraries/net/minecraftforge/forge/1.16.3-34.1.0

 

When I open the 1.16.3-forge-34.1.0.json file, it does include the following section that appears to define the correct path: 

    "libraries": [
        {
            "name": "net.minecraftforge:forge:1.16.3-34.1.0",
            "downloads": {
                "artifact": {
                    "path": "net/minecraftforge/forge/1.16.3-34.1.0/forge-1.16.3-34.1.0.jar",
                    "url": "",
                    "sha1": "0a6df450ccb26ad0fd119d5c6faaa4fb0cd889cf",
                    "size": 197523
                }
            }
        },

 

EDIT: I also noticed that the Forge related directories and files were installed beneath .minecraft with the owner as root:root (as I ran the install with sudo), but I ran chown recursively on those Forge directories and change the owner:group to my user account:my group.

There appear to perhaps be two errors here, permission denied either for the launcher.mojang.com error and then the Nonexistent for the jar file.

Can you please help me resolve this issue/these issues?

 

Thank you

Edited by spaceranger

Share this post

Link to post
Share on other sites

DaemonUmbra    531

DaemonUmbra
Posted

You didn't run anything as admin/sudo did you?

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://paste.gg/: 15MB

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.

 

Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch'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]

 

Share this post

Link to post
Share on other sites

spaceranger    0

spaceranger
Posted
31 minutes ago, DaemonUmbra said:

You didn't run anything as admin/sudo did you?

No, I run minecraft-launcher under my user account only, and did not alter any permissions or change/add/delete any files under /opt.

I only ran the forge installer under sudo and then chowned all of the files and directories under the /home/(myuser)/.minecraft folder, recursively.

Share this post

Link to post
Share on other sites

DaemonUmbra    531

DaemonUmbra
Posted

The only thing I can recommend is deleting the forge folder(s) in libraries and run the installer again under your user account

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://paste.gg/: 15MB

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.

 

Twitch Launcher: If you are using the Twitch Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Twitch'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]

 

Share this post

Link to post
Share on other sites

spaceranger    0

spaceranger
Posted

I'll give that a try, thank you.

Does it matter where I locate the forge installer jar file before I run it? I just have it sitting in /home/(myuser)/Downloads right now.

Share this post

Link to post
Share on other sites

spaceranger    0

spaceranger
Posted

I'll give that a try, thank you.

Does it matter where I locate the forge installer jar file before I run it? I just have it sitting in /home/(myuser)/Downloads right now.

 

EDIT: I'm stupid. I didn't chown everything, the json in the ./versions folder was still root:root. I finished _actually_ chowning everything to my user:my group and forge client started up just fine, it's downloading now.

Share this post

Link to post
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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  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.

×
Sign in to follow this  
Followers 1
Go To Topic Listing