JAR file not found, copying from global JAR directory

Each time I load up my fabric server I get this in my console

Table of Contents Show

Fixing Through FTP
Fixing With Server Settings
Repairing Server Installation

19.04 04:22:39 [Multicraft] Updating eula.txt file19.04 04:22:39 [Server] INFO Error: Unable to access jarfile /jar/custom_server.jar19.04 04:22:39 [Multicraft] Server shut down (starting)19.04 04:22:39 [Multicraft] Restarting crashed server in 5 seconds19.04 04:22:39 [Multicraft] Looks like a crash, check the server console. Return value: 119.04 04:22:39 [Multicraft] Server stopped19.04 04:22:44 [Multicraft] Loading server properties19.04 04:22:44 [Multicraft] Starting server!19.04 04:22:44 [Multicraft] Loaded config for "Custom Server JAR"19.04 04:22:44 [Multicraft] Failed to create local JAR directory19.04 04:22:44 [Multicraft] JAR file not found, copying from global JAR directory19.04 04:22:44 [Multicraft] Failed to copy jarfile from global JAR directory19.04 04:22:44 [Multicraft] JAR file not found. Go to "Settings"-"Update Minecraft" to download the JAR file.

Below is an example of a very common error that many clients get, but why do you see this error in your console? You receive this error because you have not deleted/cleared the modpack files from a previous modpack you were using before switching to a new modpack. To resolve the error below, you need to stop the server then delete all, if possible, or at least the mods folder and jars of the old modpack you were using from your FTP (Files -> FTP File Access).
[Multicraft] Loaded config for "Mod: Pixelmon (v4.2.7)"
[Multicraft] JAR file not found, copying from global JAR directory
[Multicraft] Failed to copy jarfile from global JAR directory
[Server] INFO Error: Unable to access jarfile /pixelmonLatest.jar
[Multicraft] Server shut down
[Multicraft] Looks like a crash, check the server console. Return value: 1

Last modified on Feb 14, 2022 in server errors

By ApexHosting

Facebook
Twitter
Youtube

Overview

Encountering the “Unable to access jarfile /jar/minecraft_server.jar” error occurs when the server panel is unable to locate the designated JAR File that has been set. This can occur if the file has an incorrect name or if the original file was deleted for any reason. This often occurs when attempting to set a custom server version on the panel using a custom JAR file. In order to fix this issue, renaming the JAR file or adjusting the server settings will be required to allow it to start properly. Rectifying this issue can be confusing for unfamiliar players, so we have created this Apex Hosting guide to ease you through the troubleshooting process.

Fixing Through FTP

Navigate to the Apex Server Panel, then stop the server.
Scroll down to the Game File section, then confirm the file name.
Proceed to the FTP File Access on the left, then log in.
Locate and enter the Jar folder.
Select and rename the .jar file to match the file name from earlier.
Submit the change once complete, then restart the server to try again.

Fixing With Server Settings

Navigate to the Apex Server Panel, then stop the server.
Proceed to the FTP File Access on the left-hand side.
Locate and enter the Jar folder.
Check the name of the jar file you wish to use.
Return to the main panel page, then scroll down to the Game File section.
Enter a new file name to match the FTP file, then save and reset.

Repairing Server Installation

If this issue occurs on a normal Minecraft version such as a modpack, it may be an issue with an update or if the file was deleted.

Navigate to the Apex Server Panel, then stop the server.
In the left-hand menu, locate and press the Reset Server Files button.
When prompted, check the Game File option.
Type in reset when prompted, then restart the server.

This will redownload the base files for the mod, including the jar file and any mods for the required version.

Conclusion

With that, you should now know how to adjust or repair the server settings in order to fix the “Unable to access jarfile” server error. This error may occur any time the used jar file is modified or deleted, so ensure that the above steps are taken in order to prevent the server from entering an error-loop. If you find that issues are still occuring after following the above troubleshooting solutions, feel free to visit our support page to receive additional help 24/7.