Linux下独立版Artifactory部署成功但无法访问问题求助

Let’s walk through the most common fixes for getting your freshly deployed Artifactory instance accessible—these are the steps I rely on when debugging similar issues:

1. Confirm Artifactory is running and check logs first #

Start by verifying the service status to make sure it’s actually up:

# For systemd-based distros (Ubuntu 16.04+, RHEL/CentOS 7+)
systemctl status artifactory

# For older init.d systems
service artifactory status

If it shows as inactive/failed, the logs will tell you exactly why. Tail the main Artifactory log to spot startup errors:

tail -f /opt/jfrog/artifactory/var/log/artifactory.log

Look for red flags like port binding failures, missing directory permissions, or invalid config syntax.

2. Check if the port is actually being listened on #

Make sure Artifactory is binding to your target port. Run this to list open ports and their associated processes:

ss -tulpn | grep -E '8080|8081'

• If there’s no output for your port, Artifactory isn’t using it (jump to checking the config file next).
• If another process is using the port, you’ll need to stop that process or pick a different unused port.

3. Stop using HTTPS (for now) #

This is a super common mistake! Standalone Artifactory doesn’t enable HTTPS by default out of the box. If you’re trying https://localhost:8080/..., you’ll get connection errors because the instance is only serving HTTP traffic initially.

Test the HTTP version first:
http://localhost:8080/artifactory/webapp
If this works, you can set up SSL later via Artifactory’s admin settings or a reverse proxy like Nginx.

4. Validate the port configuration in Artifactory’s config file #

Double-check that the port in Artifactory’s system config matches what you’re trying to use:

cat /opt/jfrog/artifactory/var/etc/system.yaml | grep -A5 -B5 'http.port'

If you need to adjust the port, update the http.port value, then restart the service to apply changes:

systemctl restart artifactory

5. Check firewall and SELinux restrictions #

Linux security tools often block traffic even if Artifactory is running:

• Firewall: List allowed ports to confirm your target port is open:

  # For ufw (Ubuntu/Debian)
  ufw status
  
  # For firewalld (RHEL/CentOS/Fedora)
  firewall-cmd --list-ports
  

  If the port isn’t listed, add it:

  # ufw
  ufw allow 8080/tcp
  
  # firewalld
  firewall-cmd --add-port=8080/tcp --permanent && firewall-cmd --reload
  

• SELinux: If SELinux is enforcing, it might block Artifactory’s port access. Temporarily disable it to test:

  setenforce 0
  

  If access works after this, permanently allow the port for HTTP traffic:

  semanage port -a -t http_port_t -p tcp 8080
  

6. Fix directory permissions #

Artifactory needs read/write access to its installation directory. Check the ownership:

ls -ld /opt/jfrog/artifactory

The directory should be owned by the artifactory user and group. If not, correct it:

chown -R artifactory:artifactory /opt/jfrog/artifactory

Then restart the service.

7. Rule out browser caching #

Sometimes browsers cache failed connection attempts. Try accessing the URL in incognito/private mode, or clear your browser’s cache and cookies before retrying.

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