Drone continually gives me 401’s on the call to /api/user/feed at the end of the login flow with Github. Upon 401 I get cycled back through the login flow which causes a login-loop that triggers the abuse mechanism from Github.
How can I tell why I am getting a 401? I am forwarding the headers through the proxy as well as the host.
I am deploying “drone/drone:alpine” on docker swarm, traffic goes nginx -> oauth2_proxy -> drone master
(for reference https://github.com/bitly/oauth2_proxy)
I’m just looking for a way to troubleshoot this since I have no idea what Drone is missing that it desires for authorization to succeed, and how/when that authorization token/header/cookie is supposed to be initialized and persisted for this call to the /api/user/feed