If you've never seen the error
Unable to access jarfile before in your Minecraft server's console here at Nodecraft, it can definitely cause some confusion. Thankfully, it's something that's really easy to figure out and fix!
This can be caused most often by one of two scenarios: Either the jar file is missing, or the jar file has a different name in the File Manager than what is set in your panel on the Java Settings page.
Let's take a look at an example of this happening. This server is looking for the jar file:
amnesia-1.1.0.jar. (We personally like to rename the forge jar files in the modpacks in our One Click Installer to keep track of the modpack name and what version they're on.)
Taking a look at the File Manager though, the jar file seems to be named
The fastest way to fix this is to go to the Java Settings page on your NodePanel, select the correct jar file, and Save the setting.
Alternatively, you can also rename the jar file to match what was is set in the NodePanel.
If you have a scenario where you don't see any Forge jar file in your File Manager, either by its normal name or renamed, then you'll need to either manually upload the Forge jar file or go to the One Click Installer and install the version you need for your server. Then, set the Panel to use the correct Forge jar file in the Java Settings like in the example above.
Your server should startup correctly now! If you do happen to see one of the modpacks in our One Click Installer behaving in a similar manner, please reach out to us in Support so we can take a look to fix it from happening again! https://app.nodecraft.com/support