Drone url redirects to github page not found

Drone Support
1

Hi,

I am following the official drone documentation to setup a self hosted drone on an Azure Ubuntu 16.04 VM.

This is my docker-compose file:
version: ‘2’

services:
drone-server:
image: drone/drone

ports:
  - 80:8000
  - 9000:9000
volumes:
  - drone-server-data:/var/lib/drone/
restart: always
environment:
  - DRONE_OPEN=true
  - DRONE_DEBUG=true
  - DRONE_ADMIN=debottam
  - DRONE_HOST=${DRONE_HOST}
  - DRONE_GITHUB=true
  - DRONE_GITHUB_CLIENT=${DRONE_GITHUB_CLIENT}
  - DRONE_GITHUB_SECRET=${DRONE_GITHUB_SECRET}
  - DRONE_SECRET=${DRONE_SECRET}
  - DRONE_GITHUB_SKIP_VERIFY=true

drone-agent:
image: drone/agent:0.8

command: agent
restart: always
depends_on:
  - drone-server
volumes:
  - /var/run/docker.sock:/var/run/docker.sock
environment:
  - DRONE_SERVER=drone-server:9000
  - DRONE_SECRET=${DRONE_SECRET}
  - DRONE_GITHUB_SKIP_VERIFY=true

volumes:
drone-server-data:

Below is the last few lines of docker-compose up output when I try to access the drone url (<VMPublicIP:80>) -

drone-server_1 | time=“2018-10-03T06:47:09Z” level=debug msg=“agent connected: d60b92b055d0: polling”
drone-server_1 | time=“2018-10-03T06:48:45Z” level=info ip=106.51.30.111 latency=323.701µs method=GET path="/" status=200 time=“2018-10-03T06:48:45Z” user-agent=“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36”
drone-server_1 | time=“2018-10-03T06:48:46Z” level=info ip=106.51.30.111 latency=58.9µs method=GET path="/api/user/feed" status=401 time=“2018-10-03T06:48:46Z” user-agent=“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36”
drone-server_1 | time=“2018-10-03T06:48:46Z” level=debug msg=“user feed: connection opened”
drone-server_1 | time=“2018-10-03T06:48:46Z” level=info ip=106.51.30.111 latency=67.6µs method=GET path="/login" status=303 time=“2018-10-03T06:48:46Z” user-agent=“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36”
drone-server_1 | time=“2018-10-03T06:48:46Z” level=info ip=106.51.30.111 latency=327.101µs method=GET path="/authorize" status=303 time=“2018-10-03T06:48:46Z” user-agent=“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36”
drone-server_1 | time=“2018-10-03T06:48:47Z” level=debug msg=“user feed: connection closed”
drone-server_1 | time=“2018-10-03T06:48:47Z” level=info ip=106.51.30.111 latency=1.058752003s method=GET path="/stream/events" status=200 time=“2018-10-03T06:48:47Z” user-agent=“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36”

And, in the browser I am getting redirected to a 404 Github page which starts with “https://github.com/login/oauth/authorize?client_id=xxxx…”

Below is my docker version details:
Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:24:56 2018
OS/Arch: linux/amd64
Experimental: false

Server:
Engine:
Version: 18.06.1-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:23:21 2018
OS/Arch: linux/amd64
Experimental: false

I tried with both drone:0.8 and drone:latest.
DRONE_HOST=http://dronecicd, where “dronecicd” is the hostname of my VM.
Can anyone please help me out here, what am I missing? Thanks a lot in advance.

Regards,
Debottam

2

As I’m having troubles installing 1.3.1 (and also tried with 0.8) and nobody answered your question. Did you finally manage to get drone running or did you simply give up?.
I’d actually need any help setting up my instance.

Regards,
Michael

3

Michael, the root cause for this issue is an incorrect configuration. If I remember correctly it usually indicates a misconfigured or missing client secret. However, in order to help you triage installation issues we need to see your server configuration, github application configuration (screenshot), server logs, etc.

