Can you please check your browser’s developer tools to learn more about what’s actually being sent? Does the Console show anything? Can you find the request in the Network tab and see what’s actually being returned?
You can’t remove it, but you may be able to prevent some of the excess redirects.
Normally, it should only redirect once. But if you have separate redirects for example to redirect you from HTTP to HTTPS, and from non-www to www, this may cause these additional redirects.
And if there are problems with the cookies of your browser, it may also cause these extra redirects, because you’ll be redirected if a security cookie is missing.
Actually this error is from root/server side.
Maybe @Admin must tell about this to iFastNet to install/setup CA Cert. correctly on the server. https://curl.haxx.se/docs/sslcerts.html
1.) For Debian/Ubuntu server: sudo apt-get install ca-certificates sudo update-ca-certificates -f
Then check whether it exists on: /etc/ssl/certs/ca-certificates.crt
2.) Or download the latest cacert.pem: https://curl.haxx.se/ca/cacert.pem
Then check/add/edit this line on server php.ini file: curl.cainfo="/path/to/cacert.pem"
From non-root user side, you can solve this problem with some ways:
1.) Download cacert.pem file above (No. 2).
Then make .user.ini file inside your domain/subdomain htdocs folder. Its contents is same with a line above.
(I haven’t tried this whether it works or not in this free hosting)
2,) If you can modify your PHP file, in your case is WordPress file. Maybe it’s impossible?
To turn off SSL verification for cURL function (CURLOPT_SSL_VERIFYPEER, false).
But this is bad, because it allows your nice, encrypted stream of confidential data to be silently hijacked by a bad guy.
Since your old post was still open, could you just reply to the old post instead of creating a new topic about the same issue? If you’re still waiting for more information after a few days, just bump the topic instead of starting over.
Yes and no.
The CA chain on our servers is perfectly normal and up to date.
The issue is that our panel doesn’t support uploading CA chains, so most automated systems, including our servers, cannot verify these SSL certificates.
Turning off SSL verification would work around this.
Googling the error message confirms my suspicion: the problem is that your BROWSER does not get a valid JSON response from the SERVER. This is DEFINITELY NOT a problem with the SSL configuration in PHP, or with the API/loopback/whatever irrelevant nonsense the Health Check plugin complains about for no legitimate reason. And it may not be a PHP problem in the first place.
I had hoped the Console would show something useful, but apparently it does not.
So instead, could you see what the server actually returns?
To do so:
Go to the WordPress admin page.
Prepare your content but don’t hit the button which causes the error yet.
Open your browser developer toolbar and go to the Network tab.
Delete anything that’s already there, and enable Preserve Logs.
Click the button which generates the error message.
Find the first request that’s being generated.
From the selected request, get a screenshot of the Headers panel and the Response panel.
So I woke up this morning tried going to the Network tab and get the logs tried updating and it seems as if the problem just went away by itself I don’t know why but as soon as I get to encounter the error I will definitely go to the Network tab and get the logs thanks for everyone’s help.