Error while creating worker project about unifi-ddns HOT 14 CLOSED

I got stuck with the same issue but I went to "Deploy" under workers and edited. I didn't actually do anything I just deleted lines and added it back. When you commit the changes it auto deploys and it worked.

from unifi-ddns.

I also solved it by editing the deploy.yml (just add some empty lines and delete them) on my github page and re-executing the "Deploy the Worker" step.

Thx @BovBrew !

from unifi-ddns.

i solved by editing my deploy.yml as well- make sure your api key/account info is correct (the worker deployment workflow might not properly insert the values for you when you initiate the fork)

from unifi-ddns.

@Rubeast The PR I made was merged, so you should be able to just run the workflow manually from the Actions page now. You'll see a notice and button that look like this:

from unifi-ddns.

I checked the actions in Github and no action was created. I have now added the action manually in Github (action -> new workflow) and inserted the code of the deploy.yml. Now I see two workflows in Github.

Under Cloudflare Workers & Pages "unifi-cloudflare-ddns" was created. Does this correspond to what the Click to Deploy process should do?

from unifi-ddns.

I too get the same "Project had an error" when deploying, The API did not have a worker option by itself, there were several worker options for the API so I added them all just to test. I followed all the instructions listed and do not know where to go from here.

from unifi-ddns.

I wonder if this is somehow related to the repository name not being the same as the worker name. I assume the "Deploy with Workers" tool does some initial manual deployment since the action would not ever run immediately after being activated once forked.
The message says:

Congratulations, unifi-ddns is now deploying!

However, the actual package name is unifi-cloudflare-ddns:
https://github.com/workerforce/unifi-ddns/blob/f9f695ab9599c2271b405def96360196d5533071/wrangler.toml#L1

from unifi-ddns.

I am also getting this error. The JSON response that comes in when error appears is:

{
  "message": "Not Found",
  "documentation_url": "https://docs.github.com/rest"
}

Not sure what to do from here but I have been trying for several days with no luck. Any help would be much appreciated.

from unifi-ddns.

I checked the actions in Github and no action was created. I have now added the action manually in Github (action -> new workflow) and inserted the code of the deploy.yml. Now I see two workflows in Github.

Under Cloudflare Workers & Pages "unifi-cloudflare-ddns" was created. Does this correspond to what the Click to Deploy process should do?

I did this same thing. Deleted the one I created and it was mostly working from there. I created one with no content just a worker that did nothing and it worked fine after that. Something must have changed with GitHub and how workers are enabled.

from unifi-ddns.

Also unable to use the Click to Deploy option

from unifi-ddns.

Was not able to get the click to deploy to work either. There was no information on the error either. when i went to actions it shows no runs yet.

so i tried the wrangler option and deploy gave an errror the entry-point file was not found.

so i tried wrangler dev and that created some files and when i opened in a browser it gave an error to use https even though it was using https. after that deploy worked but every time i visit the worker through cloudflare it use shows not found.

i'm probably doing something wrong but have no idea where to start or look.

from unifi-ddns.

It seems like the solution is to just add workflow_dispatch to the workflow so that you can manually run the deployment once. Having users manually edit a file just to force a workflow to run seems like a recipe for disaster if they ever want to contribute back to this repo from their forks.
@willswire It's a one line change, but I opened a PR since this issue has already been closed

from unifi-ddns.

Yeah. I don't understand why it is being marked as completed. What we had to do is more a workaround.
@willswire, are you expecting that every user needs to edit the deploy.yml file?

from unifi-ddns.

The PR by @MatthewA1 should fix this. Users shouldn't need to edit the deploy.yml file, but they will need to set their own API key and Account ID in their GitHub project fork's settings (under Actions secrets and variables)

from unifi-ddns.