Hello Chiara

On which pages do you see this error?

Please provide me a temporary WP-admin login for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course we do not provide login data to third party. You can write credentials here just check Private Reply so nobody can see them except us.

Hello Chiara

Sorry for the delay, we're working from 08:00 - 16:00 CET, and we go through tickets in the order in which they are received, or responded to. I've had quite a lot of tickets that came in before your response, so I just got to this ticket.

Unfortunately, I can't log in with those credentials:

The error on the page seems to be generated by Autoptimize plugin (see attachment). Please try turning off that plugin, and delete cache from your website. Let me know if that helps.

As soon as you check the log-in credentials, I'll remote in and take a look if it's not caused by Autoptimize.

Hello again Chiara

There's a strange error message on the front-end page:

message: "SQLSTATE[42000] [1203] User antoniol_kikyoga already has more than 'max_user_connections' active connections"

I've never seen it before, but I don't think it's coming from Amelia. The issue has been forwarded to our developer for testing. As soon as I hear from him, I will let you know.

Hi again Chiara

This has something to do with the configuration of your database.

It's allowing 1 - 2 logins per session. When Amelia triggers a few calls to the server, in the same moment it's trying to connect to the database with the same user, and this limit is blocking it.

In incognito window, I can see the events page load (see attachment)

Can you please reach out to your hosting provider, and ask them what's the value of the variable max_user_connections? They should be able to increase it. For us to make it work through the plugin, we would need to create a call for the entities, then when that's returned create a call for events, then when that's returned - for users. This occurs on front-end as well as on the back-end, and I doubt that our management would go for a change this big.

Hello again Chiara

Unfortunately, the change we would need to add to the plugin would require changing the logic of Amelia, so calls are made one after another, not at the same time.

That requires a lot of coding, and it simply can't be done. I can completely understand if you would like to receive a refund because of this issue, but most booking plugins work in a similar way, so most likely you will face this issue again until you switch to a dedicated hosting.