Thanks a lot your reply helped me a lot
I had to update nginx to have these settings
# Required for new HTTP-based CLI
proxy_http_version 1.1;
proxy_request_buffering off;
# workaround for https://issues.jenkins-ci.org/browse/JENKINS-45651
After some research we found the problem: it was the anti-virus software
because it damaged the HTTP responses. After disabling the HTTP
scanning feature everything worked fine.
Thanks to all for their help!
Am 04.10.2017 um 13:50 schrieb Riccardo Foschia:
Hi all,
after an upgrade of
Am 04.10.2017 um 15:51 schrieb Devin Nusbaum:
Do you see any errors in the logs on the Jenkins server, and is the
jenkins-cli.jar you are using from your 2.81 instance? You can download a fresh
jar from http://YOUR_HOST/jenkins/jnlpJars/jenkins-cli.jar. (If you aren’t
using the /jenkins
Do you see any errors in the logs on the Jenkins server, and is the
jenkins-cli.jar you are using from your 2.81 instance? You can download a fresh
jar from http://YOUR_HOST/jenkins/jnlpJars/jenkins-cli.jar. (If you aren’t
using the /jenkins context path just
Am 04.10.2017 um 14:53 schrieb Daniel Beck:
On 4. Oct 2017, at 14:29, Riccardo Foschia
wrote:
Thanks for your answer, but there is no proxy running.
What security realm are you using?
We are using LDAP and project based matrix authorization (like
> On 4. Oct 2017, at 14:29, Riccardo Foschia
> wrote:
>
> Thanks for your answer, but there is no proxy running.
What security realm are you using?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
Am 04.10.2017 um 14:00 schrieb Daniel Beck:
On 4. Oct 2017, at 13:50, Riccardo Foschia
wrote:
after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http protocol
but it doesn't work (SSH protocol seems to work after the upgrade).
No matter
> On 4. Oct 2017, at 13:50, Riccardo Foschia
> wrote:
>
> after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http
> protocol but it doesn't work (SSH protocol seems to work after the upgrade).
>
> No matter which CLI command I use, after a few
Hi all,
after an upgrade of Jenkins 1.638 to 2.81 CLI I need to switch to http
protocol but it doesn't work (SSH protocol seems to work after the
upgrade).
No matter which CLI command I use, after a few seconds the call returns
but shows no result. E.g.
java -jar jenkins-cli.jar -s