Issues setting up acme.sh

Hey there,
I’m currently trying to get that shell-script implementation for acme.sh working.

I’m using this tutorial as guide:

Now my issue is, that GUI process window will vanish after “Initial validation complete”;

Leaving the job as failed - with no logs and “no errors”.

I am able to manually request certificates via acme.sh - that thing seems to be working. Might be something with GUI or this acmeShellAuth.sh script from the guide. Maybe something very basic might fail. Like permissions etc… - but for testing / debugging I’ve set everything involved to 777 which lets permissions not look like the culprit this time…

Can you give me a hint where to start searching for whats failing? Why does that progress notification gets closed without any error message?!

SCALE 25.04.1

1 Like

Known bug, supposedly will be fixed in 25.04.2. As an alternative, see:

1 Like

That guide in the OP in the linked thread is rather dated.

As it happens @dan posted further down in that thread and as far as I know, he has maintained his script.

Thanks for your replies, so GUI is indeed bugged currently, not my fault?

I’ve read somewhere, that API is deprecated and likely to be removed in future version. Which is rendering the acme.sh deployment script solution as a bit short living, since it is relying onto that WS-API.

Maybe better waiting for 25.04.2? Not sure tho.

…which is why the guide I linked you to uses the new script, which in turn uses the new API. It’s the REST API that’s deprecated.

1 Like

Ok, my bad for lack of knowledge that there are currently 2 API implementations :wink:

Creating new keys via ui/credentials/users/api-keys will get me that new ones, correct? Or are those universal keys for both APIs?

Yep.

1 Like

Thanks, will give this a try. Solved I guess.

The supported GUI method is planned to be fixed in 25.04.2 which is expected to be released within 2 weeks.