fix(apps): repair orchestrator starts before launch

This commit is contained in:
archipelago 2026-05-18 09:20:12 -04:00
parent d0b08d2790
commit 7104ba0cbf
2 changed files with 6 additions and 0 deletions

View File

@ -1,5 +1,10 @@
# Changelog # Changelog
## v1.7.65-alpha (2026-05-18)
- Orchestrator-backed app starts now run the same pre-start repairs as the legacy Podman path, so Nginx Proxy Manager stale `81:81` container metadata is removed and recreated before the orchestrator tries to start it.
- Live diagnostics on `100.70.96.88` confirmed host nginx is healthy while Nginx Proxy Manager has no listeners on `8081`, `8084`, or `8444`, causing host nginx `502` responses for NPM proxy paths.
## v1.7.64-alpha (2026-05-18) ## v1.7.64-alpha (2026-05-18)
- Update apply rate limiting is relaxed for authenticated admins from 2 attempts per 10 minutes to 10 attempts per minute, preventing the System Update page from getting stuck behind `429 Too Many Requests` during legitimate OTA retry/troubleshooting flows. - Update apply rate limiting is relaxed for authenticated admins from 2 attempts per 10 minutes to 10 attempts per minute, preventing the System Update page from getting stuck behind `429 Too Many Requests` during legitimate OTA retry/troubleshooting flows.

View File

@ -668,6 +668,7 @@ async fn do_orchestrator_package_start(
if i > 0 { if i > 0 {
tokio::time::sleep(std::time::Duration::from_secs(2)).await; tokio::time::sleep(std::time::Duration::from_secs(2)).await;
} }
repair_before_package_start(name).await;
match orchestrator.start(name).await { match orchestrator.start(name).await {
Ok(()) => wait_after_orchestrator_start(name).await, Ok(()) => wait_after_orchestrator_start(name).await,
Err(e) if is_unknown_app_id_error(&e) => { Err(e) if is_unknown_app_id_error(&e) => {