404 not found after updating to 6.0.5

I’ve done some checks, and tried to list what we know of the issue:

– When I test the redirect, both posts are redirected to https. The LinkedIn debugger states that there’s an error in the redirect trail. This seems only to happen on https posts.
– The command curl -I https://domain.com results in a 500 error as well. But when loaded in a browser this does not happen.
– You had the issue also with Really Simple SSL deactivated, and with all .htaccess edits from Really Simple SSL removed as well.
– I do not see a difference in response on CURL from both URL’s. Both respond with a 500 when requested over https (in curl and in the LinkedIn debugger)
– If I remove the slash at the end, the 500 is gone.

So the 500 response only occurs when there’s no redirect, and not in browsers.

Even when I give CURL a user agent which should run like a browser, like this:

curl -H "user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36" https://kinamedia.se/2022/11/05/kina-vagrar-prata-klimat-med-usa-infor-cop27/

I get the “There has been a critical error on your website” in the resulting html. In case of such a response, the consequence is that the metatags are not there as well.

Based on the above, it looks like there’s a PHP error occurring in some situations, which should show up in the PHP logs on your server. If you don’t have direct access to those logs, you can enable debugging by adding

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

to your wp-config.php.

Then run the a curl command in the terminal, or running the LinkedIn debugger
curl -I https://domain.com/path

If the response is 500, you should be able to find a php error in the logs.

If you post the log here, or email it to us at support(at)really-simple-ssl.com we can check if we can see what’s going on.

• This reply was modified 2 years ago by Rogier Lankhorst.
• This reply was modified 2 years ago by Rogier Lankhorst.
• This reply was modified 2 years ago by Rogier Lankhorst.
• This reply was modified 2 years ago by Rogier Lankhorst.

Hello again,

Many thanks for running the tests. Upon opening my wp-config-php, I just wanted to show you first what is in there. At the very beginning, it says:

//Begin Really Simple SSL session cookie settings
@ini_set(‘session.cookie_httponly’, true);
@ini_set(‘session.cookie_secure’, true);
@ini_set(‘session.use_only_cookies’, true);
//END Really Simple SSL

Then a bit lower down, at row 82, by the very end, it says:

define(‘WP_DEBUG’, false);

Is this of any relevance, and if yes, should I replace the “false” with “true” sections you suggested above?

The secure cookie settings are not new, so won’t be related to this. (but you can comment them without issues if you want to check).

Yes, if you replace the debug log line with the two lines provided, you should get a log in wp-content/debug.log

• This reply was modified 2 years ago by Rogier Lankhorst.

Done! The log can be seen here: https://kinamedia.se/wp-content/debug.log

I see only one fatal error, which keeps occurring every 10-20 s or so:

PHP Fatal error: Uncaught Error: Call to undefined function stats_array() in /wp-content/plugins/https-stats-fix/https-stats-fix.php:32

The error seems to originate in the https-stats-fix plugin. I see that this plugin is not maintained anymore.

Can you try deactivating this plugin to see if it makes a difference?

Amazing – I deactivated the plugin and instantly I can share also the new posts on LinkedIn and Twitter, plus the Jetpack statistics tool started to collect data.

I will also again contact Jetpack and see if this solved whatever the problem was in communication with WordPress.

Many thanks for this! Should I now delete the debug-codes you sent me for wp-config-php, or should I keep everything untouched in the config file and the log?

Glad to hear that worked!

Yes, please delete the debug.log file, and set the WP_DEBUG constant back to false, otherwise it might expose data about your site.

Done, many thanks again!

OK, so after deleting the debug-log file and resetting the WP_DEBUG, another problem presented itself: I can’t access my control panel or log in to my admin panel at all.

https://kinamedia.se/admin or /wp-admin just returns an entirely bland page. Any idea of why this might be the case? Must be something in the wp-content-php.

@inbeijing my guess would be a typo in the wp-config.php.

For example, the code you posted above contains a formatted quote. If you pasted that back into the wp-config.php, it will result in a php error.

It should be like this:

define( 'WP_DEBUG', false );

And not

define(‘WP_DEBUG’, false);

• This reply was modified 2 years ago by Rogier Lankhorst.

That made the trick, cheers!