Using BLOCK_DIRECT=true with single_tailnet experiment results in no connectivity #10391
Labels
networking
Area: networking
s2
Broken use cases or features (with a workaround). Only humans may set this.
i'm creating this issue to track an issue experienced by a strategic customer that returned 504s on the
/listening-ports
API route with thesingle_tailnet
experiment enabled andCODER_BLOCK_DIRECT=true
. this happened upon upgrade from 2.2.x to 2.3.1. the agent and workspace displayed as healthy in the dashboard.coderd logs returned:
removing the
single_tailnet
resolved things. here's their full env var to help debug:The text was updated successfully, but these errors were encountered: