Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

  • Authentication Failure Could not connect to the remote instance

Authentication Failure Could not connect to the remote instance

  • 413 Views
  • Last Post 19 December 2020
Philipp posted this 13 December 2020

Hi

I have two servers on which amp is installed. One is configured as a controller and the other as a target. The target server is running and there are no errors in the log.

The controller server cannot connect to the target server. The target server is listed under Instances and shows the following error:

Authentication Failure 
Could not connect to the remote instance at https://amp01.domain.com/. Timed Out Please check configuration".

The following entry appears in the log when the Refresh button is pressed:

[Auth:admin Activity] : Authentication token for AMP_SYSTEM requested by UpdateRemoteInstancesList on behalf of admin

Otherwise, the following entry appears in the log every minute:

[Auth Activity] : Authentication token for AMP_SYSTEM requested by UpdateRemoteInstancesList on behalf of admin

The two servers have already been rebuilt, but with the same result. The Login.AuthServerURL= is set correctly and has been checked multiple times.

OS Name/Version: Debian 10.6 Product Name/Version: AMP Release "Europe" v2.0.8.8, built 11/12/2020 18:05

Any Help is appreciated.

amp linux error problem help-needed
Order By: Standard | Newest | Votes
Mike posted this 14 December 2020

Check your firewall rules on the target.

Philipp posted this 19 December 2020

I had checked the firewall first, but without success.

In the meantime, however, I have found the error. In my case, the amp servers are installed directly with the Debian image. After the installation is complete, the server is restarted. This direct restart caused the error. If I install a delay, it works.

However, I now have new errors. If you create an instance and want to manage it via the "Manage" button, you get the following error message:

Cannot manage this instance
The specified instance is not running

If you try this on the target server, you get this error message:

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

I have already found an old article on this problem, but no explicit solution was found there.

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

Also, the binding port is not automatically released in the firewall. As soon as you have done this manually, you can manage the instance via "Manage in new tab". However, direct management still does not work. Only after restarting the controller instance via the support area does the Manage button work without problems.

Is there a better solution than manually releasing the corresponding port each time and restarting the controller instance?

Live Chat Register to post
Categories
Search
Popular Tags
This Weeks High Earners
Hot Topics
Close