Error logging in when using an account that does not have 2FA enabled yet #2

From the gatekeeper container I was able to access the pds, so they are on the same network (I used a different docker-compose than you did), here is what I did below:

services:
  pds:
    container_name: pds
    build:
      context: .
      dockerfile_inline: |
        FROM ghcr.io/bluesky-social/pds:latest
        RUN apk add bash curl openssl jq util-linux
        RUN curl --silent --show-error --fail --output "/usr/local/bin/pdsadmin" "https://raw.githubusercontent.com/bluesky-social/pds/main/pdsadmin.sh"
        RUN chmod +x /usr/local/bin/pdsadmin
    restart: unless-stopped
    volumes:
      - data:/pds
    env_file:
      - stack.env
    networks:
      - backbone

  gatekeeper:
    container_name: gatekeeper
    image: fatfingers23/pds_gatekeeper:latest
    restart: unless-stopped
    environment:
      PDS_BASE_URL: http://pds:3000
    #This gives the container to the access to the PDS folder. Source is the location on your server of that directory
    volumes:
      - data:/pds
    depends_on:
      - pds
    env_file:
      - stack.env
    networks:
      - backbone

volumes:
  data:

networks:
  backbone:
    external: true

And, I checked that I could reach it at that host from within the gatekeepr container with:

root@11688a9228b0:/# curl http://pds:3000/

         __                         __
        /\ \__                     /\ \__
    __  \ \ ,_\  _____   _ __   ___\ \ ,_\   ___
  /'__'\ \ \ \/ /\ '__'\/\''__\/ __'\ \ \/  / __'\
 /\ \L\.\_\ \ \_\ \ \L\ \ \ \//\ \L\ \ \ \_/\ \L\ \
 \ \__/.\_\\ \__\\ \ ,__/\ \_\\ \____/\ \__\ \____/
  \/__/\/_/ \/__/ \ \ \/  \/_/ \/___/  \/__/\/___/
                   \ \_\
                    \/_/


This is an AT Protocol Personal Data Server (aka, an atproto PDS)

Most API routes are under /xrpc/

      Code: https://github.com/bluesky-social/atproto
 Self-Host: https://github.com/bluesky-social/pds
  Protocol: https://atproto.com

Hmmm it looks to be all there. I did do a new release last night with some fixes and a little bit of logging may try and other docker compose pull and docker compose down and up. Altho that may not help since you prob just set it all up today.

Does gatekeeper have any logs? And did other non 2fa endpoints work? like sign in with 2fa?

Ah, I couldn't connect from the PDS container to the gatekeeper container. The default network interface of gatekeeper 127.0.0.1 (loopback), when usually in docker it is 0.0.0.0 (all interfaces) so that you can bind by hostname too.

So, this config works:

services:
  pds:
    container_name: pds
    build:
      context: .
      dockerfile_inline: |
        FROM ghcr.io/bluesky-social/pds:latest
        RUN apk add bash curl openssl jq util-linux
        RUN curl --silent --show-error --fail --output "/usr/local/bin/pdsadmin" "https://raw.githubusercontent.com/bluesky-social/pds/main/pdsadmin.sh"
        RUN chmod +x /usr/local/bin/pdsadmin
    restart: unless-stopped
    volumes:
      - data:/pds
    env_file:
      - stack.env
    networks:
      - backbone

  gatekeeper:
    container_name: gatekeeper
    image: fatfingers23/pds_gatekeeper:latest
    restart: unless-stopped
    environment:
      PDS_BASE_URL: http://pds:3000
      GATEKEEPER_HOST: 0.0.0.0
    #This gives the container to the access to the PDS folder. Source is the location on your server of that directory
    volumes:
      - data:/pds
    depends_on:
      - pds
    env_file:
      - stack.env
    networks:
      - backbone

volumes:
  data:

networks:
  backbone:
    external: true

Awesome! I'll leave this issue open to look into swapping that over

Writing a note for someone else to pick this up if they'd like to. This can be set at this line

https://tangled.org/@baileytownsend.dev/pds-gatekeeper/blob/main/src/main.rs#L262