Credentials getting mangled in environment variables

[zilchms]

Hey,
I am running in a bit of an issue when I try to start my dockercontainer with FOUNDRY_USERNAME and FOUNDRY_PASSWORD set.
I have rechecked several times if I made mistakes during setup or while copy-pasting the username and password.
I have searched through old issues and discussions, but nothing seems to match.
Unfortunately the container only offers "Unable to log in as 'redacted', verify your credentials..." as explanation. Is there a way to debug this better?
I have tried curl-ing foundry, this works. I have not yet been able to find the right URL to send a curl with the logindata.

[felddy]

If you could start the container with CONTAINER_VERBOSE set to true and post the redacted logs it would be helpful.

[zilchms]

foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [debug] Timezone set to: UTC
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [info] Starting felddy/foundryvtt container v11.305.0
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [debug] CONTAINER_VERBOSE set.  Debug logging enabled.
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [debug] Running as: uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [debug] Environment: CONTAINER_PRESERVE_CONFIG=false
foundry_1  | CONTAINER_VERBOSE=true
foundry_1  | FOUNDRY_HOME=/home/foundry
foundry_1  | FOUNDRY_HOSTNAME="redacted-url"
foundry_1  | FOUNDRY_PASSWORD=[REDACTED]
foundry_1  | FOUNDRY_PROXY_SSL=true
foundry_1  | FOUNDRY_USERNAME='redacted-email'
foundry_1  | FOUNDRY_VERSION=11.305
foundry_1  | HOME=/root
foundry_1  | HOSTNAME=localhost
foundry_1  | NODE_VERSION=18.16.1
foundry_1  | PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
foundry_1  | PWD=/home/foundry
foundry_1  | SHLVL=1
foundry_1  | YARN_VERSION=1.22.19
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [info] No Foundry Virtual Tabletop installation detected.
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [info] Using FOUNDRY_USERNAME and FOUNDRY_PASSWORD to authenticate.
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [info] No Foundry Virtual Tabletop installation detected.
foundry_1  | Entrypoint | 2023-07-09 19:05:07 | [info] Using FOUNDRY_USERNAME and FOUNDRY_PASSWORD to authenticate.
foundry_1  | Authenticate | 2023-07-09 19:05:07 | [debug] Saving cookies to: cookiejar.json
foundry_1  | Authenticate | 2023-07-09 19:05:07 | [info] Requesting CSRF tokens from https://foundryvtt.com
foundry_1  | Authenticate | 2023-07-09 19:05:07 | [debug] Fetching: https://foundryvtt.com
foundry_1  | Authenticate | 2023-07-09 19:05:08 | [info] Logging in as: 'redacted-email'
foundry_1  | Authenticate | 2023-07-09 19:05:08 | [debug] Fetching: https://foundryvtt.com/auth/login/
foundry_1  | Authenticate | 2023-07-09 19:05:10 | [error] Unable to log in as 'redacted-email', verify your credentials...
foundry_1  | Authenticate | 2023-07-09 19:05:10 | [error] Unable to authenticate: Unable to log in as 'redacted-email', verify your credentials...

[felddy]

Could you include the head of the logs too please? It is important to see the version of the container and possibly the environment variables that you are using.

[zilchms]

I edited it in :)

[felddy]

Thanks for updating the logs. I don't see anything out of the ordinary. My best guess is that you may have an escaping issue with your password or username values. Let's try authenticating manually from within the container:

Open a shell in the container:

docker run --rm --interactive --tty --entrypoint /bin/sh felddy/foundryvtt:release

Then run the following command with your username and password:

/home/foundry # ./authenticate.js --log-level=debug <username> <password> /tmp/cookiejar.json

You should see output like this:

/home/foundry # ./authenticate.js --log-level=debug <username> <password> /tmp/cookiejar.json
Authenticate | 2023-07-10 14:45:30 | [debug] Saving cookies to: /tmp/cookiejar.json
Authenticate | 2023-07-10 14:45:30 | [info] Requesting CSRF tokens from https://foundryvtt.com
Authenticate | 2023-07-10 14:45:30 | [debug] Fetching: https://foundryvtt.com
Authenticate | 2023-07-10 14:45:31 | [info] Logging in as: <username>
Authenticate | 2023-07-10 14:45:31 | [debug] Fetching: https://foundryvtt.com/auth/login/
Authenticate | 2023-07-10 14:45:32 | [debug] Community URL: /community/<username>
Authenticate | 2023-07-10 14:45:32 | [info] Successfully logged in as: <username>

The success or failure of this test should help us narrow down the cause.

Also, how are you starting the container? e.g.; command line, docker compose, etc...

[felddy]

It's good to see the authentication tool works correctly inside the container. That means that the value from your docker-compose file is getting mangled between your keyboard and the tool.

My best guess still is that your password has some characters in it that need escaping in the yaml. Take a look at your use of single and double quotes in the environment variable section. Unless there are "special" characters you can omit the quotes.

Another thing you can try is passing your credentials using secrets.

See:

• https://stackoverflow.com/questions/19109912/yaml-do-i-need-quotes-for-strings-in-yaml
• https://github.com/felddy/foundryvtt-docker#using-secrets

[zilchms]

Turns out: single quoting either the password or the username in the docker-compose file mangled them, as I was only using upper and lowercase letters...
Thanks for the help!

[zilchms]

I am using docker-compose.

/home/foundry # ./authenticate.js --log-level=debug 'redacted-email' 'redacted-password'
 /tmp/cookiejar.json
Authenticate | 2023-07-11 05:50:19 | [debug] Saving cookies to: /tmp/cookiejar.json
Authenticate | 2023-07-11 05:50:19 | [info] Requesting CSRF tokens from https://foundryvtt.com
Authenticate | 2023-07-11 05:50:19 | [debug] Fetching: https://foundryvtt.com
Authenticate | 2023-07-11 05:50:20 | [info] Logging in as: redacted-email
Authenticate | 2023-07-11 05:50:20 | [debug] Fetching: https://foundryvtt.com/auth/login/
Authenticate | 2023-07-11 05:50:22 | [debug] Community URL: /community/redacted
Authenticate | 2023-07-11 05:50:22 | [info] Successfully logged in as: redacted

Thanks for the help btw :)

[zilchms]

Oh an just for completeness, here is the docker-compose file i am using.

---
version: "3.8"

services:
  foundry:
    restart: unless-stopped
    image: felddy/foundryvtt:release
    hostname: localhost
    init: true
    volumes:
      - type: bind
        source: /root/foundry/foundryvtt
        target: /data
    environment:
      - FOUNDRY_LICENSE_KEY='redacted-license'
      - FOUNDRY_USERNAME='redacted-email'
      - FOUNDRY_PASSWORD='redacted-password'
      - FOUNDRY_HOSTNAME="redacted-host"
      - FOUNDRY_PROXY_SSL=true

      - CONTAINER_PRESERVE_CONFIG=false
    ports:
      - target: 30000
        published: 30000
        protocol: tcp