-
-
Notifications
You must be signed in to change notification settings - Fork 248
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
[BUG] 2.7.0 - Please set the DNSPLUGIN variable to one of the following, works reverting to 2.6.0 #414
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Can replicate. looking into it. |
Thank you! Let me know if I can be of any help. |
I am having the same issue as cohenchris reported. Only difference is I'm using 'cloudflare'. Let me know if I can be of help. |
confirmed using cloudflare plugin and issue presenting the same |
having the same issue with DNSPLUGIN set to |
Please test the |
Still have the issue with lspipepr/swag:2.7.0-pkg-5e0cdeca-dev-49f6fb2b6eef1691264d25b1b9b194ff708144a5-pr-415 and lspipepr/swag:2.7.0-PR-415 with cloudflare and deploy with Portainer, I test 6 different version and still have the Please set the DNSPLUGIN error. Im running a VPS server in Hostinger and trying to set swag for reverse proxy. |
Please update to a more recent version, this was fixed after 2.7.0. Also ensure that the running container is actually using the version that you expect. This issue popped up again for me, and I found that I was running version 2.7.0, when I thought I was running a later version. |
VALIDATION=dns
DNSPLUGIN=google-domains Edit: If running a previous version then updating to after 2.7.0, recreating the config volume solved this issue. |
Switched to latest and appears to be working for me. Thank you!
|
Hello ! I remove the cli.ini file and restart without any modification and that work well, I dont Understand why my file was corrupted but that work now, thanks you all ! |
I have 2.8.0 and still have the issue with dynu. I noticed this in the release note: Freezing here: I need dynu as they provide TXT and CNAME records for free. Thanks. |
Dynu has been removed from swag. |
Sad to hear that... Not considering adding it back? (2.6.0 works with it perfectly, just tried it) |
The plugin author has abandoned the project and it no longer works with the versions of dependencies that all other plugins need, which is why we removed it. |
Where is that plugin? I'd look into it, perhaps can be taken over and updated. |
Too bad, I wanted to switch from my own setup to using swag. But I'm using Dynu and moving to a different DDNS is not an option for me. For now I am using ACME.sh in my setup, they have a working Dynu plugin, maybe this can help somehow? |
Unfortunately not, certbot and acme.sh using different plugin systems. |
Ok. Without Dynu support swag is useless for me. :( |
I thought I had stumbled over this part but somehow didn't find it again. |
Installing it breaks all other up-to-date plugins. |
Dynu has created a ticket to take over the project and update the dependencies but until such time we take it over. We will release updated version of the plugin as soon as project is claimed. |
Glad to hear that! |
We have been unable to take over the project since no one has been assigned to the ticket. We have created a new project below. Can someone please add support for Dynu in Swag again? |
I am experiencing the same issue using any version including latest. Container exits with Log File:
Fixes Attempted:
Edit: Resolved - the container was not allocated enough memory so that when running the certbot command would cause it to crash without any log or error other than outputting "Killed" when typed into the container CLI manually. |
Hi. |
If you're running old hardware, that's likely the problem. #469 |
Your issue is likely unrelated to this one, please open a new issue and provide the necessary information. |
Thanks for the hint, I had the same issue on latest, and removing \etc\letsencrypt\cli.ini and restarting container solved it. |
Is there an existing issue for this?
Current Behavior
After the most recent update, my reverse proxy does not work with porkbun (at least).
My docker container gives me an output listing the environment variables set, and then this message:
"Please set the DNSPLUGIN variable to one of the following:"
There is no further output. I have reverted to version 2.6.0 and everything works.
Expected Behavior
Reverse proxy container starts and handles traffic.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
"Please set the DNSPLUGIN variable to one of the following:"
The text was updated successfully, but these errors were encountered: