Startup Issue with Minecraft - getsockopt error on startup

System Information

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

Problem Description

Issue

Hello! I have done all steps above. One fix I attempted was disabling the firewall for the server but this has not fixed the issue. Thank you for your assistance!

Reproduction Steps

  • Run the fresh server as normal with no plugins or changes made
  • Copy the primary endpoint and put it into my minecraft direct connection
  • Attempt to connect for a while before getting the error getsockopt

Try the IP of the VPS instead of the domain that Hostinger gave you

I tried to use the IP as well as the IP with the port after it but neither worked.

The IP in the format of #.#.#.# and not something.website.com ?

Yes. I did just the ip itself (#.#.#.#) and then #.#.#.#:port
Edit: I did just notice while looking at the port info that the only port thats responding is the webserver port. I did update my instance yesterday but it didn’t seem to fix anything.

You can use a status checker like this one to see if it’s just an issue with your connection, or the server itself: https://mcsrvstat.us/

It said “could not connect to server.” I also had several friends try every version of the ip I sent previously, including the endpoint they provided.

Double check that it’s the same IP, or also try the domain that Hostinger gave you if you haven’t already.
And I would suggest checking that you’re using the right port and didn’t accidentally make a typo (been there)

I double checked and tried all the ips and domains again. I also tried to use the port thats marked as “listening” with the ips and domains but it also did not work. Currently, the SFTP port and the Game Port are not listening. The Webserver Port is listening.

The server is running and not sleeping or anything right?

Yep, I’ve restarted it several times at this point.

Check the server’s firewall in the Linux command line maybe, see if that looks fine (Hostinger should have some guides regarding firewalls and such)

Ah. I managed to skip a major step in the server setup. Thank you for all your help.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.