Troubleshooting Backend Intranet Access Failure

## Prioritize Log Review

Before changing the configuration, review the logs to identify the root cause. In most cases, the error message in the log points directly to the issue.

### Collect Key Error Information

1. Go to the `larkxr-center/admin/logs` directory.
2. Open the latest log file: `admin.log`.
3. Search for keywords such as `ERROR` or `Exception`.
4. Record the full error message before proceeding.

## Common Causes and Solutions

### 1. Incorrect Local IP Configuration

**Symptom**  
The log displays messages such as `Connection refused`.

**Solution**

1. Open the command line.
2. Check the valid intranet IP address:
   ```bash
   # Windows
   ipconfig

# Linux / macOS
   ifconfig
   ```
3. Update the local IP field in the startup manager with the correct intranet IP address.
4. Save the changes and restart the Admin service.

### 2. Port 8184 Is Already in Use

**Symptom**  
The log displays messages such as `Address already in use` or `Port conflict`.

**Solution**

1. Identify the process using port `8184`:
   ```bash
   # Linux / macOS
   lsof -i :8184
   # or
   netstat -tulnp | grep 8184

# Windows
   netstat -ano | findstr :8184
   ```

2. Stop the conflicting process:
   ```bash
   # Linux / macOS
   kill -9 [PID]

# Windows
   taskkill /F /PID [PID]
   ```

3. Restart the Admin service.

### 3. Dependent Services Are Not Running

**Symptom**  
The log shows connection failures related to MySQL, Redis, or other middleware services.

**Solution**

1. Check whether required dependent services, such as MySQL and Redis, are running properly.
2. Start any stopped services.
3. Restart the Admin service if necessary.