-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invalid value "nas1" for --exit-node; must be IP or unique node name #123
Comments
I ran into this as well, no matter what I do I cannot get the action to come up and assign an exit node so I broke it up into two different actions in the yaml file. Would be interesting to know if this is by-design and if so, could it be documented? - name: Tailscale
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.TS_OAUTH_CLIENTID }}
oauth-secret: ${{ secrets.TS_OAUTH_KEY }}
tags: tag:ci
#args: "--exit-node=nas1" #using this we get an error: must be IP or unique node name
- name: Tailscale - ReRun Up Command To Set ExitNode to pfsense
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.TS_OAUTH_CLIENTID }}
oauth-secret: ${{ secrets.TS_OAUTH_KEY }}
tags: tag:ci
args: "--exit-node=nas1" |
FYI I found the reference issue explaining why this happens (again, I really think this needs to be documented somehow in the github action itself as it seems like anyone wanting to use this action would probably have to deal with the problem). |
FYI you can just run an additional
|
I am trying to use
tailscale/github-action@v2
Github action. You can find my Github action code belowHowever, when running above action, I am getting error
invalid value "nas1" for --exit-node; must be IP or unique node name
I can successfully run Tailscale using
nas1
as exit node when using Tailscale CLICould you guide me on how to debug this issue, please?
The text was updated successfully, but these errors were encountered: