Controller and Target setup - not able to manage instances from either server

  • 603 Views
  • Last Post 29 May 2020
  • Topic Is Solved
Morphikon posted this 27 May 2020

I have a single controller "be-ads" and a single target "be-amp-01" fresh installed on the 1.9.9.6 version yesterday.

I can log into the controller and see the target server with its instances, I can start and stop the instances from either server.

When I try to manage from the controller I get "The specified instance is not running" even though I can see it is green. When I try to manage from the target I get "ADS failed to provide a login token."

I've tried setting the auth server url on the instance to the be-ads https port and also to the http 8080 port, both do the same thing.

Order By: Standard | Newest | Votes
itzxtoast posted this 27 May 2020

I have the sampe problem. Freshly installed servers with one manager and one node for gameservers.

Mike posted this 27 May 2020

Check ampinstmgr status on each machine, and also triple check the logs for each instance. Chances are they'll tell you what's wrong.

Morphikon posted this 28 May 2020

Target:

[Info] AMP Instance Manager v1.9.9.6 built 19/05/2020 17:33 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV Instance Name │ Friendly Name │ Module │ IP │ Port │ Up ───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼─── ADS01 │ ADS01 │ ADS │ 0.0.0.0 │ 8080 │ ✓ Rust01 │ Rust01 │ Rust │ 0.0.0.0 │ 8081 │ Rust02 │ Rust02 │ Rust │ 0.0.0.0 │ 8082 │ ✓

Controller:

[Info] AMP Instance Manager v1.9.9.6 built 19/05/2020 17:33 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV Instance Name │ Friendly Name │ Module │ IP │ Port │ Up ───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼─── ADS01 │ ADS01 │ ADS │ 0.0.0.0 │ 8080 │ ✓

Nothing seems out of the ordinary?

Morphikon posted this 28 May 2020

Which log files should i be checking?

Also just confirming what the auth server address should be set to?

Is it https://hostname or http://hostname:8080?

Morphikon posted this 29 May 2020

Latest update 1.9.9.8 seemed to fix the issue.

No idea what was happening, nothing in any of the logs.

Close