Jixxer

Thank you James. Once I went into the database and into the wp_options table I could see that siteurl was really wrong. I fixed that b the DB and then removed the code I added to wp-config and everything is working correctly again.

I’m not going to move WordPress though, but thank you. It’s already where it should be. It was just the URL that needed to be changed.

A much easier fix than I thought. No restoring files was necessary. Excellent. Thank you.

Hi @lastsplash – Thank you. Can you please clarify if both lists of IP addresses are needed to allow on Cloudflare and how they differ? I am referring to the list on the link I provided above and the second list I also on the link I provided above to the link to the ips-v4.txt file.

Hi @shirtguy72 – Thank you. Originally I did try the ASN number 2635 as allow in Cloudflare, without using any list of IP addresses, but Jetpack was still unable to access my sites. I just tried it again though with just the ASN number as you suggested and it worked. So I will use that now and see how it goes. Thank you again.

• This reply was modified 2 years, 8 months ago by Jixxer.

Hi @erania-pinnera – Thank you for the information. I think we will just keep the setup as it is for now and see how it goes rather than switching to Jetpack protect.

What is a bit confusing though is that list of Jetpack IP addresses I posted came from the following link:

https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

Under Cloudflare is gives the list of IP ranges from 192.0.64 to 192.0.127 that I posted, but then there is another link which says it can be used as an alternative text list for Cloudflare as well here: https://jetpack.com/ips-v4.txt

I don’t understand the difference between the two lists so I just combined them. But the way the instructions are given it sounds like one can use either list and doesn’t need both. So it is confusing why the list on that website and the link to the text file don’t contain the same lists of IP addresses?

Thanks…

Thank you, but is the old version of WordPress preventing me from getting access to the admin login screen and the dashboard? If that isn’t the real issue then I would prefer to try to get into the admin area first and then update WordPress automatically, as well as automatically updating all the other outdated plugins.

And if I do the manual WordPress update can I be sure that this will fix the problem of not being able to access the admin login screen and the dashboard?

Thank you.

• This reply was modified 2 years, 8 months ago by Jixxer.

Thank you. Following is the entire error log file:

[18-Mar-2022 17:49:32 UTC] PHP Warning:  include_once(/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache-phase1.php): failed to open stream: No such file or directory in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/advanced-cache.php on line 20
[18-Mar-2022 17:49:32 UTC] PHP Warning:  include_once(): Failed opening '/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache-phase1.php' for inclusion (include_path='.:/opt/cpanel/ea-php71/root/usr/share/pear') in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/advanced-cache.php on line 20
[18-Mar-2022 17:49:32 UTC] Your version of WordPress (4.5) is lower than the version required by Jetpack (5.1). Please update WordPress to continue enjoying Jetpack.
[18-Mar-2022 17:49:32 UTC] PHP Warning:  include(/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache-base.php): failed to open stream: No such file or directory in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache.php on line 95
[18-Mar-2022 17:49:32 UTC] PHP Warning:  include(/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache-base.php): failed to open stream: No such file or directory in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache.php on line 95
[18-Mar-2022 17:49:32 UTC] PHP Warning:  include(): Failed opening '/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache-base.php' for inclusion (include_path='.:/opt/cpanel/ea-php71/root/usr/share/pear') in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache.php on line 95
[18-Mar-2022 17:49:32 UTC] PHP Warning:  include_once(/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/ossdl-cdn.php): failed to open stream: No such file or directory in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache.php on line 118
[18-Mar-2022 17:49:32 UTC] PHP Warning:  include_once(): Failed opening '/home1/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/ossdl-cdn.php' for inclusion (include_path='.:/opt/cpanel/ea-php71/root/usr/share/pear') in /home/MYSITE/public_html/MYSITE/MYSITE/wp-content/plugins/wp-super-cache/wp-cache.php on line 118
[18-Mar-2022 17:49:32 UTC] PHP Notice:  The called constructor method for WP_Widget in Jetpack_Post_Views is <strong>deprecated</strong> since version 4.3.0! Use <pre>__construct()</pre> instead. in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/functions.php on line 3722
[18-Mar-2022 17:49:33 UTC] PHP Warning:  Parameter 1 to wp_default_styles() expected to be a reference, value given in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/plugin.php on line 601
[18-Mar-2022 17:49:33 UTC] PHP Warning:  Parameter 1 to wp_default_scripts() expected to be a reference, value given in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/plugin.php on line 601
[18-Mar-2022 17:49:33 UTC] PHP Warning:  Illegal string offset 'remember' in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/user.php on line 41
[18-Mar-2022 17:49:33 UTC] PHP Warning:  Cannot assign an empty string to a string offset in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/user.php on line 41
[18-Mar-2022 17:49:33 UTC] PHP Warning:  Illegal string offset 'user_login' in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/user.php on line 56
[18-Mar-2022 17:49:33 UTC] PHP Fatal error:  Uncaught Error: Cannot create references to/from string offsets in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/user.php:56
Stack trace:
#0 /home/MYSITE/public_html/MYSITE/MYSITE/wp-login.php(784): wp_signon('', '')
#1 {main}
  thrown in /home/MYSITE/public_html/MYSITE/MYSITE/wp-includes/user.php on line 56

