• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Wordpress Server Error 505 - Memory_Limit

theXxX

New Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.48_build1800221104.03 os_Ubuntu 20.04
Hi,

i have a problem with Wordpress and Plesk.

Details
  • When I try to save something in Wordpress with Elementor I get the error message Server Error 505.

I have already done the following:
  • Tested the same WordPress site with Elementor on another server. Everything works here.
  • It's not because of a broken plugin or because of Elementor. On another server (from a hoster), everything works without problems.
  • memory_limit was set to: 456M
    • After I increased to 456 it worked without errors for a few days. But now the error comes back.

After more detailed research, I realized that there are two settings for memory_limit. The server-side setting and the setting of WordPress itself.
In Plesk at Domains - PHP Settings memory_limit was increased to 456M. In Wordpress under Elementor - System Information, 128M was set. Therefore, I have increased the memory_limit to 456 for the used PHP version memory_limit under Plesk > Tools & Settings > PHP Settings > PHP handler (8.1.13 FastCGI application) > php.ini. Now 456M is also displayed in Wordpress. However, the error is still there.


Plesk settings:
PHP: 8.1.13 FastCGI Apache
CPUIntel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz (4 core(s))
VersionPlesk Obsidian v18.0.48_build1800221104.03 os_Ubuntu 20.04
BetriebssystemUbuntu 20.04.5 LTS

Any ideas about the problem?
 

Attachments

  • 4 - Wordpress.png
    4 - Wordpress.png
    21.5 KB · Views: 5
  • 3.png
    3.png
    49.8 KB · Views: 5
  • 2.png
    2.png
    89.9 KB · Views: 5
  • 1.png
    1.png
    77.3 KB · Views: 6
This type of error is often caused by nested scripts that recursively call themselves. Example: A rewrite rule defines a specific 404 error page, but that page does not exist, so the webserver redirects to a "not found" page, redirects to a "not found" page, redirects to a "not found" page ... The same can happen when in a post or a page a script is included that recursively opens itself. For that reason more and more RAM is consumed as the script is stock in a recursive loop. You can test this simply by increasing RAM per script execution to an abnormally high value such as 1 GB or even 2 GB (most scripts need less than 100 MB).

Should you have migrated the site recently, make sure that all your paths and absolute URLs are set correctly.
 
Back
Top