Meridian

Lazy cat OIDC login has been integrated. ##Functional characteristics - Multi-site Emby Anti-generation: Maintain multiple Emby portals in one management panel, and each site independently listens on ports, independently configures upstream, and independently starts and stops. - Dual upstream diversion: Web pages and API requests go from the main source to the source, and playback, transcoding and download requests can be switched to independent playback and return to the source, suitable for CDN or distributed media nodes. - UA camouflage and client adaptation: Built-in three presets: Infuse, Web, and client, uniformly rewrite HTTP and WebSocket request headers to reduce Emby recognition exceptions. - Traffic quota and speed limit: Calculate cumulative traffic by site, and set quotas and rate limits to facilitate private diversion, shared lines or temporary testing. ###First use process 1. Open the application. 2. After entering `Site Management`, click `Add Site` and fill in the site name, main return address, listening port and UA mode. 3. Listening ports must use ports in the range of `8001-8010`; these ports have been permanently exposed in the lazy cat manifest for access by Emby clients. 4. After saving, confirm that the status is 'running' on the site card, and then assign the corresponding 'lazy cat host name: listening port' to the Emby client or downstream player. ###Daily usage 1. Maintain different sites for different Emby nodes in Site Management, and split the portal by region, line, or device type. 2. If the playback link and the API link are not on the same server, you can fill in the independent playback node in the Playback List, and select 'Direct Diversion' or 'Redirect Follow' according to the service. 3. If the client is sensitive to Emby identification, you can switch UA mode to Infuse, Web or Client, and then return to the player for retest. 4. Observe the cumulative traffic and time window data for each site on the Traffic Statistics page to confirm quotas, speed limits and external chain loads. 5. On the Troubleshooting page, check the configuration of the main loopback, playback loopback, TLS certificate and request header, and locate the loopback that is unreachable, the certificate has expired, or the client recognition is abnormal. 6. When you need to temporarily shut down an entrance, you can directly click 'Disable' on the site card; configuration and statistical data will continue to be retained in SQLite. 7. After adjusting the UA Mode, it is recommended to immediately go back to the Troubleshooting page and run the probe again to confirm that the Current UA / Client / Version field has changed synchronously with the saved results.