Error in latest version lexicon.exceptions.ProviderNotAvailableError?

[frankhommers]

I got the lexicon.exceptions.ProviderNotAvailableError in the latest version.

Exactly the same config works in dnsrobocert:3.12.0 so when I run that docker image it did work.
I am using the transip provider.

I guess something must be wrong in the latest docker image?

[adferrand]

Hello @frankhommers!

Yes I am really sorry for the inconvenience. I was forced to remove the transip provider on Lexicon side because of security and incompatibility issues. As a temporary workaround you can stay on dnsrobocert 3.12.0, but my intention is to get back the transip provider as fast as possible.

Indeed a new REST API is proposed by TransIP, while the old XML-RPC is deprecated and planned to be decommissionned in few months. However I need valid credentials to build the new provider on the new API. If you have some, it would be really kind from you to lend them to me for the time of the implementation.

If you agree we can setup a secured channel to share these credentials.

[DotOnedotNL]

Any progress on this?
I ran into the same issue. reverting to 3:12.0 works for now but surely isn't a sustainable solution.

[frankhommers]

I have put my DNS records elsewhere, so currently no need for me.

Maybe you (@DotOnedotNL) can share your credentials with @adferrand for testing.

[DotOnedotNL]

@adferrand I'm open working with you to get the transip working again.

[adferrand]

Hello @DotOnedotNL that is great ! We need to setup a secured channel to share credentials and other sensitive informations. Do you have Signal or WhatsApp for instance ?

[DotOnedotNL]

Hi, Hi, you can read me on Signal, or Telegram Regards, Andre On Sunday, January 09, 2022 13:03 CET, Adrien Ferrand ***@***.***> wrote:     Hello @DotOnedotNL that is great ! We need to setup a secured channel to share credentials and other sensitive informations. Do you have Signal or WhatsApp for instance ?