CryptX break page

Correction, version 3.2.10. Didn’t see you pushed out another update recently.

Hi Gabriel,

i can’t reach your page (https://coursevector.com/web-design/wordpress-cms-conversion/) to have a look on it.

Do you have the problem with version 3.2.10 of CryptX too?

Ralf

Yes, I’m running 3.2.10 right now.

If you can’t see it, we may be blocking your IP. I don’t know where you are located, so I don’t want to assume. We block IP ranges sometimes overseas that attack our server. Since we deal primarily in with US customers, this isn’t an issue. If you want to email me ( gabriel [a-t_ coursevector.com ) your IP I can look to unblock it, but it will look just like what you see in the screenshots.

Actually it just affected a second page yesterday. I had a coworker working on a draft page and couldn’t preview it. It rendered completely white until I disabled CryptX.

It’s starting to affect more pages in my website, is there any update on this? I had to disable the plugin entirely as it keeps breaking my website. I even tried changing the type of protection it used but nothing seemed to matter, it breaks the page no matter what. It’s seemingly random, but I know for sure the only way to fix it is to turn it off for the page or for the site.

From what I can tell, the page stops rendering immediately after it finishes rendering the header.php file of the theme. Anything within the content stops at that point if your plugin is enabled and it decides it wants to break that page.

Any update on this?

first of all sorry for the delay.

do you have any error logs on your server? There must be something in the php error log.
can you tell me if there is something? Because i can’t find the reason without the logs.

if you wish you can mail me the part of the log file to “ralf at weber-nrw dot de”

kind regards
Ralf

I have some errors but only from the first time I reported the issue, not during the second. It was almost like it didn’t error, but just stopped executing the PHP after the header.

I looked over the logs and the only thing I saw was an issue with get_header within the theme, and an issue with the plugin Post-Expirator. But the error with that plugin was only on that day and it hasn’t been updated in about a year. It’s been installed since April 2014 and this is the first error I’ve seen from it. So I’m not convinced that’s the issue but I don’t see anything else in there.

I can send you these regardless, but I don’t think they will be too helpful. I did go ahead an update the plugin on our site to 3.2.11 and reviewed all the pages on my website with it enabled and have not seen any issues so far. But again, not sure what the issue was to begin with.

I will be sure to holler if I see it happen again and see if anything appears in the logs.