[Bug] Unable to connect to server that uses AutoModpack (mc1.21.11-fabric-4.0.5)

[artnaxel]

Bug description

I am trying to set up AutoModpack on a Minecraft server running in Docker, using playit.gg as a tunneling service (Custom TCP tunnel). External clients CAN connect to the HTTP server (verified via external curl), but the server kicks the player immediately after joining. When configuring modpackHost and generateModpackOnStart to false or removing automodpack the player is connected to server successfully. Note: my bindPort, addressToSend, portToSend seems to be configured correctly.

Steps to reproduce

1. Set up AutoModpack behind a reverse proxy / tunnel.
2. Configure addressToSend and portToSend to the external tunnel address.
3. Connect with a client.
4. Result: The server attempts a self-check, fails to connect to its own external IP, throws "Host server error" in console, and disconnects the player.

Expected behavior

No error.

Actual behavior

Error.

Relevant logs

[20:37:51] [User Authenticator #1/INFO]: UUID of player artnaxel is ***
[20:37:51] [Server thread/INFO]: artnaxel has installed AutoModpack.
[20:37:51] [Server thread/INFO]: Sending artnaxel modpack host address: address:port]
[20:38:02] [Server thread/ERROR]: Host server error. AutoModpack host server is down or server is not configured correctly
[20:38:02] [Server thread/WARN]: Please check if AutoModpack host server (TCP) port '8080' is forwarded / opened correctly
[20:38:02] [Server thread/WARN]: Make sure that 'addressToSend' is correctly set in the config file!
[20:38:02] [Server thread/WARN]: It can be either an IP address or a domain pointing to your modpack host server.
[20:38:02] [Server thread/WARN]: If nothing works, try changing the 'bindPort' in the config file, then forward / open it and restart server
[20:38:02] [Server thread/WARN]: Note that some hosting providers may proxy this port internally and give you a different address and port to use. In this case, separate the given address with ':', and set the first part as 'addressToSend' and the second part as 'portToSend' in the config file.
[20:38:02] [Server thread/ERROR]: bindPort '8080' is different than portToSend '[port]'. If you are not using reverse proxy, match them! If you do use reverse proxy, make sure it is setup correctly.
[20:38:02] [Server thread/WARN]: Server certificate fingerprint: ***
[20:38:02] [Server thread/INFO]: artnaxel (/***) lost connection: [AutoModpack] Host server error. Please contact server administrator to check the server logs!

Minecraft & Mod Loader versions

1.21.11 fabric 0.18.4

Minecraft launcher

Official Minecraft Launcher

Operating system

MacOS

AutoModpack version

automodpack-mc1.21.11-fabric-4.0.5

Other information

docker-compose.yml

services:
  mc:
    image: itzg/minecraft-server
    container_name: mc-server
    ports:
      - "25565:25565"
      - "8080:8080"
    environment:
      EULA: "TRUE"
      VERSION: "1.21.11"
      PAUSE_WHEN_EMPTY_SECONDS: 0
      TYPE: "FABRIC"
      MEMORY: "6G"
      FABRIC_VERSION: "0.18.4"
      MODRINTH_DOWNLOAD_DEPENDENCIES: "required"
      MODRINTH_PROJECTS: |
        fabric-api
        lithium
        ferrite-core
        modernfix-mvus
        chunky
        ledger
        universal-graves
        automodpack
    volumes:
      - ./data:/data
    restart: unless-stopped

  playit:
    image: ghcr.io/playit-cloud/playit-agent:0.16
    container_name: playit-agent
    network_mode: "host"
    environment:
      - SECRET_KEY=***

    restart: unless-stopped
    depends_on:
      - mc

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]

Try using default automodpack config with a single simplest default playitgg Minecraft tunnel instead. Likely playitgg doesn't recognize and block our traffic on any other tunnels than the Minecraft ones.

[artnaxel]

I've tried it in the beggining because I thought it was problem with Minecraft tunnel and then set up the TCP tunnel and the issue remained. Both tried default config and configuring address/ports.

[Skidamek]

Can't reproduce, works fine on my end with default automodpack config (minecraft port is shared) I've ran your docker compose only using the 25565 port and setting playitgg as a minecraft java tunnel and everything works

Details

[artnaxel]

Changed it to minecraft tunnel, completely removed automodpack and added again with default config. Tried to connect, however it was stuck on this after certificate verification:

Tried to disconnect and connect again (after ~5 mins) and it started downloading mods, after restart everything works fine and I am able to connect to server with mods. I hope the issue is resolved, although is this behavior expected (when loading freezes on initial start)?

[Skidamek]

no?

[Skidamek]

Tried to connect, however it was stuck on this after certificate verification:

can you send client logs from when this happened?