InBeijing

That made the trick, cheers!

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.

Done, many thanks again!

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?

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

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?

Yes, the htaccess redirect has always been enabled, apart from five minutes when I tested to disable it yesterday to see if it changed anything.

I still got the problems with no preview on my sharing and Jetpack connection not working properly. As for the latter problem, I will continue my dialog with Jetpack support.

But regarding the sharing, I believe the problem is somehow related to the Really Simple SSL update. All posts published before that update can be shared properly, but the two posts I have been publishing after that update do not generate any preview on Twitter or LinkedIn, instead resulting in error messages “No meta tags” for Twitter och card validator, and a “500” error message when running the post on LinkedIn debug.

This is a post written before the update: https://kinamedia.se/2022/11/01/analys-av-rapporten-om-de-misskota-fallen-gui-minhai-och-dawit-isaak/

This is a post written after the update: https://kinamedia.se/2022/11/05/kina-vagrar-prata-klimat-med-usa-infor-cop27/

First one doesn’t lack meta tags or come with any 500 error message, but the second one – and every post I will write from now on – unfortunately does.

Any idea what setting this problem might be attributed to?

Tried saving the settings again on Yoast – didn’t change anything. Tried to remove the htaccess redirect from Really Simple SSL – didn’t change anything.

A last try before I open up a new thread, since this might be related to the above. After experiencing problems yesterday, I also contacted Jetpack support and they said there is some problem with the fact that my site can still also be reached via HTTP:

I ran some tests on your site, and it seems that although your domain has a valid SSL certificate, it is still possible to access your site via HTTP. Your visitors and search engines can use either HTTP or HTTPS to access your site.

HTTP: https://kinamedia.se
HTTPS: https://kinamedia.se

This is an issue for search engines, since it often causes confusion and duplicate content, but it is also an issue for your site’s communication with WordPress.com, as our system does not know whether it should connect to your site via one or the other address.

To solve this issue, I would recommend that you change your site’s URL to HTTPS (you can do so under Settings > General in your dashboard), and then ask your host for help redirecting all traffic from HTTP to HTTPS.`

It was already set to HTTPS in settings, and I have reached out also to One.com support, but to no avail.

Any idea why the site would still be reachable with HTTP, and could it have anything to do with the last update?

Cheers,
Jojje

Hello again,

First i disabled all the hardening features and tried to share on Twitter/FB. Then I disabled the plugin altogether and tried the same thing. In both cases, no success – no preview when sharing on social medias, just a blue text link.

In the case of Twitter, it says “no meta tags” and in the case of LinkedIn it’s a “500 Failure”.

Again, I don’t know how or if this is related to Really Simple SSL, but I never had those problems before the last update.

I also updated to 6.0.7 and got no problems with pages or posts showing anymore. However, I am still left with a couple of other problems.

Since yesterday, there is no longer any preview when I share new content on my website on Twitter or LinkedIn. (Strangely, the preview do work as before when sharing on Facebook.)

Also Jetpack will not collect my visitor statistics any longer.

While I can’t prove that any of those problem are directly related to the Really Simple SSL, they certainly did’t exist before I made that update.

For your information, I had the 6.0.5 versin installed and the problem still persisted, was solved only after creating a .htaccess file in WordPress, a solution I was lucky to find when random troubleshooting on Google. My site was down several hours because of this.

Also, Jetpack statistics stopped working when a plugin called Comlpianz was, it seems, automatically installed when updating Real Simple SSL. Seems to be a conflict with Jetpack, so I uninstalled Complianz, again after random troubleshooting on my own.

Problem was solved when I followed the steps and created a .htaccess file in WordPress via this guide:

https://blog.hubspot.com/website/wordpress-htaccess

The other .htaccess that I referred to was the one in the File Manager at my web hotel One.com.

I still don’t understand what happened here? But happy of course that everything works again.

I just opened my htaccess and it consists only of three lines:

#Begin Really Simple Security
Options -Indexes
#End Really Simple Security

Is there any edit I should to do it that might help?

My url is https://www.inbeijing.se

Cheers,
Jojje

I noticed some other things:

* Comments are closed for posts made by authors. Only posts from me (administrator) have the comments field open.

I have checked the settings in both mine and the author’s account, and it says “allow comments”, just as before, nothing changed.

* The author can not see the statistics from WP’s Jetpack

What is going on? Is it not possible to have author’s on WP?