Registro de cambios de Quick Connect

Fixed (licensing): the license key field is always visible, so a new key can be activated even while the saved license still shows as active; a refused key no longer replaces the saved key and the page shows why; when the last check fails (for example a deleted or revoked license), the page and the log show a warning with the date until which the saved license keeps working; activation, manual checks and release are written to the log.

• Fixed: the screen no longer gets stuck without a code and QR code when its network reached 5 pending requests (all devices behind the same NAT share the limit). A screen gets its own code back (lifetime extended) instead of a new one, and its own requests no longer count toward the per-network limit.
• New: one-tap approval on the same local network. When the phone is already signed in to the server and the waiting screen is on the same network, the phone page shows "Approve screen" and a single tap approves — no confirmation digits. From another network the flow with the digits on the screen is unchanged (QC-1 intact).
• Robustness: the screen checks for an existing session even when the settings (ScreenSettings) cannot be read — it no longer shows the code pointlessly to an already signed-in browser.
• Maintenance: silently swallowed exceptions from the website-patch check and license startup now reach the log.

• Security: the phone page shows where the waiting screen is (on the same network as you, on your home network, or elsewhere, with the country when known) and a warning. When the code comes from a link or the QR code, the 6 digits on the screen must be typed before approving: a received link can no longer be approved with a single tap.
• Security: "Administrator accounts cannot sign in with a code" is on by default for new installs and now also blocks app codes. Existing installs keep their saved setting.
• Security: real visitor address. X-Forwarded-For / X-Real-IP are trusted only from localhost and from trusted proxies (new "Trusted proxies" setting), plus a "Behind Cloudflare" option (automatic when Edge Shield is connected). Attempt limits and the screen network check use this address; for IPv6, limits apply to the whole /64 prefix.
• Security: approving with the Emby session now has a wrong-attempt limit (per account and per network).
• Security: new account created from the screen (Registration): the screen is approved automatically only if it is on the server's local network or on the same network as the person who signed up; otherwise it is approved from the phone as usual.
• Security: app codes can be turned on only for accounts using Emby's default sign-in method (never over LDAP/SSO); turning them off restores the previous method, and a turn-off request for an account that does not use codes changes nothing. Only a password shaped like "123456" or "123 456" is treated as a code.
• Security: at most 2000 screen codes kept in memory, screen lookup by key without scanning every code, periodic cleanup of attempt counters.
• Licensing: unsealed license-server responses are rejected, versions offered for update or rollback must be signed, sent logs are redacted.

• Privacy: the payment QR code on the License page is now generated locally, in the page; the payment link is no longer sent to a third-party QR service (api.qrserver.com).
• If the browser already has a valid session on this server, the screen skips the code and goes straight to the configured destination (Emby Web or the Netflix-style MediaLab TV page, which gets ?fs=1 and offers full screen). ?switch=1 still shows the code (another account). New panel button: “MediaLab TV (Netflix-style)”.

• The after-sign-in address is set in the panel: the screen can open Emby Web (default), the TV web interface (e.g. /emby/MediaLabTv/, with its own button when installed) or any path/https address the admin chooses.
• Local and external addresses (HTTPS only): the external address may use a different name and SSL port than the local one. The screen shows both, and the QR code opens the external address (or the local one, if preferred). The panel suggests addresses from the Emby settings and lists the screen and phone links on both addresses.

• Panel: external links show only when the external address is set (0.1.3 showed empty boxes).

• New account straight from the screen: if the person scanning the code has no account and creates one with Registration (with payment through Cashier, if required), the screen signs in with the new account by itself once it is active. New panel setting, off by default; the code stays valid while signing up and paying (up to one hour), and the screen shows "an account is being created on the phone". Requires Registration 1.10.5.

• The server log is no longer sent automatically when changing the sign-in screen fails; it is sent only if the admin turned on automatic log sending.

• First release: passwordless sign-in on TVs and other screens. The screen shows a code and a QR code, you approve from your phone (with the phone's Emby session or with username and password) and the screen signs in to Emby Web. A "Sign in with your phone" button on the Emby Web sign-in screen. A one-time code (6 digits, valid 5 minutes) instead of the password in the official Emby apps, enabled per user, with the usual password still valid. Attempt limits; disabled accounts and accounts without remote access are refused. A panel with settings and recent sign-ins. Author: MediaLab Works.