OS Name/Version:
Product Name/Version:
Both are on Advanced
Controller: v2.6.0.12 | Debian Linux / aarch64 (Raspberry Pi 4)
Target: v2.6.0.12 | Debian Linux (Desktop)
Problem Description:
I already posted a similar version of this issue in another Tech support post, but because I can’t edit it anymore and there were a couple of changes and no one responded anyway, here is the updated version:
I want to connect the Target to the controller. As far as I know, I have to connect to the web interface of the Target for that. When trying to log in, I get the following error in the Web interface:
Authentication System Failure (code 100)
Reason: The auth server at http://192.168.2.1:8080/ is configured not to allow other instances to authenticate through it.
ADS01 of the Target is showing:
[13:35:34] [System Activity/9] : Authentication attempt for user joelsimon08 from 192.168.2.1
[13:35:34] [System Activity/10] : Authentication failure for user joelsimon08 from 192.168.2.1 - PassthruDisabled
While the ADS of the controller isn’t even showing a request or anything similar.
I already asked the discord support if anyone has an idea and Mike told me it could be a network issue, which is very possible. I can’t find any issue tho.
I use a special setup: The Controller (the Raspberry Pi) is directly connected to my home router, while the Target (gameserver) is connected to the Raspberry Pi via a USB 2.0 - Ethernet Adapter. I use this setup for something that isn’t very important right now, but I’d like to keep it that way if possible.
Maybe it’s also useful to mention that for the Raspberry Pi, eth0 is connected to the router while eth1 is connected to the Target. For the Target, it’s eno1 that is connected to the controller.
Target rules:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:2223 /* AMP:ADS01:FileManagerPlugin.SFTP.SFTPPortNumber */
ACCEPT udp -- anywhere anywhere udp dpt:12820 /* AMP:ADS01:ADSModule.Network.MetricsServerPort */
ACCEPT tcp -- anywhere anywhere tcp dpt:2225 /* AMP:ServerRafael01:FileManagerPlugin.SFTP.SFTPPortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:2226 /* AMP:BB601:FileManagerPlugin.SFTP.SFTPPortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:2227 /* AMP:Marc01:FileManagerPlugin.SFTP.SFTPPortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:2224 /* AMP:Minecraft01:FileManagerPlugin.SFTP.SFTPPortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:http-alt /* AMP:ADS01:Core.Webserver.Port */
ACCEPT tcp -- anywhere anywhere tcp dpt:8082 /* AMP:ServerRafael01:Core.Webserver.Port */
ACCEPT tcp -- anywhere anywhere tcp dpt:8083 /* AMP:BB601:Core.Webserver.Port */
ACCEPT tcp -- anywhere anywhere tcp dpt:8084 /* AMP:Marc01:Core.Webserver.Port */
ACCEPT tcp -- anywhere anywhere tcp dpt:tproxy /* AMP:Minecraft01:Core.Webserver.Port */
ACCEPT tcp -- anywhere anywhere tcp dpt:25565 /* AMP:ServerRafael01:MinecraftModule.Minecraft.PortNumber */
ACCEPT udp -- anywhere anywhere udp dpt:25565 /* AMP:ServerRafael01:MinecraftModule.Minecraft.PortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:25566 /* AMP:BB601:MinecraftModule.Minecraft.PortNumber */
ACCEPT udp -- anywhere anywhere udp dpt:25566 /* AMP:BB601:MinecraftModule.Minecraft.PortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:25569 /* AMP:Marc01:MinecraftModule.Minecraft.PortNumber */
ACCEPT udp -- anywhere anywhere udp dpt:25569 /* AMP:Marc01:MinecraftModule.Minecraft.PortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:25568 /* AMP:Minecraft01:MinecraftModule.Minecraft.PortNumber */
ACCEPT udp -- anywhere anywhere udp dpt:25568 /* AMP:Minecraft01:MinecraftModule.Minecraft.PortNumber */
ACCEPT tcp -- anywhere anywhere tcp dpt:http-alt
ACCEPT udp -- anywhere anywhere udp dpt:8080
Chain FORWARD (policy DROP)
target prot opt source destination
DOCKER-USER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere match-set docker-ext-bridges-v4 dst ctstate RELATED,ESTABLISHED
DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere
DOCKER all -- anywhere anywhere match-set docker-ext-bridges-v4 dst
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain DOCKER (1 references)
target prot opt source destination
DROP all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target prot opt source destination
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere
Chain DOCKER-USER (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
While the Controller rules are:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:2223 /* AMP:ADS01:FileManagerPlugin.SFTP.SFTPPortNumber */
ACCEPT udp -- anywhere anywhere udp dpt:12820 /* AMP:ADS01:ADSModule.Network.MetricsServerPort */
ACCEPT tcp -- anywhere anywhere tcp dpt:http-alt /* AMP:ADS01:Core.Webserver.Port */
I really don’t know how to continue and would like to get it run again xD
Steps to reproduce:
That is a really good question. I don’t even know how this happened. Everything started to break one after another (the whole setup worked great for a time long)
Actions taken to resolve so far:
- Completely reinstalled the ampinstmgr for the pi
- only re-running the setup
Hopefully someone is able to help 
EDIT:
Something just crossed my mind; When reinstalling amp on the PI, i logically had to make a new User. I used exactly the same name with also the same password. The controller still has the “original” user from the “old” controller with the same name / password. Could this be an issue?