Pujit Mehrotra 9df6a3f5eb fix(connect): clear wanport upon disabling remote access (#1624) ...

Resolve #1615 -- lingering wanport caused issue with LAN Access via
Connect, because those URL's are constructed using `wanport`, but since
WAN access would be disabled, NGINX would not listen on the port.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* WAN access settings now correctly gate related options; UPnP only
enables when WAN access is Always.
* Static WAN port is applied only when eligible and is cleared when WAN
access is disabled to avoid unintended overrides.
* Dynamic remote access migration uses sanitized URLs to prevent
propagation of user-provided addressing.

* **Chores**
* Minor ordering and formatting adjustments to reflect updated
precedence and clarify behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2025-08-25 13:21:48 -04:00

..

unraid-api-plugin-connect

fix(connect): clear wanport upon disabling remote access (#1624)

2025-08-25 13:21:48 -04:00

unraid-api-plugin-generator

fix: refactor API client to support Unix socket connections (#1575)

2025-08-13 16:15:15 -04:00

unraid-api-plugin-health

fix: refactor API client to support Unix socket connections (#1575)

2025-08-13 16:15:15 -04:00

unraid-shared

feat(api): add cpu utilization query and subscription (#1590)

2025-08-19 14:44:16 -04:00