I added another frpc IP node to the server, but encountered an error after connecting

[Ayan-520]

Bug description

log:https://mclo.gs/zkyBI9s

Steps to reproduce

Due to insufficient server bandwidth, I attempted to set up an additional frpc tunnel as a backup node for gameplay. However, after entering the IP address in the client and attempting to connect, an error occurred.

Expected behavior

join server

Actual behavior

error

Relevant logs

https://mclo.gs/zkyBI9s

Minecraft & Mod Loader versions

1.21.1neoforge

Minecraft launcher

No response

Operating system

win11

AutoModpack version

4.0.5

Other information

No response

Check list

• I have verified that the issue persists in the latest version of the mod.
• I have searched the existing issues and confirmed that this is not a duplicate.
• I have provided all the necessary information to reproduce the issue.
• I have verified that the issue does not occur without the AutoModpack - Ignore if you are reporting a mod conflict issue.

[Skidamek]

How exactly did you add it? probably it doesn't pass our handshake packets for whatever reason, likely not an automodpack issue

[Ayan-520]

[common]
server_addr = [ip]
server_port = 7000
tls_enable = false
user = admin
token = Token

[ayan_yy]
type = udp
local_ip = 192.168.2.60
local_port = 10101
remote_port = 10101

[ayan_mc]
type = tcp
local_ip = 192.168.2.60
local_port = 10100
remote_port = 23654
use_compression = true

[Ayan-520]

Network Architecture: We are using two servers on the same internal network. The primary server handles the computational load for the Minecraft server, while a smaller secondary server is responsible for hosting the backup IP and other minor services.

Connection Setup: Traffic is forwarded between them via the internal LAN.

Configuration Status: The internal network connectivity has been verified. Firewall settings have been checked and are correct, with the necessary ports open.

Key Constraint: Both hosts share and operate behind the same single public IP address.

[Skidamek]

Its configuration frp issue on your end, it worked for me flawlessly using latest version. Maybe you should update, you are using old config format

my conf:

frpc.toml

serverAddr = "127.0.0.1"
serverPort = 7000


[[proxies]]
name = "test-tcp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 25565
remotePort = 6000

frps.toml

bindPort = 7000

minecraft is running on 0.0.0.0:25565 and connecting via 0.0.0.0:6000

all set on the same machine

[Ayan-520]

Problem Summary:
After extensive testing, I found that none of the previous solutions worked. The key discovery is that directly connecting via the server's public IP address + port works perfectly, including the server's voice mod functionality when using dual ports. However, any attempt to connect using a domain name fails with the previously mentioned error. This failure occurs both with SRV records and simply using the domain name + port. The issue appears specifically when traffic is routed through the domain name.

Core Question:
Why does the connection fail when using a domain name, even though the IP + port works flawlessly? Is it a limitation of the mod not supporting dual domain access, or is there a misconfiguration in the DNS/FRP setup?

[Skidamek]

Automodpack works with domains and it doesn't matter from how many different IPs/domains you connect, it just should work. It's most likely misconfiguration in the DNS/FRP setup