This is a pretty strange situation! I second @Osiris’s request for more information about your Plesk setup - I think something has gone quite wrong with the ACME client that your system is using.
When I look at the server side logs I can see that the
ApBI0gD3x9st2KZHAro8LSka3SpJmhaJI-TOIhXB4FY authorization you mention was created on 27/02/2019 at 11:34:50 UTC by the account ID 52315893. Two seconds later that same account successfully POSTed the authorization’s HTTP-01 challenge and the challenge succeeded so the authorization is now valid
The problems start at 11:35:12 UTC that same day. A different account ID with the same contact address (ID: 52315900) started to try and POST the challenge on that authz. That’s broken for two reasons:
- The authz is already valid, so there’s no challenges that need to be done.
- Its the wrong account and doesn’t own the authorization so the error you’re seeing is returned.
Over the past 3 days I can see there were close to ~8 different ACME account IDs that tried to POST this challenge after it was already valid.
With all that technical information out of the way: I think you should try and contact Plesk support and find out what could be causing your server to get confused like this. It seems like it’s creating new ACME accounts over and over but is also remembering authorizations it previously created. Unfortunately I’m not familiar with Plesk to guess at a root cause It smells like a bug in the Plesk ACME client.
Hopefully some of the information in this thread will be helpful to Plesk support (or perhaps someone else can guess at the root cause with the server-side information I provided in hand).