4

Thanks a lot for your response. I wasn’t actually expecting such a prompt answer :smiley:

In the meantime I actually got the server rinning now. Looks like main: source code management system not configured is triggered for nearly every configuration problem on server or agent.

That doesen’t make it easy to find the cause of an issue. After

  • finding some logging and tracing parameters,
  • comparing the trace output with the environment variables
  • comparing lots of obviously outdated tuts on other sites with the obviously changed parameters
  • and starting to dig tnto the source

I got the server running with GitHub and Gogs. In my case the main problem seems to have been a typo in the DB connection string. UI starts, I can finally log in. Everything looks fine so far.

But I still couldn’t figure out the problem with the agent. (Is that a synonym for runner or is there a difference?) Here is my docker-compose file. A hint would be highly appreciated! I hope the comments indicate the state of my trial and errors.

version: '3'

services:


  db:
    image: postgres:11.1-alpine
    restart: always
    environment:
      - POSTGRES_DB=${POSTGRES_DB}
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
    ports:
      - 5435:5432
    volumes:
      # Postgres data directory.
      - ./_pgdata:/var/lib/postgresql/data


  drone-server:
    image: drone/drone:1.3.1
    restart: always
    depends_on:
      - db
    ports:
      - 580:80
      # - 5443:443                                # proxy handles ssl
    volumes:
      - ./_dronedata:/data
      # - /var/run/docker.sock:/var/run/docker.sock     # What would this actually do? What if the runner is remote or even in Windows? 
    environment:
      # DB
      - DRONE_DATABASE_DRIVER=postgres
      - DRONE_DATABASE_DATASOURCE=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db/${POSTGRES_DB}?sslmode=disable
      - DRONE_DATABASE_SECRET=${DRONE_DATABASE_SECRET}  # encrypt secrets in DB (ATTENTION: don't change after setup)
      # Server
      - DRONE_OPEN=false                          # disable self registration of users
      - DRONE_SERVER_PROTO=https                  # external protocol (proxy handles ssl)
      - DRONE_SERVER_HOST=${DRONE_SERVER_HOST}    # external address used in webhooks and the like (not used for internal ops)
      - DRONE_TLS_AUTOCERT=false                  # disbale self enrolling a letsencrypt ssl certificate
      - DRONE_RPC_SECRET=${DRONE_RPC_SECRET}      # rpc secret (runners need that value to connect)
      - DRONE_DATADOG_ENABLED=false               # undocumented - and it should be as it sends data home
      - DRONE_AGENTS_ENABLED=false                # undocumented - guess it enables a local runner rather than allowing external ones to connect
      # Logging
      - DRONE_LOGS_TEXT=true                      # logging - text instead of JSON
      - DRONE_LOGS_PRETTY=true                    # logging - i guess this intends the parameters 
      - DRONE_LOGS_COLOR=true                     # logging - colorize message level (and param names for INFO)
      - DRONE_LOGS_DEBUG=true                     # set logging level to debug (deault: INFO, not shure how to set another level than those two)
      - DRONE_LOGS_TRACE=false                    # dumps internal configuratino
      # GOGS
      - DRONE_GOGS_SERVER=${DRONE_GOGS_SERVER}    # full url to Gogs server
      - DRONE_GOGS_SKIP_VERIFY=false              # verify SSL certificate
      - DRONE_GIT_ALWAYS_AUTH=true                # authenticate even if repo is public


  drone-agent:
    image: drone/drone:1.3.1
    restart: always
    depends_on: 
      - drone-server
    ports:
      - 3000:3000                                 # do I need that? What does it do?
    # command: agent                              # do I need that? # act as a runner (is agent and runner actually the same?) -> is this actually recognized? I have the feeling it's trying to runn as a server.
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock   # What would this actually do? What if the runner is remote or even in Windows? 
    environment:
      # - DRONE_RPC_SERVER=drone-server           # undocumented - this is read but I don't know the difference to DRONE_RPC_HOST
      # - DRONE_RPC_HOST=drone-server:580         # according to docs hostname and port without protocol. Not shure if this is correct -> I guess this is the reason, why the runner dowsen't work
      - DRONE_RPC_PROTO=https                     # protocoll http or https (default https)
      - DRONE_RPC_HOST=${DRONE_SERVER_HOST}       # according to docs hostname and port without protocol. Not shure if this is correct -> I guess this is the reason, why the runner dowsen't work
      - DRONE_RPC_SECRET=${DRONE_RPC_SECRET}      # use same value as configured on server
      # - DRONE_RPC_SKIP_VERIFY=false
      - DRONE_RUNNER_CAPACITY=2                   # number of jobs that can run in parallel on this runner
      - DRONE_RUNNER_NAME=h1-r1                   # undocumented - i guess this is used to indicate where a job ran 
      - DRONE_LOGS_TEXT=true                      # logging - same as on server (see above)
      - DRONE_LOGS_PRETTY=true
      - DRONE_LOGS_COLOR=true
      - DRONE_LOGS_DEBUG=true                     # error in docs? According to docs: DRONE_DEBUG (but this is the value that actually works, or i'm missunderstanding something)
      - DRONE_LOGS_TRACE=false                    # error in docs? According to docs: DRONE_TRACE (but this is the value that actually works, or i'm missunderstanding something)
      - DRONE_RPC_DUMP_HTTP=false                 # dump the http request and response to log. Enable to debug connectivity issues with server.
      - DRONE_RPC_DUMP_HTTP_BODY=false            # dump the http request and response body to log. Enable to debug connectivity issues with server.

