Connectivity Problem with Minecraft - Players cant connect to Minecraft server

Technical Support
, , ,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Phobos’ v2.6.4.0 (Mainline)
Virtualization Docker
Application Minecraft
Module MinecraftModule
Running in Container Yes
Current State Ready

Problem Description

Issue

Whenever I launch my minecraft server on AMP players cant connect. They receive the message: “Authentication servers are down. Please try again later.” The server console shows the same message. The console also shows “Failed to request yggdrasil public key” amongst other connection errors.

Firewall dump shows the ports as open. Server is listening on the status page.

When I ssh into the server and run ‘getamp update’ the server is fine afterwards, people can connect and the console shows no errors. But on first startup it never works. This is annoying because I am using the server on demand, aka, when someone wants to play, then I launch the server, it isn’t running 24/7.

Updating the instances through the control panel does not work. It has to be the ‘getamp update’ ran on root.

Now my question are:
Is this expected behaviour and is it necessary to run the update everytime? (do note it also happens if the server is only off for say an hour)
Is it possible to run the update as soon as the server boots?
Has anyone ran into this before and knows of a solution for it?

Thanks in advance for taking the time to read this and hopefully respond. Much appreciated! If you need any more information let me know.

Reproduction Steps

  • Installed headless Debian to run as a server
  • Installed AMP according to the instructions
  • Assigned a dedicated IP to the server and allowed port forwarding on 25565
  • Checked firewall settings, necessary ports are excluded and server is listening
2

Try and stop+start the MC instance from the main panel and see if that resolves things.
If not, try switching the MC instance’s Startup mode setting to Do nothing, then stop+start the MC instance.
If that also doesn’t work, try disabling docker and see if that gives you the same result.

Then if none of those work, it may be a networking or DNS issue on your end.

(Ah, just realized you also sent a message in Discord)