The Intranet access to the background failed

## Prioritize Log Review to Identify Issues
**Obtain Key Error Information**
* Navigate to the directory   larkxr-center/admin/logs
* Open the latest log file (  admin.log  ).
* Search for keywords such as   ERROR   or   Exception   and record the specific error content.

## Common Causes and Solutions
1. **Incorrect Local IP Configuration**
**Symptom:** The log may display messages such as "Connection Refused."
**Solution**: Open   cmd   and use the   ipconfig   (Windows) or   ifconfig   (Linux/Mac) command to query the valid intranet IP address.
   * Set this IP address in the local IP field of the startup manager.
   * Save the changes and restart the Admin service.

1. **Port 8184 is Occupied**
**Symptom**: The log indicates "Address already in use" or "Port Conflict."
**Solution:**
   •  Identify the Occupying Process:
    ```bash
    # For Linux/Mac
    lsof -i :8184  # or netstat -tulnp | grep 8184
    # For Windows
    netstat -ano | findstr :8184
    ```
   •  Terminate the Occupying Process:
        *   Linux/Mac: Use   kill -9 [PID]  .
        *    Windows: End the process with the corresponding PID in Task Manager, or run   taskkill /F /PID [PID]  .

• Restart the Admin service.

**Dependent Services Not Started**
   • Symptom: The log shows connection failures to databases, Redis, or other middleware.
   • Solution: Verify that dependent services such as MySQL and Redis are running properly.