* Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/pro To restore this content, you can run the 'unminimize' command. Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings Last login: Mon Mar 9 15:35:35 2026 from 100.95.5.23 │ >_ OpenAI Codex (v0.107.0) │ │ │ │ model: gpt-5.4 xhigh /model to change │ │ directory: ~ │ Tip: Visit the Codex community forum: https://community.openai.com/c/codex/37 › hello ■ Conversation interrupted - tell the model what to do differently. Something went wrong? Hit `/feedback` to report the issue. › hey, I just wasted a bit of time because I had my pixel 6a as tailscale tunnel for this VPS I guess? thing is, this same tailscale account has another exit node which is my computer, so can't we idk use that as the tailscale exit node as kind of a fallback? or if anything the pixel 6a as a fallback? i do not dig having to keep the phone on at all times tbh, but I might whip this computer out for working on personal projects which I need to have access to the internet if I want to move forward yk? • I need to gather information for the user about Tailscale exit nodes and any fallback options. Tailscale's behavior might have changed, and since this involves specific product capabilities, browsing official documentation is essential. I might not need any coding tools right now. I could also consider mentioning the date. I will start by inspecting the official Tailscale docs regarding exit nodes and failover/fallback features. I want to ensure I give accurate and up-to-date information. • Searched site:tailscale.com official docs exit nodes automatic failover fallback multiple exit nodes • The user is curious about using a computer exit node and a phone fallback with Tailscale. I need to clarify that Tailscale supports one active exit node per client, and automatic failover isn't set to default. I wonder if the auto:any option allows selecting a recommended exit node and possibly switching if one goes offline. However, I must check the official documentation to find the specifics of how exit nodes behave in these situations. • Searched site:tailscale.com auto:any exit nodes failover automatically when exit node offline • I've come across an interesting blog about a new feature coming in August 2025. It mentions that clients will be able to set a recommended exit node using --exit-node=auto:any. This means they'll automatically switch to recommended exit nodes based on availability and network conditions. I should look for the official documentation, as it might be updated with more details. Let's search for specific docs to confirm this information! • Searched site:tailscale.com "tailscale set --exit-node=auto:any" docs • I noticed the official CLI documentation mentions automatic node switching and compatibility for various platforms like Linux, Windows, and Mac. Since the user's VPS is likely on Linux, I should highlight this compatibility. It might also be beneficial to explain Android usage, suggesting the phone as a backup exit node. Using --exit-node=auto:any enables tracking and automatic switching of nodes based on latency and performance. The documentation doesn’t seem to provide a way to prefer desktop over phone, which could be confusing. Reviewing Tailscale Updates I see that as of March 15, 2026, the Tailscale documentation mentions features from last month and updates from 2025. On a VPS running recent Tailscale, I should note that using tailscale I’m considering that tracking the suggested exit node relies on the availability of the suggested exit nodes feature. I should search the official pricing details to get accurate information. It’s essential to find out if --exit-node=auto:any is still plan-specific. I wonder if the documentation has been updated to clarify whether this feature is available across different plans. Let me dig into the docs and find the most current information to ensure accuracy! Interpreting user needs I need to clarify whether the user wants their VPS to access the public internet through their home computer to bypass ISP restrictions. It seems they might have used their phone as a "tunnel" since the VPS lacks direct internet. I should provide commands: for the desktop, use sudo tailscale set --advertise-exit-node and approve in the admin console. On the VPS, utilize tailscale set --exit-node=auto:any if the version supports it, or choose manually. I'll also mention checking available nodes with tailscale exit-node list. It’s important to note that if they’re on a free or personal plan, recommended exit nodes might not be available. Clarifying exit node availability I noticed that, according to the documentation validated on January 7, 2025, recommended exit nodes aren’t available on Personal or Free plans. Yet, the CLI docs validated on January 26, 2026, show that the command exists. Still, the availability of this feature seems to be plan-limited. I should explain that while the command is in the current CLI docs, Tailscale's separate recommended-exit-node documentation indicates it’s limited to Starter, Premium, Enterprise, or the Mullvad add-on. So, on a Personal or Free tailnet, users shouldn’t rely on auto:any unless their plan explicitly includes it. • Searched https://tailscale.com/docs/reference/tailscale-cli • Searched 'available for' in https://tailscale.com/docs/features/exit-nodes/auto-exit-nodes • I think I should clarify how each device selects an exit node separately. Maybe I need to find a citation that explains this process in detail. I could reference information from search results, but I also think it might be beneficial to open lines around the topic for a clearer understanding. Overall, I’m considering how to approach this to ensure the user comprehends the concept fully! • Searched https://tailscale.com/kb/1103/exit-nodes/ • Searched site:tailscale.com docs one exit node at a time tailscale • I’m considering how to answer the question about using exit nodes in Tailscale. Yes, you can advertise both desktop and Pixel as exit nodes in the same tailnet. Typically, Tailscale uses one selected exit node, and without auto mode, it won’t switch if that node goes offline. However, the current Tailscale CLI does allow for an auto:any setting, which can automatically track suggested exit nodes as conditions change. It’s not a strict primary/backup system, though. Clarifying exit node settings I can't tell Tailscale to prioritize using my desktop first and the Pixel second in the regular setup. If I don't have a plan with recommended exit nodes, like the Starter or Premium options, I’ll need to switch manually or create a custom script that checks connectivity. For reliable internet from my VPS, it's best to use an always-on device, such as my home PC or a mini PC. If my computer sleeps, the exit node won’t work unless I disable sleep or use Wake-on-LAN. Discussing exit node options I'm considering that if neither my desktop nor Pixel is online, I could face issues. I wonder if I can mention using a mobile device as an exit node. The official docs say Android can advertise as one, but battery restrictions could make it a poor long-term option. I need to verify this by searching the docs. If I set it up, I’d advertise the exit nodes on both devices, approve them in the admin console, and execute the required commands on the VPS to configure it properly. • Searched site:tailscale.com Android exit node docs battery sleep tailscale • If the user wants a true ordered failover on their free/personal Tailscale setup, I might suggest using a simple cron or systemd script to ping and switch nodes. They could check the version with tailscale version, and it’s important to mention that if their desktop sleeps, it will stop being an exit node. If they’d like, I can assist with setting this up on their VPS. I could also provide a link list to documentation at the end, avoiding excessive citations. Clarifying Tailscale options I want to keep my tone friendly and light, matching the user's style. I should mention another possibility: they can use ACL autoApprovers or tags, though it's not strictly necessary. If they need internet access from the VPS and are in a remote environment, using an exit node on the same Tailscale account would work. I'll ensure I accurately reference claims, noting that automatic switching relies on CLI documentation (validated Jan 26, 2026). I should clarify that the recommendation mode isn't a user-defined priority list and that MDM policies might limit exit node suggestions. Addressing Tailscale documentation updates It might be helpful to mention the potential plan mismatch between the Tailscale documentation from January 2025 and the updated CLI docs from January 2026, since the user may not be aware of this discrepancy. I could say, "One important note: the recommended-exit-node page, last validated on January 7, 2025, indicates that this feature is available only on Starter, Premium, or Enterprise plans, as well as the Mullvad add-on. The CLI page, validated January 26, 2026, does go into details on the flag itself." Drafting concise guidance I need to create a concise yet helpful draft. I think mentioning the "Pixel 6a fallback" is useful, but it has operational drawbacks. Maybe I’d say it “works technically but is lousy operationally.” I want to include exact dates: December 15, 2025; January 7, 2025; January 26, 2026. I should also note that another exit node could be my computer, which is better if left awake. I'll structure the response under Short Answer, Best Setup, and Docs with around 8-12 bullet points, including links. ─ Worked for 3m 16s ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── • Yep — with one important caveat. Short Answer - You can absolutely have both your computer and your Pixel 6a advertised as exit nodes on the same tailnet. - Your VPS can use an exit node from either one, but normally it uses one selected exit node at a time. - If that selected node disappears, traffic through that exit node breaks unless you switch manually — unless you use Tailscale’s newer auto:any behavior. What Counts As “Fallback” network conditions change. - So yes, that’s basically the closest thing to fallback for your VPS. - But I don’t see a documented “desktop first, phone second” priority list; the documented auto mode is recommendation-based, not an explicit primary/backup order. Best Setup For You - Use your computer as the main exit node if you can keep it awake; that’s way better than depending on the phone. - Keep the Pixel 6a only as emergency backup if you want, but Tailscale’s docs say Android exit nodes are still being optimized, are userspace-only, and may be too slow for many cases. - If your computer sleeps, it stops being a useful exit node, so “awake and plugged in” matters. One Gotcha - Tailscale’s “recommended exit nodes” docs were last validated on January 7, 2025 and still say that feature is for Starter/Premium/Enterprise or Mullvad add-on. - So safest read: current clients support the auto:any flag, but whether the smart auto-selection works for your tailnet may still depend on plan. Practical Commands - List exit nodes: tailscale exit-node list - Use automatic selection if supported: sudo tailscale set --exit-node=auto:any - Or pin the desktop manually: sudo tailscale set --exit-node= Docs - https://tailscale.com/docs/features/exit-nodes - https://tailscale.com/docs/features/exit-nodes/auto-exit-nodes If you want, I can help you check this VPS’s Tailscale version and set it up so it prefers the least-annoying option. □ Check available exit nodes □ Configure best exit-node mode □ Verify routing setup • I’m checking the VPS’s Tailscale state and available exit nodes first. • Ran tailscale version └ 1.94.2 tailscale commit: 0a29cf18b56e478b9cd33af07755fcae90d5171a long version: 1.94.2-t0a29cf18b-g3f044c9f6 other commit: 3f044c9f62dd0168c79f9ba7e67250b1dee06caa go version: go1.25.5 ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── • Version’s recent enough; now I’m pulling the full Tailscale status JSON. • Waited for background terminal · tailscale status --json • Ran tailscale status --json └ failed to connect to local tailscaled (which appears to be running as tailscaled, pid 825). Got error: Failed to connect to local Tailscale daemon for /localapi/v0/status; not running? Error: dial unix /var/run/tailscale/tailscaled.sock: connect: operation not permitted ✔ You approved codex to always run commands that start with sudo tailscale status } • Updated Plan └ ✔ Inspect current Tailscale state ✔ Check available exit nodes □ Configure best exit-node mode □ Verify routing setup ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── • I found two usable exit nodes. Next I’m checking whether auto-selection is available here. • Ran tailscale set --help └ Change specified preferences • The client supports auto:any; I’m checking which exit nodes Tailscale currently sees and suggests before changing anything. ✔ You approved codex to always run commands that start with sudo tailscale exit-node • Ran sudo tailscale exit-node list └ IP HOSTNAME COUNTRY CITY STATUS └ Suggested exit node: desktop-69ped3u.tail9799d2.ts.net. To accept this suggestion, use `tailscale set --exit-node=desktop-69ped3u.tail9799d2.ts.net.`. ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── • Tailscale currently recommends the desktop, which is ideal. I’m switching this VPS to automatic exit-node selection now. ✔ You approved codex to always run commands that start with sudo tailscale set • Ran sudo tailscale set --exit-node=auto:any └ (no output) ⚠ Falling back from WebSockets to HTTPS transport. stream disconnected before completion: failed to lookup address information: Try again ■ stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses) ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── › so what happened now ■ Conversation interrupted - tell the model what to do differently. Something went wrong? Hit `/feedback` to report the issue. /Token usage: total=76,493 input=68,430 (+ 162,048 cached) output=8,063 (reasoning 6,731) To continue this session, run codex resume 019cf359-5a7f-7491-80f1-0ad22c5d6941 ubuntu@miopenclaw-vnic:~$ codex resume 019cf359-5a7f-7491-80f1-0ad22c5d6941 ╭─────────────────────────────────────────────╮ │ >_ OpenAI Codex (v0.107.0) │ │ │ │ model: gpt-5.4 xhigh /model to change │ │ directory: ~ │ ╰─────────────────────────────────────────────╯ Tip: New 2x rate limits until April 2nd. › hello ■ Conversation interrupted - tell the model what to do differently. Something went wrong? Hit `/feedback` to report the issue. › hey, I just wasted a bit of time because I had my pixel 6a as tailscale tunnel for this VPS I guess? thing is, this same tailscale account has another exit node which is my computer, so can't we idk use that as the tailscale exit node as kind of a fallback? or if anything the pixel 6a as a fallback? i do not dig having to keep the phone on at all times tbh, but I might whip this computer out for working on personal projects which I need to have access to the internet if I want to move forward yk? • Yep — with one important caveat. Short Answer - You can absolutely have both your computer and your Pixel 6a advertised as exit nodes on the same tailnet. - Your VPS can use an exit node from either one, but normally it uses one selected exit node at a time. - If that selected node disappears, traffic through that exit node breaks unless you switch manually — unless you use Tailscale’s newer auto:any behavior. What Counts As “Fallback” - As of Tailscale’s CLI docs validated on January 26, 2026, tailscale set --exit-node=auto:any can track the suggested exit node and automatically switch when available exit nodes or network conditions change. - So yes, that’s basically the closest thing to fallback for your VPS. - But I don’t see a documented “desktop first, phone second” priority list; the documented auto mode is recommendation-based, not an explicit primary/backup order. Best Setup For You - Use your computer as the main exit node if you can keep it awake; that’s way better than depending on the phone. - Keep the Pixel 6a only as emergency backup if you want, but Tailscale’s docs say Android exit nodes are still being optimized, are userspace-only, and may be too slow for many cases. - If your computer sleeps, it stops being a useful exit node, so “awake and plugged in” matters. One Gotcha - Tailscale’s “recommended exit nodes” docs were last validated on January 7, 2025 and still say that feature is for Starter/Premium/Enterprise or Mullvad add-on. - So safest read: current clients support the auto:any flag, but whether the smart auto-selection works for your tailnet may still depend on plan. Practical Commands - List exit nodes: tailscale exit-node list - Use automatic selection if supported: sudo tailscale set --exit-node=auto:any - Or pin the desktop manually: sudo tailscale set --exit-node= - https://tailscale.com/docs/reference/tailscale-cli - https://tailscale.com/docs/features/exit-nodes - https://tailscale.com/docs/features/exit-nodes/auto-exit-nodes • I found two usable exit nodes. Next I’m checking whether auto-selection is available here. • The client supports auto:any; I’m checking which exit nodes Tailscale currently sees and suggests before changing anything. • Tailscale currently recommends the desktop, which is ideal. I’m switching this VPS to automatic exit-node selection now.