Otherwise it mimics the GitHub payload body well enough (we only check for the ref and repository chunks), as well as x-GitHub-event.
But the auth is wrong.
Some reasons I've seen this happen:
If there is a significant time difference between the client (browser) and the server. I've seen this happen within a Docker server sometimes, where the time on the server is very wrong.
Browser extensions such as adblockers causing issues by changing referrers or other headers, blocking things, etc.
Those forms usually send some content related to CSRF protection, within a hidden field in the form. That needs to be sent back and will be verified. Something seems to be going wrong there.
Hi, I am getting an intermittent:
Could not access HTTP invoker remote service at [https://labs-gocd-server-lv-101.labs.my-company.net:8154/go/remoting/remoteBuildRepository]; nested exception is org.apache.http.NoHttpResponseException: labs-gocd-server-lv-101.labs.my-company.net:8154 failed to respond
any thoughts on what to investigate here?
can someone possibly explain the process that is going on? It seems to occur at the same place: after this task is completed, and it's about to start the real work:
[go] Start to prepare mscm_Searchfunc10/38/Build/1/Build_Job on labs-gocd-agent-lv-115.labs.my-company.net [/var/lib/go-agent8]
It's hard to say, but it looks like either due to CPU or network saturation, the GoCD server did not respond in time, to the agent. Some instances I've seen this happen:
Uploading a huge artifact saturates the network (on the GoCD server side) and it can't service any agents.
Usually "Start to prepare" means it is about to check out materials. If your SCM repository is also on the GoCD server (and maybe lots of agents are using that repo), the git checkouts could be causing a CPU or n/w spike, meaning the GoCD server is unable to respond.