The 503 Service Unavailable Error generally means that your server has run out of resources. However, why this is occurring may vary. For the most part, a 503 Service Unavailable Error happens because WordPress uses too much memory or because your hosting service is experiencing unanticipated issues.
Can you ask your hosts for your php error logs?
-
This reply was modified 2 years, 11 months ago by
vupdraft.
They have asked the question on what the memory limit requirement is for your plugin – if that is something you can provide?
In order to be able to login, I have had to disable WP-Optimise by ftp (by renaming the plugin folder). I was immediately able to login again, so it is definitely causing the issue. Can you please advise on the resources question, as it very definitley speeded up viewing of the website, so it would be a shame not to use it.
There is no specific limit. I would generally say have max execution time of 900 and a WP memory of 512M
But it really depends on your site.
If you look in your php error log do you see anything like this
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes
If so can you copy and paste the error?
The site is a basic one hosted by Fasthosts, and there is no conventional cPanel. I am not sure php error logging is enabled. I have looked in the error_log file that is located in the <root><logfiles> folder (using ftp). and there are no fatal errors reported.
It does appear that during login, WP_Optimise is used. The following lines may well be after I disabled the plugin.
[Wed Jul 05 15:03:28.001423 2023] [fcgid:warn] [pid 226745] [client 176.252.184.95:48910] mod_fcgid: stderr: WP-Optimize: No caching took place, because the plugin location could not be found, referer: http://www.claro-orienteering.org.uk/wp/wp-login
[Wed Jul 05 15:10:00.841003 2023] [autoindex:error] [pid 226908] [client 51.222.253.3:38658] AH01276: Cannot serve directory /home/linweb43/c/claro-orienteering.org.uk-1103297071/user/htdocs/: No matching DirectoryIndex (default.html,default.htm,index.html,index.htm,index.shtml,index.php,index.php4,index.php3,index.phtml,index.cgi,_index.htm) found, and server-generated directory index forbidden by Options directive
That doesn’t give much away unfortunately. In tools >>site health >>info>> server what is your PHP time limit and your PHP memory limit
PHP time limit 60
PHP memory limit 256M
One of the issues I have had is slow load times, and occasional timeout errors – hence looking at caching.
I would seriously consider increasing your php time limit.
I would also increase your memory limit to 512M if you can
When regards to caching, it might be worth considering setting a longer cache lifespan as this will mean it’s done less frequently so uses less resources.
If you are noticing issues during the preload, you can throttle this by using the following filters
– Using add_filter(‘wpoptimize_preload_delay’, ‘my_preload_delay_method’), you can override the delay between two pages, which is currently set at 500000 (1/2 a second).
– Using add_filter(‘wpo_page_cache_preload_memory_threshold’, 10485760);
That filter lets you change how much memory should be left before interrupting the preload queue (10MB by default).
– Using add_filter(‘wpo_page_cache_preload_continue_interval’, 600);
This filter enables to change the time before the preload resumes when interrupted (600s by Default).
Thanks for the feedback. I will see what I can do about the php time limit.
I don’t think I can increase resources without paying more and the host helpline hasn’t been helpful when asked about resource limitations. A redesign using a lightweight theme is probably on the cards now.
Hello Elementor and Astra do very well as light weight themes (they both have free and Premium versions)
