As title said, i tried multiple version of Gitea and Gogs: latest to send webhook to Drone:1.0.0-rc.2
and got a Response 500
{"message":"Post : unsupported protocol scheme \"\""}
So i downgrade to Drone: 1.0.0-rc.1 which does not have this issue.
I am also having this issue the drone log says:
drone-server_1 | {“commit”:“5e7db71fb893fdc86e71250dd6315ac5324724f2”,“error”:“Post : unsupported protocol scheme “””,“event”:“push”,“level”:“warning”,“msg”:“trigger: cannot find yaml”,“ref”:“refs/heads/master”,“repo”:“user/repo”,“time”:“2018-12-09T20:59:55Z”}
make sure you pull the very latest drone/drone:1.0.0-rc.2
I can confirm that this issue is reproducible on 1.0.0.rc2. i reported this same issue at Drone 1.0.0rc2 installation troubleshooting.
This is pretty reproducible. @bradrydzewski have you been able to reproduce it? I have been able to run the drone container locally with ngrok and found the exact same problem.
Sorry, I am unable to reproduce. I just ran a test a few minutes ago and can confirm Gogs (0.11.79.1211) was able to process the webhook without issue, and successfully triggered a build. There are also a number of individuals in our gitter running rc.2 with Gogs and Gitea without issue. So it would appear to be something related to your configuration or environment …
@arca1n I noticed that you had DRONE_TLS_AUTOCERT=true even through Drone is behind a reverse proxy. This field should be disabled and could impact inbound http traffic. I recommend disabling.
Could this be something related to bitbucket?
