Tailscale script - no option to install on Proxmox VE host as stated #831

Closed
opened 2026-02-04 21:47:08 +03:00 by OVERLORD · 6 comments
Owner

Originally created by @jhedfors on GitHub (Apr 18, 2025).

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Tailscale

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/add-tailscale-lxc.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

The instructions state:
You can use it inside a running LXC container or directly on the Proxmox VE host to extend functionality with Tailscale.
Yet the only options presented in the script are to install on a selected LXC.

Either the instructions are incorrect, or there is an issue with the script.

🔄 Steps to reproduce the issue.

  1. Ran script
  2. Only presented option to install onto a list of LXC containter, and no host option.

Paste the full error output (if available).

n/a

🖼️ Additional context (optional).

No response

Originally created by @jhedfors on GitHub (Apr 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Tailscale ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/add-tailscale-lxc.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. The instructions state: `You can use it inside a running LXC container or directly on the Proxmox VE host to extend functionality with Tailscale. ` Yet the only options presented in the script are to install on a selected LXC. Either the instructions are incorrect, or there is an issue with the script. ### 🔄 Steps to reproduce the issue. 1. Ran script 2. Only presented option to install onto a list of LXC containter, and no host option. ### ❌ Paste the full error output (if available). n/a ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-04 21:47:08 +03:00
Author
Owner

@MickLesk commented on GitHub (Apr 18, 2025):

The text means you can run it on the main node or in the LXC. There is no option on the Proxmox main node

@MickLesk commented on GitHub (Apr 18, 2025): The text means you can run it on the main node or in the LXC. There is no option on the Proxmox main node
Author
Owner

@jhedfors commented on GitHub (Apr 19, 2025):

@MickLesk

The text means you can run it on the main node or in the LXC. There is no option on the Proxmox main node

OK. I did understand it that way at first, but thought I was mistaken as when I tried to use the script in the LXC, it failed.

At the section where it asked to select the container, it showed nothing to select but "OK". Selecting that just then showed the command prompt for that LXC.

Should I open a separate issue for that?

Image

@jhedfors commented on GitHub (Apr 19, 2025): @MickLesk > The text means you can run it on the main node or in the LXC. There is no option on the Proxmox main node OK. I did understand it that way at first, but thought I was mistaken as when I tried to use the script in the LXC, it failed. At the section where it asked to select the container, it showed nothing to select but "OK". Selecting that just then showed the command prompt for that LXC. Should I open a separate issue for that? ![Image](https://github.com/user-attachments/assets/9bf30b1f-72cf-4e5e-ad7d-42a207ceaccd)
Author
Owner

@MickLesk commented on GitHub (Apr 19, 2025):

Yep as Task

@MickLesk commented on GitHub (Apr 19, 2025): Yep as Task
Author
Owner

@tremor021 commented on GitHub (Apr 19, 2025):

@MickLesk Is this for @BramSuurdje ? Then InstallCommand.tsx should be corrected to not say where command should be ran, rather explained in warning or info box.

@tremor021 commented on GitHub (Apr 19, 2025): @MickLesk Is this for @BramSuurdje ? Then InstallCommand.tsx should be corrected to not say where command should be ran, rather explained in warning or info box.
Author
Owner

@burgerga commented on GitHub (May 5, 2025):

Accidentally commented on the pull request, but it makes more sense here. Additional changes might be needed because now there is conflicting/confusing information:

Image

EDIT: I see what @tremor021 means now, thanks for the clarification @MickLesk!

@burgerga commented on GitHub (May 5, 2025): Accidentally commented on the pull request, but it makes more sense here. Additional changes might be needed because now there is conflicting/confusing information: <img width="980" alt="Image" src="https://github.com/user-attachments/assets/591e44f7-6b55-4a2d-b1bd-a873cf855f74" /> EDIT: I see what @tremor021 means now, thanks for the clarification @MickLesk!
Author
Owner

@MickLesk commented on GitHub (May 5, 2025):

@MickLesk Is this for @BramSuurdje ? Then InstallCommand.tsx should be corrected to not say where command should be ran, rather explained in warning or info box.

yep, as dirty fix, you can write him in discord and link to this. (addon and pve type)

@MickLesk commented on GitHub (May 5, 2025): > [@MickLesk](https://github.com/MickLesk) Is this for [@BramSuurdje](https://github.com/BramSuurdje) ? Then InstallCommand.tsx should be corrected to not say where command should be ran, rather explained in warning or info box. yep, as dirty fix, you can write him in discord and link to this. (addon and pve type)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#831