Issues trying to Setup Controller - Target

OS Name/Version: (Controller) Raspberry Pi headless [aarch64 / Debian GNU/Linux 12], (Target) Debian Linux [x86_64 / Debian GNU/Linux 12]

Product Name/Version: AMP Advanced Edition Version: (Controller) 2.6.0.6 | (Target) 2.6.0.10

Problem Description:
Hello, so I kinda have a lot of problems going on simultaneously, as you will see further on.

I did manage to connect the Controller and the Target, but when trying to manage an Instance via the web interface (of the controller), I get the following error:

Authentication passthru is disabled on the controller The auth server at http://localhost:8080/ is configured not to allow other instances to authenticate through it.

the ADS01 console of the controller is showing:

[10:45:54] [Core:joelsimon08 Activity/12] : Managed remote instance ServerRafael01 at http://192.168.1.144:8082/ [10:45:54] [ADS:joelsimon08 Activity/12] : Authentication token for joelsimon08 requested by ManageInstance on behalf of joelsimon08

The ADS of the Target doesn’t register anything.
As shown in the post of Action 1, someone said binding the auth server to localhost doesn’t work. I did change it to the local ip (http://192.168.1.136:8080/) but it still gave me the EXACT same error. Then i also tried https://brave.servegame.com/ which both work for the web interface, but it doesn’t seem like the auth server wants to. In conclusion, i have absolutely no clue what to do.

Steps to reproduce:
Honestly, I don’t know what or how much I did wrong when setting up. Everything worked for like 1-2h till I tried to do something with port mapping (map the things sent to the Target and give it to the controller) so I can put the Target Server to sleep if no one is playing on it (with a python script) and turn it back on if there is a packet (like 25565 for minecraft) going to the Target. If that is, the Controller sends a Magic Packet to the sleeping Target. At least that was the idea. (It did not work).

I have to say that I tried to disable the Port mapping again, and it still didn’t work, so it doesn’t seem like that is the cause.

There will be a lot of questions because of my poor explanation, but I really don’t know any further.

Actions taken to resolve so far:

Action 1:

Update
I reinstalled the whole amp system of the controller (with deleting the amp file / user) and the auth error is still happening

If the Target had pre-existing instances before you attached it, you need to run the following on the Target:
ampinstmgr repairauth target http://192.168.1.136:8080
(assuming they are both in the same private network)
And then double check that you have that same URL in the Target’s settings for the Default Auth Server

If things still act weird, your best bet is to read the logs, reinstalling doesn’t tend to help much.

You don’t know how much you just helped me

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.