Troubleshooting Artifactory JCR 7.125.8 Login Stuck on Pending in Ubuntu 22.04 VM

04, focused on service health, JFrog logs, database reachability, reverse proxy behavior, and restart safety.

Quick Read

Symptom: 04, focused on service health, JFrog logs, database reachability, reverse proxy behavior, and restart safety.
Check first: Capture the affected source, destination, protocol, port, DNS name, VLAN or subnet, and exact error before changing policy.
Risk: Changes system state

Symptoms

Users are unable to log into Artifactory JCR 7.125.8, with the login process getting stuck on 'Pending' after entering the admin password.

Environment

Artifactory JCR 7.125.8 running on an Ubuntu 22.04 Virtual Machine.

Most Likely Causes

This issue may be caused by network connectivity problems, database connection issues, or misconfigured Artifactory settings.

What to Check First

Capture the affected source, destination, protocol, port, DNS name, VLAN or subnet, and exact error before changing policy.
Verify path, name resolution, authentication, and firewall policy separately so one symptom does not hide multiple failures.
Check whether the issue is isolated to one client, one subnet, one VPN profile, or every path.

Fix Steps

Check Artifactory Service Status
Ensure that the Artifactory service is running properly.
Safe to run: read-only
```
sudo systemctl status artifactory
```
Review Artifactory Logs
Examine the Artifactory logs for any errors or warnings that may indicate the cause of the login issue.
Safe to run: read-only
```
sudo tail -n 100 /var/opt/jfrog/artifactory/logs/artifactory.log
```
Verify Database Connectivity
Check if Artifactory can connect to its database. This can be done by testing the database connection settings in the Artifactory configuration file.
Safe to run: read-only
```
sudo nano /var/opt/jfrog/artifactory/etc/db.properties
```
Check Network Configuration
Ensure that the VM has proper network configuration and can reach the database server.
Example pattern only. Adjust for your environment before running.
```
ping <database-server-ip>
telnet <database-server-ip> <database-port>
```
Inspect Reverse Proxy Settings
If using a reverse proxy, verify that it is correctly configured and not blocking requests to Artifactory.
Changes system state: review before running
```
sudo nano /etc/nginx/sites-available/artifactory
sudo nginx -t
sudo systemctl restart nginx
```
Clear Browser Cache and Cookies
Sometimes, browser cache and cookies can cause issues with login sessions. Clear the cache and cookies in your web browser.
Example pattern only. Adjust for your environment before running.
```
Open browser settings > Privacy and Security > Clear browsing data
```
Restart Artifactory
If the above steps do not resolve the issue, restart the Artifactory service.
Changes system state: review before running
```
sudo systemctl restart artifactory
```

Validation

The same client and network path can reach the target after the change.
Firewall, VPN, DHCP, DNS, or switch logs show allowed traffic or successful negotiation instead of the prior failure.
A second path check confirms that the fix did not open unintended access or break another subnet.

Logs to Check

Firewall, VPN, DNS, DHCP, or switch logs for the failing timestamp.
Client resolver, route table, VPN client, or browser/network diagnostics.
Packet capture or flow logs when policy and routing disagree.

Rollback and Escalation

Export or screenshot the original policy, route, resolver, or interface configuration before changing it.
Remove temporary allow rules, test DNS records, or route changes after validation.
Restore the previous VPN profile, firewall rule, or switch configuration if reachability worsens.

Escalate When

Escalate if the same error persists after rollback and a clean retry from the original failing path.
Escalate if logs show authorization, data loss, certificate, replication, or production availability risk outside the local service owner scope.

Edge Cases

If the database is unreachable, ensure that the database service is running.
If using a firewall, check that the necessary ports are open.

Notes from the Field

Most network incidents need source and destination evidence. A successful test from an admin laptop does not prove the affected client path is fixed.
For VPN and firewall changes, keep the blast radius narrow and time-box any temporary allow rule.