I logged in to my MainWP dashboard today and the overview says I have 730 updates available. Of these, 558 are plugins and 101 are themes. I have many of my plugins and themes set to trusted, so I would expect this number to be considerably lower.
Since this number seems very high, it gives me little confidence that my account is working - and updating - correctly.
So, my question: How can I confirm that MainWP is - or is not - actually updating? And if it is not, how can I fix it?
Thanks.
Hey @Armando-A
Can you please post the community system report from your MainWP Dashboard for review? The report is located in your Dashboard under Info → Server (your-mainwp-dashboard.com/wp-admin/admin.php?page=ServerInformation), on the top right of the page.
Be sure to use the button like the one below; this button hides all your private information:
Pressing the button auto-copies the report to your clipboard then just paste it in a reply here.
Hi Bojan. I tried replying to your email yesterday but it came back undeliverable. Not sure why. So here is the report. Please let me know if you need anything else! Thanks for your help!
### WordPress Check Required Detected Status ###
FileSystem Method = direct direct Pass
MultiSite Disabled =true true Pass
WordPress Memory Limit >=64M 256M Pass
WordPress Version >=6.2 6.7.1 Pass
### PHP Required Detected Status ###
cURL Extension Enabled =true true Pass
cURL Timeout >=300 seconds 60 Warning
cURL Version >=7.18.1 7.81.0 Pass
Function `tmpfile` enabled N/A Enabled Pass
OpenSSL Version >=OpenSSL/1.1.0 OpenSSL/3.0.2 Pass
OpenSSL Working Status Yes Yes Pass
PCRE Backtracking Limit >=10000 1000000 Pass
PHP Allow URL fopen N/A YES
PHP Disabled Functions N/A disk_free_space, diskfreespace, dl, exec, fpassthru, getmypid, getmyuid, highlight_file, link, opcache_compile_file, opcache_get_configuration, opcache_is_script_cached, passthru, pcntl_alarm, pcntl_exec, pcntl_fork, pcntl_get_last_error, pcntl_getpriority, pcntl_setpriority, pcntl_signal, pcntl_signal_dispatch, pcntl_sigprocmask, pcntl_sigtimedwait, pcntl_sigwaitinfo, pcntl_strerror, pcntl_wait, pcntl_waitpid, pcntl_wexitstatus, pcntl_wifcontinued, pcntl_wifexited, pcntl_wifsignaled, pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig, phpinfo, popen, posix_ctermid, posix_getcwd, posix_getegid, posix_geteuid, posix_getgid, posix_getgrgid, posix_getgrnam, posix_getgroups, posix_getlogin, posix_getpgid, posix_getpgrp, posix_getpid, posix_getppid, posix_getpwnam, posix_getpwuid, posix_getrlimit, posix_getsid, posix_getuid, posix_isatty, posix_kill, posix_mkfifo, posix_setegid, posix_seteuid, posix_setgid, posix_setpgid, posix_setsid, posix_setuid, posix_times, posix_ttyname, posix_uname, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, show_source, socket_listen, source, system, virtual,
PHP Exif Support N/A YES
PHP IPTC Support N/A YES
PHP Loaded Extensions N/A Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fcptools, fileinfo, filter, ftp, gd, gettext, hash, iconv, igbinary, imagick, imap, intl, json, ldap, libxml, mbstring, memcached, msgpack, mysqli, mysqlnd, newrelic, openssl, pcre, pdo_mysql, posix, readline, session, shmop, soap, sockets, sodium, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib
PHP Max Execution Time >=30 seconds 180 Pass
PHP Max Input Time >=30 seconds 60 Pass
PHP Memory Limit >=256M 256M Pass
PHP Post Max Size >=2M 300M Pass
PHP Safe Mode Disabled =true true Pass
PHP Session enabled N/A Enabled Pass
PHP Upload Max Filesize >=2M 300M Pass
PHP Version >=7.4 7.4.33.8 Pass
PHP XML Support N/A YES
SSL Extension Enabled =true true Pass
SSL Warnings = empty Pass
### MySQL Required Detected Status ###
MySQL Client Encoding N/A utf8
MySQL Mode N/A ALLOW_INVALID_DATES
MySQL Version >=5.0 8.0.31-google Pass
### Server Configuration Detected Value ###
Accept Content text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Charset Content N/A
Architecture 64 bit
Gateway Interface CGI/1.1
HTTPS ON
Memory Usage 57.57 MB
Operating System Linux
Request Time 1739804815
Server Protocol HTTP/1.0
Server self connect Not expected HTTP response body:
Server Software Flywheel/5.1.0
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 Edg/133.0.0.0
### MainWP Dashboard Settings Detected Value ###
Abandoned plugins/themes tolerance 365
Cache control enabled No
Enable Uptime Monitoring Yes
MainWP Dashboard Version Latest: 5.3.5.1 | Detected: 5.3.5.1 Pass
MainWP legacy backups enabled No
Maximum number of pages to return 50
Maximum number of posts to return 200
Maximum simultaneous install and update requests3
Maximum simultaneous requests 4
Maximum simultaneous requests per ip1
Maximum simultaneous sync requests 8
Maximum simultaneous uptime monitoring requests (Default: 10)10
Minimum delay between requests 200
Minimum delay between requests to the same ip1000
Number of connected sites 74
Optimize data loading No
Plugin advanced automatic updates enabledYes
Primary backup system MainWP Legacy Backups
REST API enabled No
Site health monitoring enabled No
Theme advanced automatic updates enabledYes
Use WP Cron Yes
WP Core advanced automatic updates enabledYes
### Extensions Version License Status ###
MainWP Sucuri Extension 5.0.1 Active Pass
### Plugin Version Status ###
MainWP Child 5.3.5 Active
MainWP Child Reports 2.2.3 Active
MainWP Dashboard 5.3.5.1 Active
WPS Hide Login 1.9.17.1 Active
Thanks for the system reports.
Since auto-updates are driven by WP Cron jobs, which you seem to be using judging by your System Reports as opposed to server-side Crons, make sure that WP Cron is being triggered regularly on your Dashboard.
Easiest way to make sure that WP-Cron jobs are regularly triggered on your MainWP Dashboard, is to add your Dashboard site as a monitor to an external uptime service such as Uptime Robot.
The Uptime Robot will ping your dashboard site regularly, which will provide network activity and make sure that all scheduled events are occurring.
Another thing to mention is related to the large number of available updates and the number of connected sites. For managing that many sites, and to handle that many updates, I’d recommend increasing the PHP Memory Limit and WP Memory Limit to at least 512M.
Also, it wouldn’t hurt to increase the PHP Max Execution Time and cURL Timeout to at least 300 seconds, especially considering that your current timeouts are only 180s and 60s. You can find more details on how to adjust these settings in our system requirements guide: Resolving System Requirement Issues - MainWP Knowledgebase
Hi Bojan. I appreciate your continued support. In response to your last message:
I was already running uptime monitor on my MainWP site, so I think we’re good there. If there’s a way to download their logs to check their performance, I would be happy to do that.
With regard to the PHP and WP memory limits, etc., I asked my host, Flywheel, to implement those changes. Here is their reply:
"As a first step in troubleshooting, many developers will recommend drastically increasing memory to see if that resolves an issue. Not all hosts are created equal, and those with different infrastructures may in fact need those massive boosts in memory that the developers call for, but sites hosted on the Flywheel Cloud often call for less memory to be present because PHP workers play a larger role in faster processing on our infrastructure.
Looking at this site, we can see that it isn’t actually reaching any memory limits, so raising the memory to the values requested wouldn’t be of any benefit in this instance. However, I did find some max_children errors in the logs so I’ve bumped up the PHP workers. I’ve also adjusted the timeout as requested. "
I now see that the number of updates is dramatically fewer than when I opened my ticket, which I take as a good sign.
I also am now including a new (after those changes) message in the MainWP Settings > Advanced Settings page: “Set how many requests are performed at once and delay between requests in order to optimize your MainWP Dashboard performance. Both Cross IP and IP Settings handle the majority of work connecting to your Child sites, while the sync, update, and installation request have specialized options under the Frontend Requests Settings section.” Do you have any suggestions for optimizing this?
Finally, here is a new copy (post Flywheel’s changes) of the System Report in case it helps or sheds any light on the current performance…
### WordPress Check Required Detected Status ###
FileSystem Method = direct direct Pass
MultiSite Disabled =true true Pass
WordPress Memory Limit >=64M 256M Pass
WordPress Version >=6.2 6.7.2 Pass
### PHP Required Detected Status ###
cURL Extension Enabled =true true Pass
cURL Timeout >=300 seconds 60 Warning
cURL Version >=7.18.1 7.81.0 Pass
Function `tmpfile` enabled N/A Enabled Pass
OpenSSL Version >=OpenSSL/1.1.0 OpenSSL/3.0.2 Pass
OpenSSL Working Status Yes Yes Pass
PCRE Backtracking Limit >=10000 1000000 Pass
PHP Allow URL fopen N/A YES
PHP Disabled Functions N/A disk_free_space, diskfreespace, dl, exec, fpassthru, getmypid, getmyuid, highlight_file, link, opcache_compile_file, opcache_get_configuration, opcache_is_script_cached, passthru, pcntl_alarm, pcntl_exec, pcntl_fork, pcntl_get_last_error, pcntl_getpriority, pcntl_setpriority, pcntl_signal, pcntl_signal_dispatch, pcntl_sigprocmask, pcntl_sigtimedwait, pcntl_sigwaitinfo, pcntl_strerror, pcntl_wait, pcntl_waitpid, pcntl_wexitstatus, pcntl_wifcontinued, pcntl_wifexited, pcntl_wifsignaled, pcntl_wifstopped, pcntl_wstopsig, pcntl_wtermsig, phpinfo, popen, posix_ctermid, posix_getcwd, posix_getegid, posix_geteuid, posix_getgid, posix_getgrgid, posix_getgrnam, posix_getgroups, posix_getlogin, posix_getpgid, posix_getpgrp, posix_getpid, posix_getppid, posix_getpwnam, posix_getpwuid, posix_getrlimit, posix_getsid, posix_getuid, posix_isatty, posix_kill, posix_mkfifo, posix_setegid, posix_seteuid, posix_setgid, posix_setpgid, posix_setsid, posix_setuid, posix_times, posix_ttyname, posix_uname, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, show_source, socket_listen, source, system, virtual,
PHP Exif Support N/A YES
PHP IPTC Support N/A YES
PHP Loaded Extensions N/A Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fcptools, fileinfo, filter, ftp, gd, gettext, hash, iconv, igbinary, imagick, imap, intl, json, ldap, libxml, mbstring, memcached, msgpack, mysqli, mysqlnd, newrelic, openssl, pcre, pdo_mysql, posix, readline, session, shmop, soap, sockets, sodium, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib
PHP Max Execution Time >=30 seconds 300 Pass
PHP Max Input Time >=30 seconds 60 Pass
PHP Memory Limit >=256M 256M Pass
PHP Post Max Size >=2M 300M Pass
PHP Safe Mode Disabled =true true Pass
PHP Session enabled N/A Enabled Pass
PHP Upload Max Filesize >=2M 300M Pass
PHP Version >=7.4 7.4.33.9 Pass
PHP XML Support N/A YES
SSL Extension Enabled =true true Pass
SSL Warnings = empty Pass
### MySQL Required Detected Status ###
MySQL Client Encoding N/A utf8
MySQL Mode N/A ALLOW_INVALID_DATES
MySQL Version >=5.0 8.0.31-google Pass
### Server Configuration Detected Value ###
Accept Content text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Charset Content N/A
Architecture 64 bit
Gateway Interface CGI/1.1
HTTPS ON
Memory Usage 57.59 MB
Operating System Linux
Request Time 1740058359
Server Protocol HTTP/1.0
Server self connect Not expected HTTP response body:
Server Software Flywheel/5.1.0
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36 Edg/133.0.0.0
### MainWP Dashboard Settings Detected Value ###
Abandoned plugins/themes tolerance 365
Cache control enabled No
Enable Uptime Monitoring Yes
MainWP Dashboard Version Latest: 5.3.5.1 | Detected: 5.3.5.1 Pass
MainWP legacy backups enabled No
Maximum number of pages to return 50
Maximum number of posts to return 200
Maximum simultaneous install and update requests3
Maximum simultaneous requests 4
Maximum simultaneous requests per ip1
Maximum simultaneous sync requests 8
Maximum simultaneous uptime monitoring requests (Default: 10)10
Minimum delay between requests 200
Minimum delay between requests to the same ip1000
Number of connected sites 74
Optimize data loading No
Plugin advanced automatic updates enabledYes
Primary backup system MainWP Legacy Backups
REST API enabled No
Site health monitoring enabled No
Theme advanced automatic updates enabledYes
Use WP Cron Yes
WP Core advanced automatic updates enabledYes
### Extensions Version License Status ###
MainWP Sucuri Extension 5.0.1 Active Pass
### Plugin Version Status ###
MainWP Child 5.3.5 Active
MainWP Child Reports 2.2.3 Active
MainWP Dashboard 5.3.5.1 Active
WPS Hide Login 1.9.17.1 Active
Thanks again!
This is indeed a great sign of automatic updates working through the large number of available updates.
I would suggest leaving the values on the Advanced Settings page at their defaults. If you notice that servers hosting the child sites are running out of resources, I would then suggest decreasing the number of simultaneous installs/requests and increasing the delay between them.
Thank you. I will keep an eye on the number of pending updates over the next few days and will jump back in here if I need further assistance. Have a great day, and thank you again for your patience and support.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.