Forbidden hudson.plugins.git.UserRemoteConfig/checkUrl on this server

[sstraakenbroek]

I'm running a fresh installation of Jenkins on CentOS 7 behind Apache 2.4.6.

I modified my service /etc/sysconfig/jenkins to run over port 9090

Configuration of my apache to access jenkins on https: 

<VirtualHost *:80>
ServerName jenkins.domain.nl

RewriteEngine on
ReWriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R,L]
</VirtualHost>

<VirtualHost *:443>
ServerName jenkins.domain.nl

SSLEngine On
SSLProxyEngine on
SSLCertificateFile /etc/pki/tls/certs/domain_nl.crt
SSLCertificateChainFile /etc/pki/tls/certs/domain_nl.ca-bundle.crt
SSLCertificateKeyFile /etc/pki/tls/private/domain_nl.key

ProxyRequests Off
ProxyPreserveHost On
RewriteEngine On
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port "443"
AllowEncodedSlashes NoDecode

ProxyPass / http://localhost:9090/ nocanon
ProxyPassReverse / http://localhost:9090/

<Proxy http://localhost:9090/*>
Order allow,deny
Allow from all
</Proxy>
</VirtualHost>

 I've installed the following plugins: 

apache-httpcomponents-client-4-api	4.5.3-2.1
bouncycastle-api	2.16.2
command-launcher	1.2
credentials	2.1.16
display-url-api	2.2.0
git	3.8.0
git-client	2.7.1
jackson2-api	2.8.11.1
jsch	0.1.54.2
junit	1.24
mailer	1.21
matrix-project	1.13
mercurial	2.3
scm-api	2.2.7
script-security	1.44
ssh-credentials	1.13
structs	1.14
workflow-api	2.27
workflow-scm-step	2.6
workflow-step-api	2.14

Creating a new project

Item name: Project

Type: Freestyle project

When selection the Source Code Management to Git.

The following error is occured (See Screen Shot): 

Forbidden
You don't have permission to access /job/Project/descriptorByName/hudson.plugins.git.UserRemoteConfig/checkUrl on this server.

 and 

Forbidden
You don't have permission to access /job/Project/descriptorByName/hudson.plugins.git.UserRemoteConfig/checkCredentialsId on this server.

Can someone help me solving this issue?

 

 

[Mark Waite]

Check the ownership and permissions of the directories and files inside the JENKINS_HOME directory.  If they cannot be written by the user running the Jenkins java process, that would probably cause the type of failure message you're reporting.

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7881e75f-6f5f-4dac-a0ec-0f400b803128%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sstraakenbroek]

Everything is set to user jenkins and group jenkins.

Other plugins like Mercurial are working just fine with no errors with the same user/group/permissions.

[Mark Waite]

And yet the message in the screenshot says that files cannot be read.

Have you checked that the plugins/git.hpi file is readable?

Have you confirmed that there are no directories on that system which forbid writing or searching their contents?

Are there any exotic permissions being applied to that file system by SELinux?

Is the file system hosting the Jenkins installation mounted read-only?

If you execute `java -jar jenkins.war -httpPort 23456` on that computer as a different user can you configure a job that uses git?

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/49ba25d7-0870-4f49-9eb5-9ee4619de787%40googlegroups.com.

[Daniel Beck]

> On 30. Apr 2018, at 13:44, Mark Waite <mark.ea...@gmail.com> wrote:
>
> And yet the message in the screenshot says that files cannot be read.

That's a URL.