POST results in "context deadline exceeded" [Please help]

Hello everyone.

I would really appreciate some help getting Drone running correctly.
I am using docker compose inside a GCP compute instance, but whenever I start drone & agent I get an endless stream of the following.
Please advise

drone-agent_1   | 2019/10/17 06:54:40 [ERR] POST http:// < IP >:8000/rpc/v1/request request failed: Post http:// < IP > :8000/rpc/v1/request: context deadline exceeded
drone-agent_1   | {"arch":"amd64","level":"debug","machine":"f0d6c7aa5bc9","msg":"runner: polling queue","os":"linux","time":"2019-10-17T06:54:40Z"}
drone-agent_1   | 2019/10/17 06:54:40 [DEBUG] POST http:// < IP > :8000/rpc/v1/request

Here is my config:

version: '3'

    image: drone/drone:1.2.1
    restart: always
      - /var/lib/drone:/var/lib/drone/
      - 8000:80
      - 9000:443
      - DRONE_SERVER_HOST=<IP>:8000
      - DRONE_RPC_SECRET=xxxx
      - DRONE_AUTOCERT=false
      - DRONE_OPEN=false
      - DRONE_ADMIN=jadechip
      - DRONE_PROVIDER="github"
      - DRONE_GITHUB=true

    image: drone/agent:1.2.1
    command: agent
    restart: always
      - drone-server
      - /var/run/docker.sock:/var/run/docker.sock
      - DRONE_LOGS_DEBUG=true
      - DRONE_LOGS_TRACE=true
      - DRONE_RPC_SERVER=http://<IP>:8000
      - DRONE_RPC_SECRET=xxxx

Thank you very much for your time!

My Github oAuth app has the following callback url: http:// < IP > :8000/authorize

But after authenticating via Github all I get is a blank page :woozy_face:
with the following message in the devtools console
Failed to load resource: the server responded with a status of 401 (Unauthorized)

The callback URL path is /login, not /authorize. See

Thank you Brad! Completely missed that change from version 0.8. I am finally able to login!
Still getting some status 542 context deadline exceeded errors but hopefully it won’t affect my pipeline.

you can expect to see context deadline exceeded in the logs:

The Agent uses long polling to request builds from the server queue. The agent connects to the server for up to 30 seconds. If the agent does not receive a build from the queue after 30 seconds, it terminates the connection and then reconnects. The connection is terminated after 30 seconds to prevent timeouts (from reverse proxies, load balancers, etc). It is therefore completely normal to see 524 status codes and context deadline exceeded errors in the trace logs.

Got it! Thanks! Really appreciate the support :muscle: