Replies: 2 comments
-
Thank you, the wildcard domain helped me immensely. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm stuck at the very first step. Docs say to "Deploy the Worker", but when I click the link, I'm asked to log in with my user name and API Token. Unfortunately there's no explanation of where this API Token is supposed to be from. I tried creating the DNS Zone Editor token described in the next step, but it's not accepted. So how did you handle this? Do I need to create a different API Token just to get started? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I ran into a few issues and took me about a week to troubleshoot and fix them all. Since documentation is limited I wanted to offer my experience in case someone has similar problems.
Starting with installation. I was getting an error when running the
Deploy Workers
script. I found out that the GHA was not running from the forked repo. To force the run all I did was edit hedeploy.yml
file (added a space and then removed it). That triggered the workflow and it installed the worker in CF.I have a UDM SE and had to remove the
https://
from the server field as it was not workingI have a wildcard DNS entry and a root domain entry. To update both at he same time you can add a list of comma separated domains to the Host field like
domain.com,*.domain.com
. Make sure you have no spacesSome said that
dyndns
is missing from the UDM but it's there for me in my UDM SE running network application 8.0.28. According to some, if you are missingdyndns
you can usedyn
. Have not confirmed this.If you want to test this script you have a few options
inadyn
(easiest but needs SSH). See hereProxied DNS works fine with his
Beta Was this translation helpful? Give feedback.
All reactions