“Allowed Memory Size Exhausted” appears when a WordPress request needs more PHP memory than the configured limit. It may be caused by a heavy plugin, theme, import task, faulty script or a low memory limit.
What the error means
The PHP process stops because it exhausted its memory allowance. The site may show a blank page, a fatal error or fail only during a specific task such as an update, import or page-builder action.
Find the cause first
Review the error log for the file or plugin consuming memory.
Temporarily disable the most recently installed plugin or theme.
Check whether the error happens only during an import, backup or another heavy operation.
Make sure the site runs on a supported and current PHP version.
Increase the WordPress memory limit
You can define a higher WP_MEMORY_LIMIT in wp-config.php if the hosting environment allows more PHP memory. A WordPress setting cannot exceed the server-level maximum.
Server PHP memory limit
If the WordPress limit is already correct, check PHP memory_limit in the hosting panel or ask support to change it. Do not keep increasing the limit without identifying the script that consumes the memory.
Verify after the change
Purge cache and repeat the task that failed.
Monitor the error log for another fatal error.
Check for unusual RAM or CPU usage.
If the issue returns, profile the request or test plugins one by one.
Helpful note
Increasing memory fixes the symptom only when the workload legitimately needs it. A memory leak or faulty code still requires correction of the real cause.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
When your domain stays at easy.gr but the website is hosted elsewhere, the connection usually happens through nameserver changes or DNS records. The legacy FAQ had separate short instructions for each platform; this article turns them into one practical reference.
Wix
With Wix you can connect an external domain either by changing nameservers or by DNS pointing. The platform typically recommends nameserver connection when you want Wix to handle the main site-side configuration.
Weebly, Tumblr and Shopify
Weebly: root-domain A record to 199.34.228.59.
Tumblr: root-domain A record to 66.6.44.4.
Shopify: root-domain A record to 23.227.38.32.
Squarespace
Four A records to 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
A verification CNAME to verify.squarespace.com.
A www CNAME to ext-cust.squarespace.com or whatever current value your Squarespace account provides.
Blogger
A records to 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.
A www CNAME to ghs.google.com.
An extra verification CNAME using the values shown in your Blogger account.
WordPress.com
In the legacy material, the connection used nameservers NS1.WORDPRESS.COM, NS2.WORDPRESS.COM and NS3.WORDPRESS.COM.
Helpful note
Exact DNS values and verification records can change on the external provider side. If something does not work, first compare the setup with the current documentation of the platform before assuming there is a registrar or DNS-zone issue.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
If you want faster delivery of static WordPress assets, a CDN can help a lot. In the legacy material, the suggested flow was based on the W3 Total Cache plugin with a Generic Mirror style setup.
When a CDN is useful
A CDN is useful when your site serves many static files such as images, CSS and JavaScript and you want to reduce latency for visitors coming from different regions.
Installing the plugin
From the WordPress admin area, go to Plugins, add or activate W3 Total Cache and then open its settings.
Enabling the CDN
Inside the plugin settings, enable CDN and choose the appropriate connection type. In the legacy example, Generic Mirror is used so you can define the accelerated URL of your CDN endpoint.
Final checks
Confirm that static assets are loading from the CDN domain.
Purge cache from the plugin and your browser.
Test the site on desktop and mobile.
Watch for mixed content or broken asset URLs.
Helpful note
If styles break or images do not load after the setup, first review the CDN base URL and cache rules before making deeper changes.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.
Automated installers reduce manual steps but do not remove the need for updates, secure credentials and tested backups.
Installing an application
Use the available application catalogue or WordPress Toolkit, select the correct domain and directory, and set a unique administrator username with a strong password. Do not retain default credentials.
Review versions and updates
After installation, configure appropriate updates and remove unused plugins or themes. Create a backup before a major update.
Creating a backup
In Backup Manager, choose a full or selective backup. A complete copy should include files, databases and the required settings.
Storage and restore
Do not keep the only copy on the same server. Maintain an external copy and test the restore process before a real incident.
Need more help?
If this guide did not resolve your issue, continue with the easy support team.