Sorry, below is correct now. This is the Fatal error:

[18-Mar-2022 17:49:33 UTC] PHP Fatal error: Uncaught Error: Cannot create references to/from string offsets in /home/mysite/public_html/mysite/mysite/wp-includes/user.php:56

Sorry, the above info is not correct. I will post the correct info shortly.

• This reply was modified 2 years, 8 months ago by Jixxer.

Thank you. Please see below:

[18-Mar-2022 17:49:33 UTC] PHP Warning: Illegal string offset ‘user_login’ in /home/mysite/public_html/mysite/mysite/wp-includes/user.php on line 56

• This reply was modified 2 years, 8 months ago by Jixxer.

@vijayhardaha thank you for your very helpful reply.

I disabled the .htaccess file temporarily, but that didn’t fix the problem.

I also changed to define( 'WP_MEMORY_LIMIT', '512M' ); in my wp-config file, but this didn’t fix the problem either.

Then I enabled debugging. About a dozen errors come up in the debug.log file. Not sure why I am getting so many errors when the site runs perfectly on the front end.

Unfortunately I wouldn’t know how to trouble shoot any of these errors though.

Thank you.

I have two sites running older version of WordPress and I just tried to manually update them to 5.9.2 via Dashboard. On both sites the update failed and said critical error and that I was sent an email with more information, but no emails received. Both websites are still working normally though, only the update failed.

I have now manually downloaded a copy of wordpress-5.9.2.zip – If I understand this thread correctly I just need to extract the wp-settings.php file from the Zip file and then replace the file on my WordPress sites with the new wp-settings.php file and I am done?

Thank you.

Sorry, my bad. I realized after I made this post that the site wasn’t running the latest version of WordPress. After updating, the plugin works again without problem.

I have one site running this plugin and I went to the site yesterday and discovered that it had completely crashed. Could not get the site to come up at all. When I entered the URL I got just a blank white screen. Eventually I spent a couple of hours disabling plugins on the site one by one and discovered that this plugin is what was crashing my entire site. I used it for a long time without problem. Then I saw it was just updated 3 days ago. Perhaps when it updated a few days ago is when it started crashing my site. Anyway, I have disabled it now and switched to a similar plug-in called “WP Content Copy Protection & No Right Click”, which is doing the job well now and no crashes. I hope my site has only been crashed for a few days by this plugin, but after reading some of the other problems people have had with the plugin, perhaps my site has been crashed for a long time. Very unfortunate.

• This reply was modified 5 years ago by Jixxer.

I also contacted Jetpack Support on this issue to see if they might be able to help and, after looking into it already, they said they can’t do anything to resolve the problem. They said they feel the issue is on the theme developers side.

They also suggested: “…you may be better off selecting a theme that does have support and regular updates.”

• This reply was modified 5 years, 2 months ago by Jixxer.

Thanks James. Unfortunately Jetpack Support already looked into it and they said they can’t do anything to help to resolve the issue. They said they feel the issue is on the theme developers side.

Hello Kookie,

Thank you. I guess its possible there is something in one of the posts on page 4 that may be causing a problem, but I can’t be sure.

Yes, I am able to go directly to the 4th page of posts by adding /page/3/ to the URL. But then it starts to crash as I mentioned.

I also sent a support email to Jetpack with the URL and they are also looking into it I think.

Thanks again…