Code 401

The `Code 401` error usually occurs when the application session URL is accessed incorrectly after the session has already been created.

## Cause

After a user enters an application through the correct launch URL, LarkXR generates a temporary in-session URL for the active session. This generated URL is used internally by the web client and is not intended to be refreshed, copied, bookmarked, or opened again directly.

If the user refreshes the page after entering the application, or tries to access the generated in-session URL again later, the session may fail and `Code 401` may appear.

## Correct Access Method

Always enter the application through the original launch URL in the following format:

```text
http://<server-ip>:8181/appli/start?appliId=<application-id>&codeRate=<bitrate>&frameRate=<frame-rate>
```

Do not reopen the generated session URL in the following format:

```text
http://<server-ip>:8181/webclient/?appliId=...&taskId=...&renderServerIp=...&renderServerPort=10002...
```

## Example

Correct launch URL:

```text
http://192.168.0.55:8181/appli/start?appliId=911273233334927360&codeRate=8000&frameRate=60
```

After the application starts, the browser may change to a generated session URL such as:

```text
http://192.168.0.55:8181/webclient/?appliId=911273233334927360&appliType=2&taskId=991368586012393472&taskStatus=1&network=1&codeRate=8000&frameRate=60&audioCodeRate=32&preferDecoder=h264&renderServerIp=192.168.0.50&renderServerPort=10002...
```

This generated `webclient` URL