Minecraft Server won’t start and returns an error in Linux

When you go to start Minecraft using “java -jar server.jar” or whatever you chose to name server.jar you receive the following error: “java.lang.UnsupportedClassVersionError: net/minecraft/bundler/Main has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

This is most likely caused by installing the “default-jre” in Linux instead of the one required by the server.jar file.

To fix this issue, install JDK 17 using the following steps:

sudo apt-get update
sudo apt-get install openjdk-17-jdk

Once the install is completed, run “java -jar server.jar” again, this time the Minecraft server should boot up correctly.

If this is the new install, you will receive “[13:56:37] [ServerMain/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.

If you list the directory where you tried to run the Minecraft server you will now see multiple files, run “sudo nano eula.txt

Modify the line that says “eula=FALSE” to “eula=TRUE” and use ctrl+o to save the file and ctrl+x to exit the nano editor.

If you run the server at this time it will load into the main shell window, if you want the server to run quietly in the background use the following command “java -jar server.jar &“. The ampersand will tell Linux to launch the program in to the background.

If you do not want any notifications the command is:

java -jar server.jar > /dev/null 2>&1

Happy Mining!

WordPress – Error: Could not connect to the server. Please verify the settings are correct.

When you attempt to run the WordPress core updates you receive the following error: “Error: Could not connect to the server. Please verify the settings are correct.”

Check and see if only two settings are available, “FTP” and “FTPS”. A more secure option is SSH2 which is supported by most Apache systems but this option is not visible in WordPress.

In order to add the SSH2 option, you will need to access the server shell and install “php-ssh2“. The command is “sudo apt install php-ssh2“.

Once php-ssh2 is installed, restart the Apache service using: “sudo systemctl restart apache2“.

Go back to WordPress and refresh the page, you should now see the below:

Enter your normal user credentials and select “SSH2” and click proceed. The update should now work as expected. You do not need to enter the authentication keys unless you set these up previously.

If it doesn’t and you receive “Could not create directory. Installation failed.” this means that your folder permissions are not set correctly for WordPress.

In order to fix the file and folder permissions use the following commands:

sudo find . -type f -exec chmod 664 {} +
sudo find . -type d -exec chmod 775 {} +
sudo chmod 660 wp-config.php

Some server configurations do not permit the wp-config.php file to be set to 660, it will result in the site becoming in accessible. If this is the case in your situation, change the permissions to 664 and this should resolve the issue (It adds the “read” permission back for guests).

WordPress Critical Error on Installation

During a WordPress installation, you receive a critical error after entering the database information and click next and the server is running PHP 8.0 or higher.

Example Error: “wpdb->query()\n#3 {main}\n thrown in /var/www/html/wp-includes/wp-db.php on line 2056”

In order to fix this error, open/edit setup-config.php. Its located in the /wp-admin/ directory.

Beneath the line that says, “define( ‘WP_SETUP_CONFIG’, true );” enter the following line: “@mysqli_report(MYSQLI_REPORT_OFF);”

Click the browser back button, verify your information again and then click next.

The installation will now succeed. This is a known bug issue that has since been patched, however, older templates may still result in this error.