White Blanked Out Plugin Field

Resolved

(@mexxez)

Dear Support-Team,

Recently I have been facing an issue with white blanked out plugin fields within WordPress in rssssl. The issue occured after migrating from one server to another.

Chrome developer console error codes:

api-fetch.min.js?ver=bc0029ca2c943aec5311:2          GET https://www.vinaet.de/wp-json/reallysimplessl/v1/fields/get?false=&nonce=573efd8a38&token=jjvlu&_locale=user 404
T @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
l @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
O @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
o @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
O.method.r @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
o @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
t @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
v @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
A @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
d @ index.js?ver=759ecc9365aebd919115:382
(anonymous) @ index.js?ver=759ecc9365aebd919115:382
getFields @ index.js?ver=759ecc9365aebd919115:382
Be @ index.js?ver=759ecc9365aebd919115:382
Qn @ react-dom.min.js?ver=17.0.1:9
Wt @ react-dom.min.js?ver=17.0.1:9
os @ react-dom.min.js?ver=17.0.1:9
Ur @ react-dom.min.js?ver=17.0.1:9
Ir @ react-dom.min.js?ver=17.0.1:9
Dr @ react-dom.min.js?ver=17.0.1:9
Pr @ react-dom.min.js?ver=17.0.1:9
Er @ react-dom.min.js?ver=17.0.1:9
ul @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
Lr @ react-dom.min.js?ver=17.0.1:9
ml @ react-dom.min.js?ver=17.0.1:9
e.render @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ index.js?ver=759ecc9365aebd919115:382
api-fetch.min.js?ver=bc0029ca2c943aec5311:2          GET https://www.vinaet.de/wp-json/reallysimplessl/v1/tests/get_modal_status?state=undefined&nonce=573efd8a38&token=jhfjf&data=undefined&_locale=user 404
T @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
l @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
O @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
o @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
O.method.r @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
o @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
t @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
v @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
(anonymous) @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
A @ api-fetch.min.js?ver=bc0029ca2c943aec5311:2
d @ index.js?ver=759ecc9365aebd919115:382
m @ index.js?ver=759ecc9365aebd919115:382
(anonymous) @ index.js?ver=759ecc9365aebd919115:382
$r @ react-dom.min.js?ver=17.0.1:9
unstable_runWithPriority @ react.min.js?ver=17.0.1:9
xn @ react-dom.min.js?ver=17.0.1:9
Qr @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
h @ react.min.js?ver=17.0.1:9
ne.port1.onmessage @ react.min.js?ver=17.0.1:9
vue.runtime.esm.js:8418 Download the Vue Devtools extension for a better development experience:
https://github.com/vuejs/vue-devtools
content-script.js:1243 [ WER: Connected to Extension Hot Reloader ]
options-general.php:1 Uncaught (in promise) {code: 'invalid_json', message: 'Die Antwort ist keine gültige JSON-Antwort.'}
Promise.then (async)
getFields @ index.js?ver=759ecc9365aebd919115:382
Be @ index.js?ver=759ecc9365aebd919115:382
Qn @ react-dom.min.js?ver=17.0.1:9
Wt @ react-dom.min.js?ver=17.0.1:9
os @ react-dom.min.js?ver=17.0.1:9
Ur @ react-dom.min.js?ver=17.0.1:9
Ir @ react-dom.min.js?ver=17.0.1:9
Dr @ react-dom.min.js?ver=17.0.1:9
Pr @ react-dom.min.js?ver=17.0.1:9
Er @ react-dom.min.js?ver=17.0.1:9
ul @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ react-dom.min.js?ver=17.0.1:9
Lr @ react-dom.min.js?ver=17.0.1:9
ml @ react-dom.min.js?ver=17.0.1:9
e.render @ react-dom.min.js?ver=17.0.1:9
(anonymous) @ index.js?ver=759ecc9365aebd919115:382
options-general.php:1 Uncaught (in promise) {code: 'invalid_json', message: 'Die Antwort ist keine gültige JSON-Antwort.'}

WordPress server error logs:

[Mon Jan 23 03:47:02.593761 2023] [ssl:warn] [pid 2420486:tid 140394665744512] AH01909: RSA certificate configured for h512606.web246.dogado.net:443 does NOT include an ID which matches the server name
[Mon Jan 23 03:47:05.135200 2023] [ssl:warn] [pid 2420486:tid 140394665744512] AH01909: RSA certificate configured for h512606.web246.dogado.net:443 does NOT include an ID which matches the server name
[Mon Jan 23 03:47:22.743567 2023] [ssl:warn] [pid 2065961:tid 140449932535936] AH01909: RSA certificate configured for h512606.web246.dogado.net:443 does NOT include an ID which matches the server name

I get the basic meaning of this error. However, I checked the SSL-certificate with several tools and these tools e.g. qalys consider it ok as far as I understand.

Probably an error due to migrating / switching the server e.g. registry still containing old ssl-certificate information?

However, I created a completely new domain and there the issue also happened.

I am looking forward to hearing from you soon.

Kind regards,

Max

The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)

Plugin Author Rogier Lankhorst
(@rogierlankhorst)