The only message the runner logs is:

drone-agent_1   | FATA[0000] main: source code management system not configured
5

The problem with the agent is that there is no agent in your configuration :slight_smile: . It appears you have configured two server instance by mistake.

  drone-agent:
-   image: drone/drone:1.3.1
+   image: drone/agent:1.3.1
6

Of course! Thanks a lot! Usually if things seem too difficult you’re braking up the wrong tree :slight_smile: I guess (again) it was an outdated third party post, that confused me with it’s 'agent command.

But unfortunately I’m stuck again. Server and agent are starting without errors now, yeah. I can log into the drone site and see all my repos. So I tried to create a trivial pipeline: I added a repo for a simple dotnet core console app and added the .drone.yaml file. I can now activate the repo and the build triggers automatically. But the step ‘default’ it stays in pending state forever (or at least for 5 hours). I can cancel and restart it, no errors, no log entries (that I had found). Here’s the .drone.yml:

---
kind: pipeline
type: docker
name: default

steps:
- name: build
  image: mcr.microsoft.com/dotnet/core/sdk:2.2-alpine3.9
  commands:
  - dotnet build

...

So ok, maybe Microsoft is evil, or I fetched the wrong image. So I searched for a hello-world node repo and basically copied the .drone.yml from the docs:

kind: pipeline
name: default

steps:
- name: test
 image: node:12.9.1-alpine
 commands:
 - npm install
 - npm test

Same result, pending forever. And, yes,

  • I tried with and without the ---.
  • The image isn’t downloaded automatically, but when I pull it manually, docker run works fine.
    Only the drone step shows nothing but default: Pending.

What am I doing wrong? Or, even better, how I troubleshoot such a thing?

Thank you very much for getting me up and running!

7

see Builds are Stuck in Pending Status

8

Wow, you’re fast! Thanks, I’ll look into that.

That link would be great in the docs.

9

Thanks a lot for pointing me to that post. It was is very helpful to troubleshoot my issues. Both of the above samples worked perfectly now.

A link to that article would be a great help in a troubleshooting section of the docs.

And hey, … thank’s a lot for guiding me through my troubles setting up drone!

10

happy to help, and glad to hear you got it working! I do plan to move the troubleshooting guide to a faq in the docs. We just updated the docs last week and are in the process of adding content / copying content over from this forum.