Skip to content
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

Troubleshooting steps are missing something #341

Open
sterlingwes opened this issue Feb 25, 2023 · 2 comments · May be fixed by #342
Open

Troubleshooting steps are missing something #341

sterlingwes opened this issue Feb 25, 2023 · 2 comments · May be fixed by #342
Assignees

Comments

@sterlingwes
Copy link

I had a bunch of errors with the one-click deploy and found the other issues indicating I should reset with your troubleshooting docs. I followed all the steps there and now my action errors with this:

Screenshot 2023-02-25 at 4 17 13 PM

I'll dig through the code and figure out what the value of this GH action secret should be but wanted you to know the troubleshooting steps for resetting state seem to be missing something

I noticed that the setup UI at https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/wildebeest&authed=true doesn't ask for my domain or instance name, etc. anymore, even with a browser cache reset so not sure what happened there or if it's related

@sterlingwes
Copy link
Author

Worked when I added the following to https://github.com/YOURUSERNAME/wildebeest/settings/variables/actions

  • ADMIN_EMAIL
  • CF_DEPLOY_DOMAIN
  • CF_ZONE_ID
  • INSTANCE_TITLE
  • INSTANCE_DESCR

@sterlingwes sterlingwes linked a pull request Feb 25, 2023 that will close this issue
@CyberFlameGO
Copy link
Contributor

CR - deleting my original fork (which was created before there was much content in the repo) seemed to fix it for me but I think a documented solution would be better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants