Connectivity Problem with StarRupture - no connection possible

Technical Support
, ,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Phobos’ v2.6.5.0 (Mainline)
Virtualization Docker
Application StarRupture
Module GenericModule
Running in Container Yes
Current State Stopping

Problem Description

Issue

I can’t connect from the Game to the Server whatsoever. No Managing no joining. I tried sending tcp and udp packets from my windows pc to the server and I am able to recieve it with tcpdump.

Reproduction Steps

  • install the server
  • SStart the Server (new or saved game doesnt matter)
  • try to manage the server via ingame function
  • no connection
  • try joining the server
1 Like
2

Configure the server under Configuration>StarRupture

The server manager in-game is not used

You have to use your public IP to connect

3

More information: StarRupture Guide

4

Well if it makes you feel any better. I cannot even get this server up and running in AMP. When I “Create New Instance” > Choose Star Rupture. Give it a friendly name leave “start instance on boot” enabled and leave after creation set as “Update and Start Always” and click create instance (Like I do for all other servers); it creates the instance and “starts”. Then it immediately goes idle. When I attempt to click the manage server button I Gert the message “Cannot manage this instance - The specified instance is not running” and then practically a minute later the server goes offline. I have now tired on 3 different linux installs and 2 windows installs with AMP. This is the only server I cannot get up and running. I don’t know enough about code or underlying systems to diagnose any further. I am at the point I am going to pay GCode to run this server for me.

5

If you checked the logs of the instance you would likely find your answer

6

Best I can tell there are no errors in the deployment logs and for the instance log, the only error is “No valid AMP licence was found. Please open a shell as the ‘amp’ user and run ‘ampinstmgr reactivate #####01’ to reactivate this instance” yet my AMP license is just fine. AMP works just fine for all other games. I will attempt running the command when I get home.

7

upon running the command to reactivate the instance, I get the output of

[Info/1] AMP Instance Manager v2.6.5.2 built 28/01/2026 16:01
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Licence Key

When I enter my amp license I get the output of

[Error/1] No such instance matching name: ‘#####01’

(for clarification the instance has a name that is not #####01, I just put the hashtag/pound symbol to obscure the name of the server). The instance is there, but I just cannot start it. Is there another log I should be looking at?

8

You need to switch to the amp user first:

sudo su - amp

9

That was being entered as the amp user. Just to be sure I tired again and I logged out of amp into root and then back into amp and tried again. Same error message. I also attempted entering my amp license with and without the dashes (-) and it still gives the same error message. Any other ideas?

10

Run ampinstmgr status to check the list and the instance name (as the amp user)

11

1st and foremost I am sorry but we are getting much closer now that my idiotic memory lapse is out of the way. The simple stupid explanation is after running the status check, I was logged into the wrong mini pc.

(You can skip this paragraph - this is long winded version) I have 3 mini pc’s that were clustered via proxmox. They now run independently and I named them wrong. They were assigned static IPs ending in 21, 22, and 23 to correspond to the pc names AMP1 (21), AMP2 (22), and AMP3 (23) and the computers are labeled 1, 2, & 3. Apparently when setting them up independantly, I set pc1 as amp3, pc2 as amp 1, and pc3 as amp 1. I immediately realized it when I saw what instances were running. They were labeled for me as being on computer 1 but were actually on computer 3.

Now that is fixed and out of the way (I am sorry truly about that), attempting to run the reactivate command on the correct computer outputs this.

[Info/1] Checking licence key…

[Error/6] IM was unable to execute the requested command.

[Error/6] TimeoutException

[Error/6] [0] (TimeoutException) : The request channel timed out attempting to send after 00:00:30. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

[Error/6] at ServiceModel.Channels.RequestChannel.RequestAsync(Message message, TimeSpan timeout)

  • at ServiceModel.Channels.RequestChannel.RequestAsyncInternal(Message message, TimeSpan timeout)
  • at Runtime.TaskHelpers.ToApmEnd[TResult](IAsyncResult iar)
  • at ServiceModel.Channels.ServiceChannel.SendAsyncResult.FinishSend(IAsyncResult result, Boolean completedSynchronously)
  • at Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
  • at ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
  • at ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result)
  • at ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.b__0(IAsyncResult asyncResult)
  • at CubeCoders.LicencingClient.Licencing.GetLicenceInfo(String LicenceKey)
  • at InstanceManagerCLI.Core.ReactivateInstance(String InstanceName, String LicenceKey)
  • at InstanceManagerCLI.Core.ExecuteCommand(List1 Params, Dictionary2 Args

[Error/6] TimeoutException

[Error/6] [1] (TimeoutException) : The HTTP request to ‘https://auth.cubecoders.com/v2/service.svc’ has exceeded the allotted timeout of 00:00:30. The time allotted to this operation may have been a portion of a longer timeout.

[Error/6] at ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message, TimeoutHelper timeoutHelper)

  • at ServiceModel.Channels.RequestChannel.RequestAsync(Message message, TimeSpan timeout)