I’m getting this error testing connection on one of my sites:
Connection test failed.
Error message: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
Any idea to solve this?
Thank you
Raul
Hey @RED
Can you please post the community system report from your MainWP Dashboard for review? The report is located in your Dashboard under Info → Server, 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.
### WordPress Check Required Detected Status ###
FileSystem Method = direct direct Pass
MultiSite Disabled =true true Pass
WordPress Memory Limit >=64M 40M Warning
WordPress Version >=3.6 6.0 Pass
### PHP Required Detected Status ###
cURL Extension Enabled =true true Pass
cURL SSL Version >=OpenSSL/1.1.0 OpenSSL/1.1.1o Pass
cURL Timeout >=300 seconds 60 Warning
cURL Version >=7.18.1 7.83.1 Pass
PCRE Backtracking Limit >=10000 1000000 Pass
PHP Allow URL fopen N/A NO
PHP Disabled Functions N/A No functions disabled.
PHP Exif Support N/A YES ( V7.4.)
PHP IPTC Support N/A YES
PHP Loaded Extensions N/A Core, PDO, Phar, Reflection, SPL, SimpleXML, bcmath, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, intl, json, libxml, mbstring, memcache, memcached, mysqli, mysqlnd, openssl, pcntl, pcre, pdo_mysql, pdo_sqlite, posix, readline, session, soap, sqlite3, standard, tidy, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib
PHP Max Execution Time >=30 seconds 30 Pass
PHP Max Input Time >=30 seconds 60 Pass
PHP Memory Limit >=128M 256M Pass
PHP Post Max Size >=2M 50M Pass
PHP Safe Mode Disabled =true true Pass
PHP Upload Max Filesize >=2M 50M Pass
PHP Version >=7.0 7.4.30 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 utf8mb4
MySQL Mode N/A NOT SET
MySQL Version >=5.0 5.7.38 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.9
Accept-Charset Content N/A
Architecture 64 bit
Gateway Interface CGI/1.1
HTTPS ON
Memory Usage 80.52 MB
Operating System Linux
Request Time 1655990439
Server Protocol HTTP/1.0
Server self connect Response Test O.K.
Server Software Apache
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36
### MainWP Dashboard Settings Detected Value ###
Abandoned plugins/themes tolerance 365
Basic uptime monitoring enabled Yes
Cache control enabled No
MainWP Dashboard Version Latest: 4.2.5 | Detected: 4.2.5 Pass
MainWP legacy backups enabled No
Maximum number of pages to return
Maximum number of posts to return 50
Maximum simultaneous install and update requests
Maximum simultaneous requests 4
Maximum simultaneous requests per ip1
Maximum simultaneous sync requests
Minimum delay between requests 200
Minimum delay between requests to the same ip1000
Number of child sites 64
Optimize for shared hosting or big networksYes
Plugin advanced automatic updates enabledYes
Primary Backup System MainWP WP Time Capsule Extension
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 ###
Activity Log for MainWP 2.0.0
MainWP Time Capsule Extension 4.0.1 Deactivated Warning
### Plugin Version Status ###
Activity Log for MainWP 2.0.0 Active
Backup and Staging by WP Time Capsule1.22.10 Active
Defender 3.0.1 Active
Disable Comments 2.3.6 Active
Loginizer 1.7.1 Active
MainWP Dashboard 4.2.5 Active
MainWP Key Maker 1.2 Active
Really Simple SSL 5.3.2 Active
Restricted Site Access 7.3.0 Active
Wordfence Security 7.5.11 Active
Thanks @RED
I’m not seeing anything obvious in the system report.
Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?
Just to provide an update on this - the issue was due to the Apache server update related to HTTP/2.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.