1 month, 4 weeks ago

@mexxez the “json is not valid response” sounds like the php errors are causing invalid json. If you disable debugging, and re-save the permalinks, does that help?
Thread Starter mexxez
(@mexxez)

1 month, 4 weeks ago
Many thanks for your response. I think you rolled out your latest update today. It actually helped to solve the issue on the new domains.

However, on the vinaet.de domain the issue still persists. I alrealdy tried to re-save permalinks etc.

How could I cleanly reinstall your plugin (without crashing site and damaging database)?
- This reply was modified 1 month, 4 weeks ago by mexxez.
Plugin Author Rogier Lankhorst
(@rogierlankhorst)

1 month, 4 weeks ago

@mexxez that is good to hear. I don’t expect a re-install will help, did you try in a private/anonymous browser? That might help.

To re-install: if you click “deactivate” in the plugins overview, please select “keep https”. You can then deactivate and re-install.

digitaljetstream
(@digitaljetstream)

1 month, 4 weeks ago

Im having the same problem. I checked the PHP I updated it, and I deleted the simple SSL and reinstalled it. I kept the Pro model and disabled it, and then ran able to it when the new software was installed. I’m still getting the white screens and on able to activate the program and the portal.

Can you help?

Thanks in advance!
Anthony

Plugin Author Rogier Lankhorst
(@rogierlankhorst)

1 month, 3 weeks ago

@digitaljetstream please check if you see a console error in the browser? Right click on the screen, inspect element, console. Then check for any errors there. If you post them here, we can take a look.
digitaljetstream
(@digitaljetstream)

1 month, 3 weeks ago
https://daughtersoflegends.org/images/console.png
The above link gives the full screen print of the console
```
JQMIGRATE: Migrate is installed, version 3.3.2
daughtersoflegends.org/:1 Mixed Content: The page at 'https://daughtersoflegends.org/' was loaded over HTTPS, but requested an insecure video 'http://my.sunsoft.pk/wp-content/uploads/2023/01/Video.mov'. This content should also be served over HTTPS.
DevTools failed to load source map: Could not load content for chrome-extension://bmnlcjabgnpnenekpadlanbbkooimhnj/browser-polyfill.js.map: System error: net::ERR_BLOCKED_BY_CLIENT
daughtersoflegends.org/:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
```
Thread Starter mexxez
(@mexxez)

1 month, 3 weeks ago
Somehow, your plugin is working in the staging environment.

Differences so far are:
- Disabled the cache by setting the constant WP_CACHE to FALSEin the file wp-config.php.
- Permalinks are disabled
- Consequently, WP Rocket has not created a cache
Plugin Contributor Mark
(@markwolters)

1 month, 3 weeks ago

@digitaljetstream I don’t see any errors specifically related to Really Simple SSL in your browser console. There does seem to be an error related to a Chrome extension. Does the issue also occur when opening the settings page in an incignito / private window?

@mexxez if it does work on staging by disabling the cache, but not on live, could you if clearing the cache on the live website resolves the issue?

Thread Starter mexxez
(@mexxez)

1 month, 3 weeks ago

I already did what you suggested, several times actually.
Thread Starter mexxez
(@mexxez)

1 month, 3 weeks ago
I found a solution which unfortunately is not great: Change permalink structure to simple. Anything else will not work. I tested this a a new wordpress installation. Thus, SEO etc. will not be affected.

Another workaround is using a permalink plugin instead. Somehow it works. Though, I really do not see any need for such a plugin.

I am having also another permalink based issue with elementor on some wordpress installations if I change permalink structure to anything except simple. The issue occured on another wordpress installation after activating rank math plugin. But, the issue still stayed even after deactivating rank math. Could it be possible that rank math tries to overwrite at least some of the wordpress permalink structure?

However, I had absolutely no issues with that on the old server. Thus, may there be any server config on nginx which basically enables this issue?

https://github.com/elementor/elementor/issues/13849
- This reply was modified 1 month, 3 weeks ago by mexxez.
- This reply was modified 1 month, 3 weeks ago by mexxez.
- This reply was modified 1 month, 3 weeks ago by mexxez.
- This reply was modified 1 month, 3 weeks ago by mexxez.
Plugin Contributor Mark
(@markwolters)

1 month, 3 weeks ago

Really Simple SSL should work fine on all permalink setups. It could be that a different plugin is altering the default WordPress permalinks behaviour. It’s hard to say what’s causing the issue exactly, but I wouldn’t rule an issue in your NGINX permalink configuration.

Thread Starter mexxez
(@mexxez)

1 month, 3 weeks ago

I finally found a solution. I still think it is more kinda workaround but for now it works.

Firstly, I switched back to Apache (less performance, but I have to take it for now). Secondly, as security headers were not set I still had to add them manually (due to new wordpress installation old .htaccess was not in the root). First this caused 404 errors everywhere except on the starting page. However flushing (saving) permalinks solved the issue and Really Simple SSL started working as well as Elementor. I assume that there were some server configuration lines which simply got “overwritten”.

Now, I am still in contact with my hosting provider to see wether this problem may be solved on Nginx and to see what actually happend.

Viewing 12 replies - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.

Views