Friendbot always returning 502 Bad Gateway using Stellar Quickstart

[Juan Avero]

Hey 👋🏻 I'm running a stellar/quickstart image. I'm trying to fund an account using the friendbot on http://localhost:8000/friendbot?addr=G....... but I'm always getting a 502 Bad Gateway error. These are the only logs about friendbot that are on my logs. When I tried to fund the account, the logs with INFO exited: friendbot (exit status 1; not expected) were not there so I assume that the friendbot process was running at that time. Now it seems to fail to start the process.

If I go to http://localhost:8000 it works fine so I assume that must be a problem with the Friendbot only.

I tried with different tags (latest, testing (both linux/amd64 and linux/arm64) but it's not working neither.

Also tried invoking the method of the stellar-sdk await stellarServer.friendbot(publicKey).call();, instead of using Postman but it returns the same error message.

I'm using the following docker compose file:

version: '3'

services:
  stellar:
    image: stellar/quickstart:testing
    container_name: stellar-local
    command: --local
    ports:
      - '8000:8000'

Any help?

[github-actions]

This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed.

[Leigh McCulloch]

@jjuannn Could you share the full logs that you see on the terminal, as well as the logs from all the files found in this folder of the container? /var/log/supervisor/

[suhail]

friendly bot working fine for me.

$ curl http://localhost:8000/friendbot?addr=GB3SSRJE7CETRO3WZYBKMSIH2HT74LV5DZ64IWPEVSAODVP6C6EVORWP

i used this command to run the docker:

$ docker run -d -p "8000:8000" --name stellar stellar/quickstart --local

[Jane Wang]

@jjuannn Could you let us know if this issue has been resolved. Thank you :)

[Juan Avero]

Hey 👋🏻 Sorry I didn't get a notification for this thread.

We fixed our version to stellar/quickstart:v423-latest@sha256:0cf1ef247ae73d39c3503657f1fba27e2b6ae0b00b0bc0867ec497350ecf9998 and it started to work as expected. I don't know it was something related to the version that we were using.