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.

mysql_connect function does not exist, is mysql extension installed? []

After upgrading to PHP 7 or higher you may encounter the following error:

General Error
SQL ERROR [ mysql4 ]

mysql_connect function does not exist, is mysql extension installed? []

An sql error occurred while fetching this page. Please contact an administrator if this problem persists.

The reason for this is the mysql request is deprecated in the new version of PHP, as part of the security update to 7 from 5.6.40. All that needs to be done is to modify the configuration file and switch the configuration file from “mysql” to “mysqli” as the method for requesting the database.

Theme displays blank page after PHP upgrade

As many are aware, the hosting industry has been upgrading PHP to its latest version of 7.3.3 for additional security. Many of the original themes that have not been updated contain code that is only compatible with PHP 5.6.40.

This fix applies to RocketTheme WordPress Templates but may also apply to others as well. Part of the Rockettheme core contains RokCommon components. If you have recently upgraded from PHP 5.6.40 to PHP 7.* you may experience a blank page for WordPress after the upgrade.

The fix is to

  1. Download the latest RokCommon Core here: https://rockettheme.com/wordpress/plugins/rokutilities
  2. Once the zip file has been downloaded, unzip the file and locate the “wp_RokCommon” folder.
  3. Upload all of these files to your WordPress plugin directory located in: (Your WordPress Install Directory)\wp-content\plugins\wp_rokcommon\
  4. Overwrite the existing files. This will fix the incompatibility issue, when you refresh the site it should now be live and functioning on PHP 7.3.3.

Fix: No Sound / On-Board Sound disabled after installing new Video Card with HDMI

This was a frustrating error that I found numerous possible fixes to on-line on various forums which involved installing the latest nightly builds and completely flushing out my drivers and rebuilding them. None of this worked, which led to hours of frustration. Finally, I tried a very old fix that I used to use for Sound Blaster (dating myself here…) back in the 90’s to get the games Doom or DukeNukem to load properly.

This fix will require you to know a little bit about CMOS and BIOS and is designed to fix the HDMI on the video card from over-riding the onboard sound.

1. Boot up into your BIOS – This is usually the F1 / DEL / F2 Key on first starting the computer.

2. Locate the Advanced tab for your PCI card settings, you are looking for the Interrupt settings which will be a list of features with assigned “IRQ”‘s next to them. Every system has these.

3. Locate the HDMI Sound Interrupt – Regardless of the value for the IRQ, set it to disabled.

4. Once its disabled, Save the changes to BIOS and reboot. Once the system starts you should have your On-Board sound again.

The issue is occurring because it appears that the HDMI on the video card is grabbing the interrupt for the on-board sound system and overriding it on every start up. I have tested this on Windows 10 and Ubuntu 14.04, 16.04 and 18.04 for Nvidia brand cards. Once the above change was made everything works well.

Trimble device will not connect in Windows 10

Symptoms:  A Trimble device or similar rugged handheld device that was working fine with Windows 10 may suddenly stop working and no longer be able to connect to the computer. This is a known issue associated with the Windows 10 version 1703 (Creators Update) Build 15063.  On an attempt to sync the device the software will state that its unable to connect or just fail.

The credit here goes to Junipersys.com for identifying the fix for this frustrating error, the original can be found here: http://www.junipersys.com/Juniper-Systems-Rugged-Handheld-Computers/support/Knowledge-Base/Support-Knowledge-Base-Topics/Desktop-Connection-ActiveSync-or-Windows-Mobile-Device-Center/WMDC-in-Windows-10

The solution is a multi-step process:

  1. Ensure that .NET Framework 3.5 is fully installed under Control Panel > Programs > “Turn Windows features on or off”. Sometimes before being successful at installing WMDC, you must first manually enable the required .NET Framework 3.5 under “Turn Windows features on or off” and/or by using the previous dotNetFx35setup.exe installer from Microsoft. You may need to check the http and non-http additions to complete the install.
  2. Run the 64-bit drvupdate-amd64.exe or 32-bit drvupdate-x86.exe installer as an Admin and in “Compatibility Mode” for Windows Vista if WMDC and the required drivers do not successfully install automatically through the Windows Update service when you connect USB.  You can access compatibility mode by right clicking on the file, go to properties, and click the compatibility tab, “Run as Windows Vista”.  Also make sure that you run it as Administrator.   If you do not feel comfortable downloading the files from Junipersys.com you can obtain the files from Microsoft’s website by searching Windows WMDC.
  3. After install and once “Windows Mobile Device Center” appears in the list under the Start menu on the desktop PC, similar to as is automatically applied by our “WMDC-Helper.exe” utility referenced above, you WILL need to run command-prompt as an administrator to apply the following registry commands, and then perform a Restart.
    1. REG ADD HKLM\SYSTEM\CurrentControlSet\Services\RapiMgr /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
    2. REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WcesComm /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
  4. Reboot the machine and you should be able to connect your device and sync with the computer again!

