-
Notifications
You must be signed in to change notification settings - Fork 401
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
New deployment failed #227
Comments
I just discovered this issue on my first attempt. Including Images, you also have to subscribe to Workers Paid plan. Durable Objects is only accessible in the Workers Paid plan. Based on the Readme, I had buy in with $5/month. Unfortunately, I don't have buy in to do $10/month just for Wildebeest. I'm stoked that Cloudflare is contributing to the ActivityPub community. Sorry Cloudflare team, I won't be participating. |
Thank you for the information. Unfortunately after I upgraded to a paid workers account, I ended up with the exact same error. I agree the Readme is deceptive in cost. |
Also had the same issue. Got a Workers paid tier going and activated Durable Objects. Now getting slightly different error under download terraform state heading. I'd be expecting to see the account id where the "***" is being displayed below, so the process might be dropping that variable along the way possibly? [ERROR] Failed to fetch |
@PrimeSitesCo I added a fix, could you please sync your fork? It will trigger a deploy build. |
We will work on the tutorial and clarify the required subscriptions and associated costs. |
Thanks @xtuc, sync'd from main, but it didn't trigger a deploy. Manually re-ran the job and got past that step, but failed again at the Configure step I'm afraid. Something I did wrong perhaps? |
I keep getting the same error |
Okay, let me revert my fix. Sonds like it's something else. Have you tried to delete your KV namespaces starting with |
Hi there - I've tried this, and it doesn't fix the problem. What I've been able to figure out thus far is that the default "Cloudflare Workers" API Token template lacks the permissions necessary to fully deploy the Terraform template. Unless I'm overlooking something obvious, I don't believe any of the repo documentation mentions the CF API token permissions necessary for deployment. It may help to start there. |
During the latest attempt I was able to get as far as this error message (see image): Of note, I have no rulesets on this account (0 across all zones), and the target zone is on the Pro plan. By this point in the TF run the following items have already been configured: Images variants, metadata 2 KV namespaces, D1 instance, DO, Pages project, DNS record, and Zero Trust application. |
We are working to rewrite the README to provide better documentation and troubleshooting. @DataDrivenMD Once Terraform created some resources. I strongly recommend not deleting anything manually. Resolving the permission / I asked internally about your |
I re-synced and opted in to the pay-as-you-go plan and when I re-run the job I am still getting the same message:
The latter link ( |
The magic link didn't work for me initially, which is why I ended up using the Workers Template. I wiped everything, disabled my browser's 3rd-party cookie blocker, then attempted Deploy to Cloudflare Workers button again-- that solved the API key issue.
Yeah, I'm not touching anything once it is created unless I'm removing all resources before starting over from scratch.
FWIW/FYI @xtuc: one of my earliest attempts didn't encounter this error at all, and successfully produced a managed ruleset. I deleted that ruleset between attempts. Could it be that the now-deleted rulesets are still being counted against my account? If so, then I suspect others will eventually hit this roadblock, too. |
@koehn: I ran into this issue earlier
The fix is to replace the *** with your CF account number, drop that into your browser URL bar, and you'll be prompted to agree. IOW: |
@xmflsct I can confirm that I am on the new managed rule interface |
@DataDrivenMD sorry deleted my previous message. Digged a bit more, you should have deployed managed rules already in that target zone. If that is the case, for now a workaround is to remove Terraform's config of managing WAF like this commit. |
@xmflsct I don't have any deployed rules (at all). I'm happy to deploy the managed rules, but I believe that TF directive yields an exception to the managed rulesets. So, unless I'm misunderstanding the TF directive, the workaround would remove the bypass and thereby block ingress traffic to the |
OK, just made sure my repo was sync’ed, enabled DO, Enabled Access, and now this error in the “Download Terraform State” task:
|
@koehn Encountered this one, too. It happens because there's no |
I encountered simillar situation. I tried deployment but GitHub Action failed due to payment approval. Then I approved payment and re-run action to fail. Situation is getting better when I removed all of related KV. Currently I got error:
What should I do? |
Just did this, thank you. New error: So... I did this |
That is likely you have deployed rules in the past through the dashboard UI, hence an entrypoint ruleset had been automatically created by the UI behind the scene. Tested that you need to call the API https://developers.cloudflare.com/api/operations/zone-rulesets-delete-a-zone-ruleset to delete that entrypoint ruleset, then it can be managed by Terraform. |
It's been re-branded as "Zero Trust" (see image): |
To delete ruleset (requires
Look for the
|
The workaround for the first error:
For the second error, see @koehn's response ^^ but also see my earlier response to him regarding deleting the KV Namespaces, DNS Records, Pages Projects, etc. Once you do that, re-run the failed GH Actions job and cross your fingers |
ruleset are a bit in a weird state because the UI in the dashboard hasn't shipped yet so only way is to use the API. |
Thanks for trying @DataDrivenMD. It helps us improve the documentation and deployement process. |
Thanks for being so responsive- that's what kept me going tbh. This is a great project, and happy to help smooth out the wrinkles. |
@DataDrivenMD Everything worked well. Thank you very much for great application! I'll create account. |
Thank you. I am new to CF, I don't know what that means, so for anyone reading this, it's under Workers: I needed to delete things in Overview, KV, and D1. Yet again ran into another error after a new re-deploy, looks like the same one other folks have been getting.
Re-ran the deploy, it failed again. Went back to the dashboard and deleted everything, again. This time there was a DNS record for the domain, deleted it too. and... it failed again.
|
^^ The workaround for that last error is here: #227 (comment) |
Thanks, @DataDrivenMD. Made it to a successful deployment in the end following the Starting Over guide. Opened the Mastodon app on a mobile and managed to get through to the login interface of my new Wildebeest instance, but when I hit the register button I got a "Worker exceeded resource limit" error. Signing out of the Mastodon app and back in, now shows that it requires authorisation, which is the step that gives that Worker exceeded resource limit error. |
@PrimeSitesCo can you please double check that Worker is set to unboud in Pages? If not, it requires a deployement to apply. |
@xtuc accessing either of the wildebeest-consumer-xxxxx and wildebeest-do workers show the little Unbound icon top-right. |
@PrimeSitesCo yes. The What client are you using? Official Mastodon app on iOS? |
Yes, first used it with Mastodon, but also tried Tooot and got the same issue. |
@PrimeSitesCo it is under Pages that you need to set functions to unbound, see https://github.com/cloudflare/wildebeest#error-1102 After changing the setting of Pages, you need to re-run the last GitHub deploy action to let the new settings apply |
Thanks @xmflsct, that did the trick. |
Just seeing this message now, great to see that you found a fix @PrimeSitesCo |
I apologize if this was already covered. I tried finding how to fix this, but I'm not seeing anything specific about this. I am running in to |
this presumes a great deal. I do not use Cloudflare. I do not interact with it with CLI. This makes no sense. Am I hearing that for me to be able to deploy Wildebeest, I need to setup some other environment just to delete CF's mistakes? |
I share your frustration. I don't work for CF, I'm just trying to help; I wish I could do more. |
Thanks, I'm just deleting my paid services from CF. This isn't turn key and is arguably harder to manage versus deploying Mastodon in a VM. |
@yawnbox thanks for trying, we are improving the deployment process and documentations. I'll go ahead and close the issue for now. |
I tried deploying just this morning (Feb 19) and I am still getting "Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2.". I tried "Sync Fork" and I am not behind the upstream branch. |
I see in your logs:
Please agree with the pricing and retry. |
I've spent tons of time trying to deploy, and failing over and over again. I first deployed without agreeing to use DO, because it wasn't at all clear from the instructions here that I needed to do that in advance. But now, I've started paying $5/m to Cloudflare workers, which I think means DO should be enabled (the ?enable-durable-objects link doesn't do anything special for me - and I am correctly changing it to have my account ID). I also tried deleting the D1 database before a new deploy, didn't work. Couldn't figure out any other things I should delete to try and make this work.
|
OK, turns out that paying for Cloudflare Workers did not actually enable DO. I managed to get link to work and bring up modal asking to agree to DO (which didn't come up before, even using that link). Got past DO part of deployment. Now failing here: │ Error: failed to create DNS record: Authentication error (10000) Going to try delete DNS records then attempt deploy again. |
Like you, I'm now paying for Cloudflare Workers, but don't appear to have DO enabled. How did you fix this? The link in the error message doesn't work for me - I just get a 404. |
@maxtappenden are you putting your Cloudflare user ID in the URL in place of ***? |
No! 😳 Didn't notice it. I only looked at the domain and the query string 😁 Thank you! |
Regarding getting past the durable object error you gotta go here and scroll to the bottom of the page and click enable durable object (make sure the replace the account id and worker name. https://dash.cloudflare.com/accountId/workers/services/view/myWorker/production |
I setup a new Cloudflare account, followed the directions...
Github job (deploy_to_cf_workers) failed with a warning:
Overall I would say deploying Wildebeest is not any easier than deploying Mastodon on a VM.
The text was updated successfully, but these errors were encountered: