Fatal error: Uncaught Error:

Hi @mokl,

The flush rewrites code is written so it will only try to flush the rewrite rules once, one minute after activating SSL. It should not do this twice, so if it fails once, you should only see this error once. I just checked your site, and it’s looking good. Do you still have the issue after clearing the browser cache?

Hi @rogierlankhorst

When i clearing the browser cache, still see only old layout and old data. Nn some pages the WP builder line is missing.
Pages are not displayed correctly. No changes, upload data, they are not visible on the site.
After install SSL all pages do not match my edits.
Css
Old data, no WP builder line administration, no footer …

Thank you for your answer Rogier.

Do you have a screenshot of what you see? Then I can compare it with what I see.

Hi @rogierlankhorst

On pages, where are not displayed correctly, I′m changed new copy that. It works.
Menu looks correctly.
But http and https mixed home page. Maybe problem on home page start – ssl.
Look at logs:

This page checks to see whether WordPress can detect HTTPS.
Tests completed.
Your server can detect HTTPS normally. The recommended setting for HTTPS detection is standard WordPress function.
Your server environment shows this:
Array
(
[TMPDIR] => /data/web/virtuals/206325/virtual/tmp
[REDIRECT_QUERY_STRING] => action=sslfix-environment&sslfix_nonce=c6edef49a4ea1eb87a71387b3fa3c785
[REDIRECT_URL] => /wp-content/plugins/ssl-insecure-content-fixer/nowp/ajax.php
[REQUEST_SCHEME] => https
[LD_LIBRARY_PATH] => /usr/local/openssl/CURRENT/lib:$LD_LIBRARY_PATH
[HTTP_X_FORWARDED_PROTO] => https
[HTTP_X_PROXY_UUID] => 78704176-cc22-43cf-9721-dbc9e5c5c2bd-12239
[HTTP_VIA] => https/2 8bb1fbbe0b1b[78704176-cc22-43cf-9721-dbc9e5c5c2bd] (ApacheTrafficServer/8.0.1)
[HTTP_CLIENT_IP] => 109.105.39.18
[HTTP_DNT] => 1
[SSL_TLS_SNI] => heybay.cz
[PROXY_SCHEME] => https
[HTTPS] => on
[LOCAL_SCHEME] => https
[REDIRECT_SSL_TLS_SNI] => heybay.cz
[REDIRECT_PROXY_SCHEME] => https
[REDIRECT_HTTPS] => on
[REDIRECT_LOCAL_SCHEME] => https
[REDIRECT_UNIQUE_ID] => XEciknQWs9VBPwb9MAmOBQAAAFc

Log for debugging purposes
Send me a copy of these lines if you have any issues. The log will be erased when debug is set to false
Options:
* WordPress redirect
* Mixed content fixer
SERVER: apache
SSL is enabled for this site
** Detecting configuration **
plugin version: 3.1.3
Already on SSL, start detecting configuration
SSL type: LOADBALANCER
** Configuring SSL **
testing htaccess rules…
test page url, enter in browser to check manually: https://heybay.cz/wp-content/plugins/really-simple-ssl/testssl/loadbalancer/ssl-test-page.html
htaccess rules tested successfully.
checking if .htaccess can or should be edited…
.htaccess does not contain default Really Simple SSL redirect
retrieving redirect rules
converting siteurl and homeurl to https

Thank you Rogier.

Hi,

your site doesn’t seem to be redirecting to SSL yet, can you try to enable a redirect option in the plugin settings? The homepage does have the secure lock for me, you can try to clear all caches the website uses and check if the ‘mixed content fixer’ option is enabled in Settings->SSL->Settings.

Mark

Hi.

I tried it, but nothing happened.
In the WP Super cache plugin I can see this:

Cache Tester
Test your cached website by clicking the test button below.

Note: if you use Cloudflare or other transparent front-end proxy service this test may fail.

If you have Cloudflare minification enabled this plugin may detect differences in the pages and report an error.
Try using the development mode of Cloudflare to perform the test. You can disable development mode afterwards if the test succeeds.
Fetching https://heybay.cz/ to prime cache: OK (0.html)

Fetching first copy of https://heybay.cz/: OK (1.html)

Fetching second copy of https://heybay.cz/: OK (2.html)

Page 1: 200 (OK)
Page 2: 200 (OK)
The pages do not match! Timestamps differ or were not found!

Things you can do:

Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.
Enable logging on the Debug page here. That should help you track down the problem.
You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.

test https
Cache Tester
Test your cached website by clicking the test button below.

Note: if you use Cloudflare or other transparent front-end proxy service this test may fail.

If you have Cloudflare minification enabled this plugin may detect differences in the pages and report an error.
Try using the development mode of Cloudflare to perform the test. You can disable development mode afterwards if the test succeeds.
Fetching https://heybay.cz/ to prime cache: OK (0.html)

Fetching first copy of https://heybay.cz/: OK (1.html)

Fetching second copy of https://heybay.cz/: OK (2.html)

Page 1: 200 (OK)
Page 2: 200 (OK)
The pages do not match! Timestamps differ or were not found!

Things you can do:

Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match.
Enable logging on the Debug page here. That should help you track down the problem.
You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.
Send non-secure (non https) request for homepage

Is not this all caused by this?
No one of cached homepages have actual data.

Martin

Possibly the test fails because there are no timestamps present in the page source. Can you try to load the site over https:// in another browser/incognito mode to test if you do see the secure lock then?

Mark

http and https – (only here i see secure lock) has different content.
Loading site over two another browsers.

Martin

… all contens are outdated. Only on home page.

did you enable the .htaccess 301 redirect in settings/ssl? With caching the default redirect might not work as expected.

I would recommend to clear the cache, then deactivate the caching plugin.

If you use CloudFlare, enable developer mode.

Long-term settings

Mixed content fixer ON
Enable WordPress 301 redirection to SSL ON
Enable 301 .htaccess redirect OFF
Enable Javascript redirection to SSL ON
Debug ON
Stop editing the .htaccess file OFF
Switch mixed content fixer hook ON

CACHE OFF
CloudFlare NO USE

Site unchanged….

Where does my home page find out what to do with http or https when you type in the search engine row?

Martin

…. first win. On https version I see actual data.
But http does not redirect to https. Site has old data.

Martin

I see you have the .htaccess redirect not enabled. Please enable it to get it redirected to https. You can find it in settings/ssl/settings.

Hi Rogier.

I did it. It seems perfect.
Good job!
Many thanks!
Martin