Yoast SEO version 4.3 plugin conflicts with RocketTheme RokBox 2.50.7 on WordPress 4.7.2

The Yoast SEO version 4.3 plugin conflicts with RocketTheme’s RokBox 2.50.7 on WordPress 4.7.2

Updated: 3/14/2017


The Yoast SEO plugin installs without error and sets up correctly, however, when you go to use the “Readability” or “Analysis” features they do not respond.  Additionally, all posts will state that the Readability feature and the SEO are “Not Available”.

This is expected to occur in any WordPress site where a RocketTheme template is in use since the RokBox plugin is a standard feature in many of its available templates.


  • Disabling the RokBox plugin will allow Yoast SEO to work properly.


Troubleshooting Linksys LRT214 VPN Router Issues

Troubleshooting a Linksys LRT214:

I recently had to install a Linksys LRT214 Router, the install itself went well but there were a few issues along the way.   One thing I like about the LRT214 VPN Router is that it offers a full client to site VPN Tunnel using IPSEC.  The setup itself was extremely easy and only took a few minutes, the issues arose when the clients started trying to connect to the system as no error was given.

Issue #1:

The first issue was that I was not able to use the existing adapter in the shrew.net vpn client that Linksys recommends per their documentation.  Apparently, in some cases using the existing local adapter can cause the vpn tunnel to loop and therefore fail in establishing a connection.  The recommended setting is to use a virtual adapter and a random address that is outside the range of the network you are connecting too.

Issue #2:

The second issue was far more frustrating.  The tunnel would immediately enable without error but the client would not be able to reach any network resources except the switch itself…  In some cases some network resources would be available but not all.  The first telltale sign was in the logs:

Feb 7 20:07:27 2017    VPN Log    (grpips0)[130] … #248: [Tunnel Established] ISAKMP SA established
Feb 7 20:07:54 2017    VPN Log    (grpips0)[130] … [Tunnel Disconnected] instance with peer {isakmp=#0/ipsec=#0}

The tunnel is established and the ISAKMP SA is established, but nothing moves… Then the strange thing, one system was able to connect:

Feb 8 06:39:19 2017    VPN Log    (grpips0)[133] … #251: [Tunnel Established] ISAKMP SA established
Feb 8 06:39:23 2017    VPN Log    (grpips0)[133] … #252: [Tunnel Established] IPsec SA established {ESP=>0x06c8fd59 < 0xe0bb64ad NATOA=}

So why is one connection successfully completing the IPsec SA and the other is not?  The simple answer is its a result of the IP settings on the client network. For example, if the remote network is then the client must be on a separate network, they cannot be on the same subnet.  You can liken it to trying to send a letter from yourself to yourself, the post office will just leave it in your mailbox and it will never go anywhere.

Solution:  Break apart the subnets, regardless of the virtual adapter settings.

Client Network:  (Subnet is 192.168.3)

Server Network: 192:168.2.0 (Subnet is 192.168.2)

IPsec will work because when it tries to push the resources for now it won’t conflict with the clients internal network.

Do not have permission to delete file or folder – Windows 10

You do not have permission to delete a file or folder in Windows 10


You attempt to delete a file or folder on a Windows 10 drive and receive a permission denied error or that you must get permission from another user in order to delete that file.  Changing the permissions through the Advanced tab on security has no effect.



  1. Right Click on the folder and Select Properties, then click the “Security Tab” followed by “Advanced
  2. Change the Owner at the top of the Advanced Window to your Windows User Account located at C:\Users
  3. Check “Replace Owner on Subcontainers and objects”
  4. Click Apply, and then click OK two more times and exit the properties window.
  5. Once its applied, go back into properties again, “Security Tab” followed by “Advanced”
  6. Check the box at the bottom of the Window that says, “Replace all child object permission entries with inheritable permission entries from this object”.
  7. Click Apply again.
  8. Click OK two more times and exit the properties window.

You should now have access, this problem can occur from a variety of sources.  One example is when another user on the system creates a directory or file and places restrictions on that file or directory.  Only the security ID that it was created with can access that information unless a user with Administrative authority takes over that file or directory.  Another example is when a user re-installs the Windows operating system or attempts to copy old data from a former Windows install to a new hard drive.  Again, since windows is now a new installation, the security ID information will no longer match and the error will occur.

This error seems to be specific to Windows 7, Windows 8, and Windows 10.  It may occur in Windows Vista as well since that was the first version of Windows to have User Account Control (UAC) enabled in the file system.