So just curious what is the “supported” way to configure SSL for Drone. I ask because I’m having timeouts between drone and maybe my NGINX reverse proxy. So goal is to run something “supported” so if I continue to have issues I can resonablely ask for help.
I ask because I’m having timeouts between drone and maybe my NGINX reverse proxy.
what sort of timeout issues are you seeing? Are these timeouts between drone + agent? I ask because we added the heartbeat which should be pinging the server every 30 seconds to keep the connection alive.
So goal is to run something “supported”
I definitely want to make sure drone works with nginx since it is so widely used, but I’m not an nginx expert by any means.
These are not timeouts between drone and the agent. This is some sort of issue with UI. Maybe it’s not a timeout…? Not 100% what is causing this but seeing things like:
Jan 9 13:50:22 drone docker/drone[8879]: #033[31m2017/01/09 13:50:22 [Recovery] panic recovered:
Jan 9 13:50:22 drone docker/drone[8879]: GET /api/user/feed?latest=true HTTP/1.1
Jan 9 13:50:22 drone docker/drone[8879]: Host: drone.company.com
Jan 9 13:50:22 drone docker/drone[8879]: Connection: close
Jan 9 13:50:22 drone docker/drone[8879]: Accept: */*
Jan 9 13:50:22 drone docker/drone[8879]: Accept-Encoding: gzip, deflate, sdch, br
Jan 9 13:50:22 drone docker/drone[8879]: Accept-Language: en-US,en;q=0.8
Jan 9 13:50:22 drone docker/drone[8879]: Connection: close
Jan 9 13:50:22 drone docker/drone[8879]: Cookie: ...
Jan 9 13:50:22 drone docker/drone[8879]: Referer: https://drone.company.com/
Jan 9 13:50:22 drone docker/drone[8879]: User-Agent: ...
Jan 9 13:50:22 drone docker/drone[8879]: X-Forwarded-For: ...
Jan 9 13:50:22 drone docker/drone[8879]: X-Forwarded-Proto: https
Jan 9 13:50:22 drone docker/drone[8879]: X-Real-Ip: ...
Jan 9 13:50:22 drone docker/drone[8879]:
Jan 9 13:50:22 drone docker/drone[8879]:
Jan 9 13:50:22 drone docker/drone[8879]: write tcp 172.17.0.2:8000->172.17.0.1:56780: write: broken pipe
Jan 9 13:50:22 drone docker/drone[8879]: /usr/local/go/src/runtime/panic.go:458 (0x443673)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:419 (0x71dfbb)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/server/user.go:37 (0x73fefd)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/router/middleware/session/user.go:113 (0x72fb2d)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/router/middleware/token/token.go:26 (0x7300a3)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/router/middleware/session/user.go:68 (0x72f436)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/router/middleware/store.go:17 (0x5808e7)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/contrib/ginrus/ginrus.go:26 (0x5877bc)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/router/middleware/header/header.go:25 (0x72d4a0)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/router/middleware/header/header.go:17 (0x72d441)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/recovery.go:45 (0x72b07a)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/context.go:97 (0x71c5ea)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/gin.go:284 (0x72256e)
Jan 9 13:50:22 drone docker/drone[8879]: /go/src/github.com/drone/drone/vendor/github.com/gin-gonic/gin/gin.go:265 (0x721e50)
Jan 9 13:50:22 drone docker/drone[8879]: /usr/local/go/src/net/http/server.go:2202 (0x55168d)
Jan 9 13:50:22 drone docker/drone[8879]: /usr/local/go/src/net/http/server.go:1579 (0x54df87)
Jan 9 13:50:22 drone docker/drone[8879]: /usr/local/go/src/runtime/asm_amd64.s:2086 (0x4762a1)
Jan 9 13:50:22 drone docker/drone[8879]: #033[0m
This happens about ~20 times a day. It seems to only interrupt the UI for people and not affect jobs which is good. It happens for different endpoints as well.
So it seems network traffic between drone container and docker host system gets interrupted. Wanted to remove nginx if I don’t need it to rule it out. Maybe this is a completely unrelated thing I should open a new topic on for though?
Can you try to get more of the stacktrace? That might help pinpoint the source of the panic. I think we definitely want to resolve any panics in the codebase.
ok yes I see now … I think you are right that it is an interrupted network connection. In this case the logic next step does seem to be removing nginx to see if that fixes the problem.
