Code 403

The `Code 403` error usually indicates that the configured application startup path is invalid or no longer matches the actual executable location on the rendering server.

## Cause

The application startup path configured in LarkXR is incorrect. This usually happens after the executable file is moved, renamed, or replaced, causing the configured path to become invalid.

## Solution

### 1. Check the Render Server Logs

Open the latest log file in the following directory on the rendering server:

```text
\larkxr-render\RenderServer\logs
```

Review the log to confirm whether the configured application startup path exists on the server and whether the executable can be found correctly.

### 2. Verify the Application Path on the Server

Check whether the executable file still exists in the expected location. If the file has been moved or renamed, note the correct full path.

### 3. Update the Startup Path in LarkXR

Go to the LarkXR management backend and open the application management page. Update the application startup path to the correct executable location, then save the configuration.

![Application startup path configuration example](https://docs.paraverse.cc/media/202504/7f8ad875ea9e408c8807e05249330d667385.png)

### 4. Test the Application Again

After updating the startup path, launch the application again and verify that it starts normally.

## Notes

- This issue is usually caused by an invalid application path rather than a network or client-side problem.
- If the path is correct but the application still fails to start, review the render server logs for additional startup errors.
- If the executable was recently updated, confirm that the new file location is reflected in the LarkXR application configuration.