regression when using the alternative-authentication mod

[not-fiore]

Describe the problem

i am runnning a server using the alternative authentication mod. this used to work fine, but now i cannot start my server anymore because it stops with an error from playerdb or mojang, saying that the requested account was not found. it seems that the container is checking the accounts instead of letting the minecraft server do it, and as such the mod is unable to direct the request towards ely.by?

this is just a guess, i am trying to fix this and really dont know what to do, i am desperate.

Container definition

version: "3"
services:
  server:
    image: ghcr.io/itzg/minecraft-server
    tty: true
    stdin_open: true
    restart: always
    ports:
      - "25565:25565"
      - "25575:25575"
    environment:
      VERSION: "1.21.6"
      MEMORY: "4G"
      DIFFICULTY: "hard"
      FORCE_GAMEMODE: "true"
      MODE: "survival"
      ENABLE_WHITELIST: "true"
      VIEW_DISTANCE: "20"
      ONLINE_MODE: "true"
      ENABLE_COMMAND_BLOCK: "true"
      OVERRIDE_WHITELIST: "true"
      SPAWN_PROTECTION: 0
      ALLOW_FLIGHT: "true"
      CUSTOM_SERVER_PROPERTIES: |
        enforce-secure-profile=false
      EULA: "TRUE"
      TYPE: "FABRIC"
      MODRINTH_DOWNLOAD_DEPENDENCIES: "required"
      MODRINTH_PROJECTS: |
        lithium
        chunky
        alternate-current
        netherportalfix
        villager-names-serilum
        dismount-entity
        zombie-horse-spawn
        skeleton-horse-spawn
        mooshroom-tweaks
        scaffolding-drops-nearby
        floodgate
        frostbytes-skip-server-movement-check
        ferrite-core
        discord-mc-chat:PtVawIb0
        death_coordinates
        universal-graves
        alternative-authentication
        no-chat-reports:G2i6IY0q
        disconnect-packet-fix
        fabric-custom-names
        luckperms
      DATAPACKS: |
        /data/datapacks-local/minecarts.zip
      VANILLATWEAKS_FILE: |
        /data/config/vt-datapacks.json
        /data/config/vt-crafting.json
        /data/config/vt-resource.json
      WHITELIST: |
        # lots of stuff here...
      RCON_CMD_STARTUP: |
        gamerule disableElytraMovementCheck true
        gamerule doInsomnia false
        gamerule doLimitedCrafting true
        gamerule playersSleepingPercentage 50
        spawnChunkRadius 1
        spawnRadius 1
    volumes:
      - /var/minecraft/cherrysmp/server/data:/data

Container logs

15:29:01.492 ERROR : Invalid parameter provided for 'manage-users' command: Could not resolve username from Mojang: $USERNAME

[itzg]

Since it errors with mention of

$USERNAME

Then you're doing something wrong with variable substitution.

I am not going to consider this a regression since that logic hasn't changed in over a year. When using WHITELIST the container has always been doing a lookup to manage the ops and whitelist files.

Leave off WHITELIST if you don't want the image startup to manage users.

[itzg]

FYI it is using Mojang's api at https://api.mojang.com/users/profiles/minecraft/{username}

[not-fiore]

i am sorry, i exposed this badly. $USERNAME is just my way of not typing out the exact username explicitly, since it seemed irrelevant

apart from that, then i suppose i might be mistaken in considering this a regression? but i am pretty sure this mod used to work up to a few months ago

[not-fiore]

is it then just not possible to keep the whitelist enabled if i want ely.by auth? i am genuinely curious as to why the container has to check the whitelist before the server itself has a chance to handle it?

[itzg]

Does the URL provided work for you?

Hmm, sounds like it's the mod's fault since you said that's the only thing that changed recently.

Most changes are a year or more old

https://github.com/itzg/docker-minecraft-server/blame/master/scripts/start-setupRbac

[itzg]

is it then just not possible to keep the whitelist enabled if i want ely.by auth? i am genuinely curious as to why the container has to check the whitelist before the server itself has a chance to handle it?

Remove WHITELIST variable if you don't like its behavior.

Perhaps manage the whitelist directly to comply with whatever that mod wants

[not-fiore]

Does the URL provided work for you?

Hmm, sounds like it's the mod's fault since you said that's the only thing that changed recently.

Most changes are a year or more old

https://github.com/itzg/docker-minecraft-server/blame/master/scripts/start-setupRbac

no the url will not work because the user does not exist on mojang's servers, but only on ely.by

[not-fiore]

is it then just not possible to keep the whitelist enabled if i want ely.by auth? i am genuinely curious as to why the container has to check the whitelist before the server itself has a chance to handle it?

Remove WHITELIST variable if you don't like its behavior.

Perhaps manage the whitelist directly to comply with whatever that mod wants

ok i will try, thanks

[itzg]

i am genuinely curious as to why the container has to check the whitelist before the server itself has a chance to handle it?

I don't have time or mental energy to walk you through the whole code. If you want whitelist.json to be managed by the image then use WHITELIST variable. If you don't, then don't.

Maybe set offline mode? 🤷‍♂️

[itzg]

no the url will not work because the user does not exist on mojang's servers, but only on ely.by

I refuse to support cracked Minecraft software which seems to be the only reason for this service. I'm sorry it used to work but doesn't now, but I am no longer going to reply to this issue.