Connectivity Problem with Minecraft - Cannot connect to server

System Information

Field Value
Operating System Linux - Debian GNU/Linux 11 on x86_64
Product AMP ‘Decadeus’ v2.4.6.10 (Mainline)
Virtualization QEMU_KVM
Application Minecraft
Module MinecraftModule
Running in Container No
Current State Ready

Problem Description

Issue

My users told me my Minecraft version was out of date and they thought that was why the couldn’t connect to play the game. I upgraded AMP and Minecraft by that didn’t help. The users still report an “unable to connect” error.

Reproduction Steps

  • Updated AMP
  • Updated Minecraft
  • Had numerous users try to access the server without success

Is this Bedrock or Java edition?

Bedrock. The server says it is running but users cannot connect. I’ve seen some connections have been refused because tokens were not issued.

Can you show me both what you see in the logs and what you see in-game when you try and connect?

When I try to connect within Minecraft, the error message I get is something like: "There was a problem connecting to the server. Try again or restart the server (both of which I tried). Where would I find the log you need?

Show me the exact message. Don’t paraphrase please.

The server logs will show in AMPs console.

I suspect that it may be similer to the issue i am seeing “[22:23:15] /AMP/./Minecraft/bedrock_server: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory”

The message is: “There was a problem connecting to the world. Please try again. If this error continues, check your internet connection or try restarting Minecraft. Unable to connect to world.”

The only thing in Console is: " :admin 17:25:31 Managed remote instance [SERVER NAME] at [SERVER IP] Authentication token for admin requested by ManageInstance on behalf of admin". I removed the server name and IP address in case these messages are public.

Try updating the instance - the docker images just got updated.

That’s the console in ADS, not the actual Minecraft instance. Manage the Minecraft instance and then show me.

I tried updating the instance but I am not sure it worked. As for the log, hopefully this is what you are looking for:
Application State: Services Running

:admin

17:25:31

Managed remote instance SpaceGuy123sServer01 at {IP ADDRESS]

Authentication token for admin requested by ManageInstance on behalf of admin

17:49:15

Managed remote instance SpaceGuy123sServer01 at [IP ADDRESS]

Authentication token for admin requested by ManageInstance on behalf of admin

17:50:28

Stopping instance SpaceGuy123sServer01…

Requesting soft-stop…

Waiting for instance to stop…

17:50:41

Managed remote instance SpaceGuy123sServer01 at [IP ADDRESS]

Authentication token for admin requested by ManageInstance on behalf of admin

17:50:42

LIM - Failure to make API call to SpaceGuy123sServer01: Connection refused

:admin

17:50:48

Soft-stop request was ignored after waiting for 20 seconds, force stopping…

17:50:58

SIGTERM failed after 10 seconds, killing process…

Instance SpaceGuy123sServer01 has stopped.

17:51:25

Waiting for AMP instance to start…

17:51:26

AMP instance SpaceGuy123sServer01 is now running.

Managed remote instance SpaceGuy123sServer01 at [IP ADDRESS]

Authentication token for admin requested by ManageInstance on behalf of admin

17:51:27

LIM - Failure to make API call to SpaceGuy123sServer01: Connection refused

:admin

17:51:39

Stopping instance SpaceGuy123sServer01…

Requesting soft-stop…

Waiting for instance to stop…

17:51:59

Soft-stop request was ignored after waiting for 20 seconds, force stopping…

17:52:09

SIGTERM failed after 10 seconds, killing process…

Instance SpaceGuy123sServer01 has stopped.

17:52:19

Upgrading instance SpaceGuy123sServer01

17:52:36

Waiting for AMP instance to start…

17:52:37

AMP instance SpaceGuy123sServer01 is now running.

Managed remote instance SpaceGuy123sServer01 at http://[IP ADDRESS]/

Authentication token for admin requested by ManageInstance on behalf of admin

17:52:37

LIM - Failure to make API call to SpaceGuy123sServer01: Connection refused

:admin

17:53:03

Upgrading instance SpaceGuy123sServer01

Again, you’re showing me the logs for ADS - not for the actual Minecraft instance.

I really don’t know where to find what you are asking for. I thought it might be within Minecraft so I started that, tried to connect to the server, then I went to the log. It showed there should be a log file but when I open the folder in the path (C:\Users\ben\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\logs), the log folder is empty.

