Failed to login to remote instance/Cannot manage this instance

  • 1K Views
  • Last Post 22 April 2019
Eizock posted this 21 April 2019

Problem: I have 2 LXC Containers, one with a ADS-Controller and one with a ADS-Target. If I create a new instance (Tried GarrysMod and Minecraft Java Edition) on the Target (via the Webinterface of the Controller), I cant manage the new instance.


If I try it via the Webinterface of the Controller it says:

"Failed to login to remote instance. Invalid Username or password"

The console of the Controller says:

21.04.2019 20:13:59: Anonymous
20:13:59 Authentication attempt for user admin@8a596ef4-6d7b-4f87-946e-5257ee02ca37@834f3965-c015-4be4-9ffc-f2061ca4b620 from 10.20.20.1
20:14:00 Authentication failure for user admin@8a596ef4-6d7b-4f87-946e-5257ee02ca37@834f3965-c015-4be4-9ffc-f2061ca4b620 from 10.20.20.1 - No such user

The console of the Target says:

21.04.2019 20:13:58: Anonymous
20:13:58 Authentication attempt for user admin@8a596ef4-6d7b-4f87-946e-5257ee02ca37 from 10.20.20.1
20:14:00 Authentication failure for user admin@8a596ef4-6d7b-4f87-946e-5257ee02ca37 from 10.20.20.1 - Failure

If I try it via the Webinterface of the Target it says:

"Cannot manage this instance. ADS failed to provide a login token."

The console of the Controller says nothing.

The console of the Target says:

21.04.2019 20:24:23: admin
20:24:23 Managed remote instance srcds01 at http://127.0.0.1:8081/

OS Name/Version: Debian GNU/Linux 9 (stretch)

Product Name/Version: AMP Release "Hawking Starman" v1.7.4.1, built 11/04/2019 13:12

Steps to reproduce:

  • Create 2 LXC Containers
  • Install AMPInstancemanager into both of them (without suggests)
  • Create a "ADS-Master" as a Controller in first LXC Container (IP: 10.20.10.30/16)
  • Set it up via the firstrun-wizard in the Webinterface
  • Create a "ADS-Minecraft" as a Target in second LXC Container (IP: 10.20.20.1/16)
  • Connect it to the "ADS-Master" via the firstrun-wizard in the Webinterface
  • Create a Instance from the Controller or Create a Instance from the Target or Create a Instance from the CLI of the Controller or Create a Instance from the CLI of the Target
  • Try managing it

Expected behaviour:

  • The Instance is manageable via the Webinterface of the Controller or Webinterface of the Target

Actions taken to resolve so far:

  • Checked Firewalls: All Disabled
  • Updated the System to the latest Version
  • Confirmed that the two Containers can communicate ('wget' the AMP-Webinterface of eachother)
  • Create the Instance via the Webinterface of the Controller
  • Create the Instance via the CLI of the Controller
  • Create the Instance via the Webinterface of the Target
  • Create the Instance via the CLI of the Target
  • Recreate the whole thing multiple Times to confirm that the Usernames/Passwords are Correct/Identical

Any Help is appreciated.

Order By: Standard | Newest | Votes
Mike posted this 22 April 2019

What is the auth server URL set to for the instance you're trying to manage?

Eizock posted this 22 April 2019

By Default its set to the local ADS-Target. But I also tried manually setting it to the ADS-Master, but it threw another error.

Mike posted this 22 April 2019

It should be set to whatever is acting as the controller, what error did you get?

Eizock posted this 22 April 2019

Where should I set it? in the AMPConfig.conf or in the instances.json? Or Both?

Mike posted this 22 April 2019

AMPConfig.conf

Eizock posted this 22 April 2019

OK, I set it in both to the ADS-Master.

From the ADS-Master I'm now able to manage the Instance.

But not from the ADS-Target. I'm still getting the Error

"Cannot manage this instance. ADS failed to provide a login token."

Eizock posted this 22 April 2019

Ok I reverted the setting in the instances.json. It has the same "error".

Eizock posted this 22 April 2019

What relevance have the "DeploymentArgs" in the "instances.json"? Are they only getting used on the first setup?

Mike posted this 22 April 2019

Correct. For any that are network related (IP/port bindings) it's also how ADS keeps track of them.

Eizock posted this 22 April 2019

So should I make sure that they are set correctly after the first setup?

Or should I just make sure that the AMPConfig.conf has the right values? (This is easy via the "New Instace Defaults" and "Default auth server" setting)

Close