Posted: February 9, 2021 at 6:07 am
Earlier today we moved our site to Kinsta Managed WordPress hosting service (we already host plenty of sites there with success).
After the migration, we QAed the site and found out that it was not working properly. We had to switch the IP back to the old host.
Before describing the issues, I am listing here the cache exclusion rules that we had already applied on the new server.
Also, our payment provider is Authorize.net.
Our EE is Version 4.10.10.p
The primary issue is that the checkout did not work. We did 2 separate checkout attempts and we received the following:
Also, we had another issue, which led us to disable cache for all Events pages.
If I added 0 tickets to the event cart, the page had to reload and show the following message:
This sounds correct, Kinsta’s nginx server was caching it. As a result, all guest visitors would see this message if another person had previously hit this button with 0 tickets.
So, we had to exclude all /events/xxxxx URLs from the cache, which fixed the issue. This is not ideal (we do want to cache as much as possible for better performance), so I would like to ask if there is a cookie that is set by Event Espresso at this action so that we can exclude this specific cookie from the cache.
I have reached Kinsta’s support for all this. They are happy to help but they are saying they do not have issues with other clients running Event Espresso.
So, at this point, I am not sure where to start in order to debug this.
Please let me know if you can help.
Thanks in advance
While Event Espresso doesn’t set its own cookies for the session, it does make use of PHPSESSID. So if that’s something that can be allowed to be unique per each visitor that should allow the registration process to work as expected.
Hello Josh, thanks for getting back.
According to this article
it seems like this is not going to work with Kinsta hosting, correct?
What confused me is that I have read in your forums that there have been clients who host Event Espresso on Kinsta.
Also, Kinsta lists Event Espresso as a plugin recommendation in their blog.
Is there something that I am missing here?
Maybe you could double-check this technical compatibility issue and either make them compatible or just mention in your “Compatibility” page that the plugin is not compatible with their hosting environment.
Thanks in advance.