Jenkins运行于8080端口但访问首页报AccessDeniedException求助

The Issue You're Seeing #

You mentioned Jenkins is running on port 8080 but throwing an access denied error when loading the homepage. Here's the core error from your stack trace:

java.nio.file.AccessDeniedException: /var/lib/jenkins/config.xml

This means the Jenkins process doesn’t have permission to read its main configuration file—something critical for it to start up properly.

Step-by-Step Solutions #

Let’s walk through the most reliable fixes for this permission issue:

1. Check which user Jenkins is running as
   First, confirm the user that owns the Jenkins process—this is usually a dedicated jenkins user, but sometimes it might run under another account (like root, though that’s not recommended). Run this command to check:

   ps aux | grep jenkins
   

   Look at the first column of the output to get the username.

2. Fix ownership of the Jenkins home directory
   The /var/lib/jenkins directory and all its contents need to be owned by the user Jenkins runs as. If the user is jenkins, run:

   sudo chown -R jenkins:jenkins /var/lib/jenkins
   

   Replace jenkins:jenkins with the correct user:group pair if you found a different user in step 1.

3. Adjust file and directory permissions
   Even with the right ownership, incorrect permissions can block access. Set safe, standard permissions:

   # Set all directories to 755 (read/write/execute for owner, read/execute for others)
   sudo chmod -R 755 /var/lib/jenkins
   # Set config.xml to 644 (read/write for owner, read-only for others)
   sudo chmod 644 /var/lib/jenkins/config.xml
   

4. Restart Jenkins to apply changes
   Finally, restart the Jenkins service so it picks up the new permissions:

   sudo systemctl restart jenkins
   

If the Problem Persists #

If you’re on a RHEL/CentOS-based system, SELinux might be blocking access even with correct file permissions. Test this temporarily by disabling SELinux:

sudo setenforce 0

If Jenkins loads correctly after this, you’ll need a permanent SELinux fix. You can adjust the context of the Jenkins home directory to let SELinux allow access:

sudo semanage fcontext -a -t jenkins_home_t "/var/lib/jenkins(/.*)?"
sudo restorecon -Rv /var/lib/jenkins

That should resolve the access denied error and let Jenkins load its configuration properly.

内容的提问来源于stack exchange，提问作者shrawani karpe