Hello @sulfsby,
Thank you for the details. Since Masteriyo works on your sandbox site but not on the new site, this usually means a server or cache issue, not the plugin itself.
Please also make sure your server meets Masteriyo system requirements:
- WordPress 6.5+ and PHP 7.4+ (PHP 8.0 recommended)
- REST API, cURL, JSON, and GD/Imagick enabled
- Memory limit at least 256MB
- Avoid aggressive server caching (especially shared or LiteSpeed caching)
👉 One clear solution to try:
Please exclude Masteriyo pages (Learn, Account, Checkout) from server and plugin cache, then go to Settings → Permalinks → Save Changes, clear cache, and try the setup wizard again.
If it still does not work, your hosting provider can confirm whether REST API or security rules are blocking Masteriyo requests.
Best Regards!
I have WordPress 6.9 and PHP 8.3 on both sites. They are both in the same cpanel webhotell and share the same PHP configuration and other system configurations.
Cashing was not on. I saved changes in permalinks and cleared cash, but it had no effect.
I deletet the new site and reinstalled everything, but the problem persists.
Since the two installations run on the same configurations, it is strange one work and the other not.
Is there anything else I should look for?
Hi @sulfsby,
Thank you for writing back,
- Log in to your WordPress Admin Dashboard
- Go to Tools → Site Health
- Open the Info tab
- Expand the following sections:
- Server
- WordPress Constants
- PHP
From there, please copy and share the following details with us:
- PHP memory limit
- Max execution time
- Upload max filesize
- Post max size
In addition, please follow this guide to enable logging in Masteriyo:
https://docs.masteriyo.com/faqs/how-to-enable-logging-in-masteriyo
After that, try to open the demo site again and let us know if you see any error message. Please share the error details with us if available.
Once we receive this information, we will review it carefully and get back to you as soon as possible.
Best Regards!
There was a resource limit at the server causing the problem. It seems to work now.