System Information
Field
Value
Operating System
Linux - Ubuntu 24.04 on x86_64
Product
AMP ‘Callisto’ v2.5.1.0 (Mainline)
Virtualization
None
Application
Garry’s Mod
Module
GenericModule
Running in Container
No
Current State
Starting
Problem Description
Issue
Still Isn’t Starting Please Help
Reproduction Steps
Restarted The Server
Restarted the Instanace
Attempted to Upgrade Everything
@CubeCoders-Bot could you take a look at this please? Have them check their logs, make sure the selected map is valid, etc. You might want to look up the config for gmod.
Alright, let’s get this Garry’s Mod server up and running. Let’s start by checking the logs to see if they give us any hints.
Go to your AMP web interface.
Right-click on the Garry’s Mod instance.
Select “View Logs”.
Copy and paste the logs here as text so I can take a look.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Says too big file so makes hard.
Just the end of the log after you attempt to start the server. Copy the text rather than attaching a file.
Alright, no worries. Just copy the last 20-30 lines from the log after the server start attempt and paste them here. That should be enough to get a clue on what’s going wrong.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
[22:33:32] [RCON Error/15] : Source RCON failed to connect:
Connection refused.
[22:33:32] [RCON Debug/15] : Source RCON connecting to 172.17.0.1:27015…
[22:33:33] [RCON Error/4] : Source RCON failed to connect:
Connection refused.
[22:33:33] [RCON Debug/4] : Source RCON connecting to 172.17.0.1:27015…
[22:33:37] [RCON Error/15] : Source RCON failed to connect:
Connection refused.
[22:33:37] [RCON Debug/15] : Source RCON connecting to 172.17.0.1:27015…
[22:33:38] [RCON Error/5] : Source RCON failed to connect:
Connection refused.
[22:33:38] [RCON Debug/5] : Source RCON connecting to 172.17.0.1:27015…
[22:33:42] [RCON Error/19] : Source RCON failed to connect:
Connection refused.
[22:33:42] [RCON Debug/19] : Source RCON connecting to 172.17.0.1:27015…
[22:33:43] [RCON Error/15] : Source RCON failed to connect:
Connection refused.
[22:33:43] [RCON Debug/15] : Source RCON connecting to 172.17.0.1:27015…
[22:33:47] [RCON Error/18] : Source RCON failed to connect:
Connection refused.
[22:33:47] [RCON Debug/18] : Source RCON connecting to 172.17.0.1:27015…
[22:33:48] [RCON Error/4] : Source RCON failed to connect:
Connection refused.
[22:33:48] [RCON Debug/4] : Source RCON connecting to 172.17.0.1:27015…
[22:33:52] [RCON Error/7] : Source RCON failed to connect:
Connection refused.
[22:33:52] [RCON Debug/7] : Source RCON connecting to 172.17.0.1:27015…
[22:33:53] [RCON Error/11] : Source RCON failed to connect:
Connection refused.
[22:33:53] [RCON Debug/11] : Source RCON connecting to 172.17.0.1:27015…
[22:33:57] [RCON Error/16] : Source RCON failed to connect:
Connection refused.
[22:33:57] [RCON Debug/16] : Source RCON connecting to 172.17.0.1:27015…
[22:33:58] [RCON Error/16] : Source RCON failed to connect:
Connection refused.
[22:33:58] [RCON Debug/16] : Source RCON connecting to 172.17.0.1:27015…
[22:34:02] [RCON Error/4] : Source RCON failed to connect:
Connection refused.
[22:34:02] [RCON Debug/4] : Source RCON connecting to 172.17.0.1:27015…
[22:34:03] [RCON Error/11] : Source RCON failed to connect:
Connection refused.
[22:34:03] [RCON Debug/11] : Source RCON connecting to 172.17.0.1:27015…
[22:34:07] [RCON Error/16] : Source RCON failed to connect:
Connection refused.
[22:34:08] [RCON Error/5] : Source RCON failed to connect:
Network subsystem is down.
Alright, it looks like your RCON connections are failing—big time.
First things first, let’s check if the RCON port is correctly set up. You’ll want to:
Head to the AMP web interface.
Use the Search box (top right) to look for “RCON”.
Make sure the RCON port is correctly set to 27015
and double-check the password you’ve set.
Give that a shot and let me know how it goes!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
@CubeCoders-Bot RCON will fall over repeatedly if the server process isn’t starting. A bad map value could cause this. AMP will need to be put in debug mode to get more info.
Alright, let’s dive deeper with debug mode. It’s like turning on the lights when you’re trying to find your keys in the dark. Here’s how you do it:
Open your AMP web interface.
Go to your Garry’s Mod instance.
Use the Search box (top right) to find “Debug”.
Enable debug mode for the instance.
Once you’ve done that, start the server again and check the logs for any juicy details. Post the logs here as text, and we’ll figure it out!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Map was issue, thanks. Fixed.
system
Closed
20 2024 23:32
13
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.