Double click your Minecraft instance.


When I double-clicked the instance, this is what I see…

Is there any statement from Hostinger about this issue? I see 10 recent threads about this same issue. As far as I’m aware there still remains no fix, it’s been 3 days.

Trying to be patient, but with not even an acknowledgement of an issue I’m becoming frustrated. Are their developers working on a fix? It appears that the AMP is not correctly updating to the new MC Server.

People keep creating new posts about the same thing without searching, which is confusing the issue and slowing things down.

Restart the instance via the Support tab and then update the server.

I have tried what you suggested numerous times but that does not solve the problem.

Have you tried it since I said that? The last-resort fallback data was changed to try and address this.

@Mike Completed post your request - updated and restarted AMP instance. Restarted and updated Minecraft instance.

The log file (posted below) still shows that the AMP is unable to find the latest bedrock version and is reverting to 1.17 (Circa 2021).

The problem appears to remain the same

[20:08:50] [Logger Info] : Starting AMP version 2.4.6.10 (Decadeus), built 06/12/2023 17:17
[20:08:50] [Logger Info] : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[20:08:50] [Logger Info] : Running in a QEMU KVM environment.
[20:08:50] [Logger Info] : Purging old audit logs (this may take a moment)…
[20:08:50] [Logger Info] : OS: Linux / x86_64
[20:08:50] [Logger Info] : CPU: AMD EPYC 7543P 32-Core Processor (1C/1T)
[20:08:50] [Logger Info] : RAM: 3934MB
[20:08:50] [Logger Info] : AMP Instance ID: ecd9a384-30bd-43fd-b2a8-40ec2c446aa3
[20:08:51] [Logger Info] : Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited
[20:08:51] [Logger Info] : Metrics publishing is enabled at udp://193.203.164.239:12820.
[20:08:51] [Logger Info] : Loaded FileManagerPlugin by CubeCoders Limited
[20:08:51] [Logger Info] : Loaded EmailSenderPlugin by CubeCoders Limited
[20:08:51] [Logger Info] : Loaded WebRequestPlugin by CubeCoders Limited
[20:08:51] [Logger Info] : Loaded LocalFileBackupPlugin by CubeCoders Limited
[20:08:51] [Logger Info] : Loaded CommonCorePlugin by CubeCoders Limited
[20:08:51] [Logger Info] : Licence Present: AMP Enterprise Edition
[20:08:52] [Logger Notice] : Using keypair with fingerprint +ZqFQNvQgRjYTEmb6jgkNMWeaRIW8GYJCWRdTSi7Xe8=
[20:08:52] [Logger Info] : SFTP Server started on 193.203.164.239:2225
[20:08:52] [Webserver Info] : Websockets are enabled.
[20:08:52] [Logger Info] : RouterTimer@10Hz with 2 jobs started
[20:08:52] [Logger Info] : Webserver started on http://193.203.164.239:8082
[20:08:52] [Core Info] : Checking for AMP updates…
[20:08:52] [Logger Info] : Startup mode is UpdateAndStart.
[20:08:53] [Core Info] : AMP is up to date.
[20:08:55] [Logger Warning] : Unable to get Bedrock version data from https://www.minecraft.net/en-us/download/server/bedrock: Data not found.
[20:08:56] [Logger Info] : Modpack cache is up-to-date.
[20:09:00] NO LOG FILE! - setting up server logging…
[20:09:00] [INFO]: Starting Server
[20:09:00] [INFO]: Version 1.17.10.04
[20:09:00] [INFO]: Session ID f2b5a033-5c53-42a3-8216-632e47a86f27
[20:09:00] [INFO]: Level Name: world
[20:09:00] [INFO]: Game mode: 0 Survival
[20:09:00] [INFO]: Difficulty: 2 NORMAL
[20:09:00] [INFO]: opening worlds/world/db
[20:09:03] [INFO]: IPv4 supported, port: 19133
[20:09:03] [INFO]: IPv6 supported, port: 19134
[20:09:03] [INFO]: IPv4 supported, port: 19132
[20:09:03] [INFO]: IPv6 supported, port: 36385
[20:09:03] [INFO]: Server started.

1 Like