How to setup Minecraft server on Ubuntu 18.04 Bionic Beaver Linux -

The following article will describe a Minecraft server configuration procedure on Ubuntu 18.04 Bionic Beaver Linux. Let's start by installation of all prerequisites including the nmap command which we can later use for some basic troubleshooting purposes:
$ sudo apt update
$ sudo apt install wget screen default-jdk nmap 

This is a companion discussion topic for the original entry at


Poster Guy
How can I open the console for the server? Hopefully this is a quick and easy question. Thank you :slight_smile:


Flan OBrien

nmap -p 25565 localhost
Starting Nmap 7.70 ( ) at 2018-06-02 10:14 WITA
Nmap scan report for localhost (
Host is up (0.000087s latency).

25565/tcp closed minecraft

Thanks for the article.
Any idea why the STATE might be closed?



I followed the guide and got the server to start, but whenever I try to join it it says: Authentication Servers are down for maintenance. (This usually only happens when mojang’s servers are down) I found this weird because I could still connect to 5 different servers which meant I was the one with the problem. I also got my friend to try to connect and he said that the authentication server failing was also displayed on his screen. I have been able to get a server to work successfully in Kubuntu 17.04 and 17.10 but with 18.04 I am encountering this problem.

What I have found to allow me to access it is to set online-mode=false in; however, this does allow me to join but not my friend, and this leaves the server open for access by “pirate” versions of Minecraft according to what I have read as well as failing to load in player skins. Since 18.04 has been released recently I am not able to find information online to help, so I came here hoping I can find a response.


AndreEnderMC -> AndreEnderMC

So far the only work around that I have found is to use a virtual machine on an older version of Kubuntu to get it to work. I hope this gets fixed soon though, as I don’t really like the limitations this creates.


James Lex -> AndreEnderMC
Finally got mine running! Remove Java using the top answer from this link:

Then install Java 8 JDK:

sudo apt-get install openjdk-8-jdk

Started up the server again and it was working.


Lubos Rendek Mod -> James Lex

Hi James,

thank you for your input! Are you saying that the issue is with the open-jdk version. Your suggestion is that instead the default jdk version ( currently 11 ) and you suggest that Minecraft server only works properly with open-jdk 8?



James Lex -> Lubos Rendek

Yes, I believe that is what I’m saying. :stuck_out_tongue: I’m new to Ubuntu, so I’m not sure what version (or versions) of Java was installed by default.

I followed the instructions listed on this How To, and when it didn’t work, I checked my Java version (I think I used sudo java -version) and found I had both 8 and 11 installed. I tried removing only 11, but still had the Authentication issue.

Once I completely removed all versions of Java and ran the command listed in my previous comment, it worked fine.


Ben Povey -> AndreEnderMC

I’m having the same problem. all i could find that seemed relevant was this (https://www.minecraftforum....

but it didn’t work for me. I’m stuck. i have 2 separate minecraft server installs via different install methods. firewalls off, ports forwarded. tried running as root.

If i run a server on windows, everyone authenticates just fine.

My difference is i did have friends connect when in offline mode.


Usually you can do this by logging in as the user that is running the server. and then enter “screen -r”


FWIW, I have an ESXi 6.7 host in my garage and created a Ubuntu 18.04 Server build for the sole intent of running minecraft for my kids and their friends.

I followed various other tutorials, this one is the only one to use a system account for the user minecraft, which is why someone cannot "screen -r " to the instance. No biggie for me. I was having the external (internet) side kids get disconnected and timeouts after connecting for a few seconds. It turned out that my gateway VM wasn’t sending their packets through quick enough, so I had to put their minecraft port in bypass mode. Strange, since the physical box didn’t need that attention. Either way, it works and they’re happy. Cheers.