Luadns plugin no longer works, Adding TXT Entry: 403

Hi there,

I know that I am not leaving any context or logs, but my question is pretty simple. Everything after my question is just an explanation of why I am reaching out.

*** Has anyone tried and successfully used the certbot luadns plugin to create a cert (staging or otherwise) since 06/24/2024? ***

I ask because initially I couldn’t get the plugin to work, but that was because I had not enabled API access in General Settings on luadns.com yet, doh.

I realized my mistake a few days later, and setup 4 different certs successfully using certbot and Proxmox. That was on 06/20/2024, and life was good. I was ready to start creating certs for all my servers.

However, on 06/24/2024, and today as well. When I run the same command as I did for my successful run of the certbot luadns plugin, I get a 403 error when it is Adding TXT api call. I tried on the system that was successful on the 20th with staging and I get the same result now, yet I had changed nothing since it worked. Looking at the logs other API calls to Luadns are successful.

I tried creating a new API key but I have the same result.

I have the log from when it was successful, and plan to compare it to the failing run, hopefully I can figure out what is wrong, but to be honest my Python skills may not be that good to dig through the plugin.

Anyway thanks in advance to anyone who can let me know if they are seeing a similar issue.

Welcome @echo9
Just for clarity ... in both cases (worked and failed) are you talking about the built-in luadns plugin for Certbot?

Because your title says Luanda plugin.

https://certbot-dns-luadns.readthedocs.io/en/stable/

2 Likes

That’s what I get for writing my message on a phone. I am sorry. I should have proof read the message better before I sent it.

Yes the certbot luadns plugin. I’ll edit the message if possible.

Thanks for letting me know.

3 Likes

Thanks. You should probably contact lua if you haven't already. Perhaps they have logs that describe the problem better.

GoDaddy recently restricted their DNS API for many customers giving a similar problem. Perhaps lua has done the same?

That Certbot plugin is rarely seen on this forum so don't be surprised if no one responds.

Another option is to try a different ACME Client. The acme.sh client supports LUA and is a shell script. Do you know that better than python? acme.sh/dnsapi/dns_lua.sh at master · acmesh-official/acme.sh · GitHub

1 Like

Yeah, bash and sh I have been using and writing for 20 years. The python stuff is just too many classes and imports for me to follow along (at least for the level I am at). I really appreciate the suggestion @MikeMcQ that's a great idea. If the shell script doesn't work correctly, I will know where the issues lie. Alright off to go check it out. Have a good one!

2 Likes

It finally occurred to me that this could be a limit of my free account. I finally checked the luadns side again, and found I had used the 30/30 records that I can have for the free account. Hopefully this helps anyone else who may run in to the same issue in the future.

Thanks again everyone for the help

:slight_smile:

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.