tailscale / tailscale/github-action
GitHub Action Failing with Error in Tailscale Setup
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
The TS_OAUTH_CLIENT_ID and TS_OAUTH_SECRET secrets are confirmed to be set correctly, as indicated by the "Debug Secrets" step.
The error occurs specifically during the "Set up Tailscale" step.
Please provide guidance on resolving this issue or suggest modifications to the workflow to ensure it works correctly.
on:
push:
branches:
- main
jobs:
connect:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: Debug Secrets
run: |
echo "Checking TS_OAUTH_CLIENT_ID"
if [ -z "${{ secrets.TS_OAUTH_CLIENT_ID }}" ]; then
echo "::error::TS_OAUTH_CLIENT_ID is empty"
exit 1
else
echo "TS_OAUTH_CLIENT_ID is set"
fi
echo "Checking TS_OAUTH_SECRET"
if [ -z "${{ secrets.TS_OAUTH_SECRET }}" ]; then
echo "::error::TS_OAUTH_SECRET is empty"
exit 1
else
echo "TS_OAUTH_SECRET is set"
fi
- name: Set up Tailscale
uses: tailscale/github-action@v2
with:
oauth-client-id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
oauth-secret: ${{ secrets.TS_OAUTH_SECRET }}
# tags: tag:ci
version: 1.52.0
- name: Verify Tailscale connection
run: |
tailscale ping <IP ADDRESS>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the provided workflow, especially the Debug Secrets and Set up Tailscale steps using tailscale/github-action@v2. Reproduce the failure on the Set up Tailscale step and inspect the linked screenshot or action logs for the actual error. Done means identifying the cause and documenting or applying a workflow change that allows the Tailscale connection step to complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100