Skip to content
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

Closed
1 task done
cohenchris opened this issue Oct 3, 2023 · 32 comments · Fixed by #415
Closed
1 task done

Comments

@cohenchris
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

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

  1. Update to the most recent version of swag, as of October 3, 2023
  2. Run the docker-swag container
  3. Observer the output listed above

Environment

- OS: Arch Linux
- How docker service was installed: distro's package manager

CPU architecture

x86-64

Docker creation

docker-compose up -d

Container logs

"Please set the DNSPLUGIN variable to one of the following:"
@github-actions
Copy link

github-actions bot commented Oct 3, 2023

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@cohenchris cohenchris changed the title [BUG] Please set the DNSPLUGIN variable to one of the following [BUG] 2.7.0 - Please set the DNSPLUGIN variable to one of the following, works reverting to 2.6.0 Oct 3, 2023
@Roxedus
Copy link
Member

Roxedus commented Oct 3, 2023

Can replicate. looking into it.

@Roxedus Roxedus pinned this issue Oct 3, 2023
@cohenchris
Copy link
Author

Can replicate. looking into it.

Thank you! Let me know if I can be of any help.

@CyberOxide
Copy link

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.

@djcath
Copy link

djcath commented Oct 3, 2023

confirmed using cloudflare plugin and issue presenting the same

@toddke
Copy link

toddke commented Oct 3, 2023

having the same issue with DNSPLUGIN set to google-domains

@Roxedus Roxedus mentioned this issue Oct 3, 2023
1 task
@Roxedus
Copy link
Member

Roxedus commented Oct 3, 2023

Please test the lspipepr/swag:2.7.0-pkg-5e0cdeca-dev-49f6fb2b6eef1691264d25b1b9b194ff708144a5-pr-415 image and report back in #415

@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Oct 3, 2023
@hodindorian
Copy link

hodindorian commented Dec 7, 2023

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.

@cohenchris
Copy link
Author

cohenchris commented Dec 7, 2023

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.

@martinmiglio
Copy link

martinmiglio commented Dec 8, 2023

Still seeing issue running on these containers:

lscr.io/linuxserver/swag:2.8.0-ls263
lspipepr/swag:2.7.0-pkg-5e0cdeca-dev-49f6fb2b6eef1691264d25b1b9b194ff708144a5-pr-415

With these variables set

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.

@toddke
Copy link

toddke commented Dec 8, 2023

Switched to latest and appears to be working for me. Thank you!

dns validation via google-domains plugin is selected
Certificate exists; parameters unchanged; starting nginx

@hodindorian
Copy link

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 !

@cybericius
Copy link

cybericius commented Dec 15, 2023

I have 2.8.0 and still have the issue with dynu.

I noticed this in the release note:
11.12.23: - Deprecate certbot-dns-dynu to resolve dependency conflicts with other plugins.
Can you please explain if it has any connection?

Freezing here:
Please set the DNSPLUGIN variable to one of the following:

I need dynu as they provide TXT and CNAME records for free.

Thanks.

@j0nnymoe
Copy link
Member

Dynu has been removed from swag.

@cybericius
Copy link

cybericius commented Dec 15, 2023

Sad to hear that... Not considering adding it back? (2.6.0 works with it perfectly, just tried it)
If not, do you have any suggested alternative that supports free CNAME and TXT records?
Thank you.

@thespad
Copy link
Member

thespad commented Dec 15, 2023

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.

@cybericius
Copy link

Where is that plugin? I'd look into it, perhaps can be taken over and updated.
It would be a huge loss, as I cannot find any other DDNS provider that gives for free both CNAME records and TXT record validation through acme...

@thespad
Copy link
Member

thespad commented Dec 15, 2023

@kinslayer1982
Copy link

kinslayer1982 commented Dec 21, 2023

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?

@thespad
Copy link
Member

thespad commented Dec 21, 2023

Unfortunately not, certbot and acme.sh using different plugin systems.

@kinslayer1982
Copy link

Ok. Without Dynu support swag is useless for me. :(

@Roxedus
Copy link
Member

Roxedus commented Dec 21, 2023

@kinslayer1982
Copy link

I thought I had stumbled over this part but somehow didn't find it again.
But now I'm confused. I thought Dynu plugin is broken. Did I get that wrong?

@Roxedus
Copy link
Member

Roxedus commented Dec 22, 2023

Installing it breaks all other up-to-date plugins.

@DustyRah
Copy link

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.

pypi/support#3520

@kinslayer1982
Copy link

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.

pypi/support#3520

Glad to hear that!

@DustyRah
Copy link

DustyRah commented Mar 5, 2024

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?

https://pypi.org/project/certbot-dns-dynudns/

@aptalca aptalca reopened this Mar 5, 2024
@aptalca aptalca self-assigned this Mar 5, 2024
@LinuxServer-CI LinuxServer-CI moved this from Done to Issues in Issue & PR Tracker Mar 5, 2024
@aptalca aptalca removed their assignment Mar 5, 2024
@aptalca aptalca closed this as completed Mar 5, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Mar 5, 2024
@crltc
Copy link

crltc commented Mar 8, 2024

I am experiencing the same issue using any version including latest.

Container exits with Log File:

Variables set:
PUID=1000
PGID=1000
TZ=America/New_York
URL=mydomain.com
SUBDOMAINS=example
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=true
VALIDATION=dns
CERTPROVIDER=
DNSPLUGIN=cloudflare
EMAIL=
STAGING=true

Please set the DNSPLUGIN variable to one of the following:

Fixes Attempted:

  • Confirm my configuration through docker is identical to the one shown on the readme
  • Included the relevant CAP_ADD
  • Have tried running as root and giving full permissions on the host volume with no luck.
  • The dns-conf folder used to be populated with .ini file examples of every provider but now when I deploy the image it does not populate any.
  • Recreated the volume entirely

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.

@gadolf66
Copy link

gadolf66 commented Apr 11, 2024

Hi.
I experience this bug on version 2.10.
Reverting to version 2.9.0 fixed the problem.
I'm using cloudflare dns plugin

@j0nnymoe
Copy link
Member

Hi. I experience this bug on version 2.10. Reverting to version 2.9.0 fixed the problem. I'm using cloudflare dns plugin

If you're running old hardware, that's likely the problem. #469

@thespad
Copy link
Member

thespad commented Apr 11, 2024

Your issue is likely unrelated to this one, please open a new issue and provide the necessary information.

@Roxedus Roxedus unpinned this issue Apr 25, 2024
@4-FLOSS-Free-Libre-Open-Source-Software

I remove the cli.ini file and restart without any modification and that work well

Thanks for the hint, I had the same issue on latest, and removing \etc\letsencrypt\cli.ini and restarting container solved it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.