-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
Update Dynu code and .ini file #483
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this pull request! Be sure to follow the pull request template!
dynu is a different plugin and it's abandoned |
I am a bot, here are the test results for this PR:
|
According to docker logs
|
I am a bot, here are the test results for this PR:
|
I'm also using dynudns and can confirm these changes have to be made to be able to use the dynu plugin. |
I am a bot, here are the test results for this PR:
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Description:
Running SWAG for the first time I got errors while setting it up to work with Dynu DNS challenge. The code for
DNSPLUGIN
flag was wrongly named and the .ini config file had the wrong name.Benefits of this PR and context:
If it's not fixed, every single Dynu DNS user will have to make the same adjustments.
How Has This Been Tested?
I kept making adjustments to
docker-compose.yml
and the filesystem until there were no errors shown.Source / References: