Previously, the predefined "asleep" MOTD response on backend-dial-failure
was only served when the route had a waker registered. For static fleets
(no auto-scale) the gate left clients with a silently-closed TCP socket on
status-pings whenever the backend was down — they couldn't tell whether
the route was wrong, the host was offline, or the proxy was down.
Drop the `waker != nil` gate so any known route's dial-failure on
NextState=Status falls back to the configured asleep/loading MOTD. The
existing per-route override + global AUTO_SCALE_ASLEEP_MOTD chain handles
the actual text. Login attempts still close silently as before — only
status pings get the fallback.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* fix: Reduce log spam for sleeping servers
* fix: Fix autodownscaling for initial player connection
* fix: Instant route updating when a docker container is downscaled
* feat: Show asleep or loading motd while the server is waking up
* Code cleanup of routes config loader and API server (#424)
(cherry picked from commit 1ee3eb4de3)
* Refactored server setup and run out of main (#425)
(cherry picked from commit 05c57c3b85)
* Code cleanup in and around connector (#427)
(cherry picked from commit b3e88db48c)
* Update away from deprecated k8s NewInformer
* Tidy up couple of k8s docs examples
* Revert "Code cleanup in and around connector (#427)"
This reverts commit b3e88db48c.
* Revert "Refactored server setup and run out of main (#425)"
This reverts commit 05c57c3b85.
* Revert "Code cleanup of routes config loader and API server (#424)"
This reverts commit 1ee3eb4de3.
claude-timemachine
Bastian Wagner
Lenart Kos
Chris Farhood
Jasper
Geoff Bourne
solidDoWant
Samuel McBroom
UrbaneChimp
Slawomir CALUCH
iipanda
Michael Vorburger ⛑️
Gabriel C