Title: Enabling JetPack causes 404 errors
Last modified: December 16, 2016
---
# Enabling JetPack causes 404 errors
* [KieronLittleFishFX](https://wordpress.org/support/users/kieronlittlefishfx/)
* (@kieronlittlefishfx)
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/)
* Hello,
Whenever I enable JetPack I can no longer access URLs such as wp-admin,
because it returns as a 404. It also does not let me access and option pages,
as I just get a 404.
* Sometimes when I get access to my WooCommerce order details it only shows the
order title and page navigation but nothing else.
* It’s as if JetPack is breaking my URLs everytime it is enabled.
* Thanks
Viewing 9 replies - 1 through 9 (of 9 total)
* Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
* (@jeherve)
* Jetpack Mechanic 🚀
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8560705)
* Could you add the following to your site’s wp-config.php file?
* ```
define( 'WP_DEBUG', true );
if ( WP_DEBUG ) {
@error_reporting( E_ALL );
@ini_set( 'log_errors', true );
@ini_set( 'log_errors_max_len', '0' );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'CONCATENATE_SCRIPTS', false );
define( 'SAVEQUERIES', true );
}
```
* Your `wp-config.php` file may already include a line that says “define(‘WP_DEBUG’,
false);”. You can remove it, and replace it by the code above.
* Once you’ve done so, try to reproduce the error and then check the `wp-content/
debug.log` file for errors. You can paste the results here. You can then replace`
define('WP_DEBUG', true);` by `define('WP_DEBUG', false);` in the code above.
* Thanks!
* Thread Starter [KieronLittleFishFX](https://wordpress.org/support/users/kieronlittlefishfx/)
* (@kieronlittlefishfx)
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8561022)
* This is from the error log:
* ```
[16-Dec-2016 18:43:23 UTC] PHP Warning: Parameter 1 to wp_default_scripts() expected to be a reference, value given in /home/littl123/public_html/wp-includes/plugin.php on line 600
[16-Dec-2016 18:43:23 UTC] PHP Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/littl123/public_html/wp-includes/functions.php on line 3996
[16-Dec-2016 18:43:23 UTC] PHP Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/littl123/public_html/wp-includes/functions.php on line 3996
[16-Dec-2016 18:43:23 UTC] PHP Warning: Parameter 1 to wp_default_styles() expected to be a reference, value given in /home/littl123/public_html/wp-includes/plugin.php on line 600
[16-Dec-2016 18:43:23 UTC] Use Google Libraries: Not yet qualified with this version of WordPress. Bypassing UGL.
[16-Dec-2016 18:43:24 UTC] PHP Warning: Parameter 1 to wp_default_scripts() expected to be a reference, value given in /home/littl123/public_html/wp-includes/plugin.php on line 600
[16-Dec-2016 18:43:24 UTC] PHP Fatal error: Allowed memory size of 3145728000 bytes exhausted (tried to allocate 3274247974764767120 bytes) in /home/littl123/public_html/wp-includes/option.php on line 1109
```
* Thanks!
- This reply was modified 9 years, 8 months ago by [KieronLittleFishFX](https://wordpress.org/support/users/kieronlittlefishfx/).
* Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
* (@jeherve)
* Jetpack Mechanic 🚀
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8561124)
* Could you try to increase the amount of memory allocated to PHP, as explained
here:
[https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP](https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP)
* Let me know how it goes!
* Thread Starter [KieronLittleFishFX](https://wordpress.org/support/users/kieronlittlefishfx/)
* (@kieronlittlefishfx)
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8564346)
* Hello,
I’ve already tried allocating more memory, I had allocated a total of
3GB memory to WordPress and still no difference.
* The thing is, I’ve had JetPack enabled for months straight, how can it just decide
it needs over 2GB more memory when there is already 1GB allocated to it.
* Also, when I check my memory usage with JetPack disabled, it’s only 20MB.
* Thanks
* Thread Starter [KieronLittleFishFX](https://wordpress.org/support/users/kieronlittlefishfx/)
* (@kieronlittlefishfx)
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8567307)
* I am going to increase the allocated memory to 4GB, although I have no idea how
JetPack is using nearly 4GB RAM??
* Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
* (@jeherve)
* Jetpack Mechanic 🚀
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8569024)
* Yeah, it shouldn’t be happening. Jetpack doesn’t use that much memory on any
of my own installations.
* Could you tell me more about your server setup?
* Thanks!
* Thread Starter [KieronLittleFishFX](https://wordpress.org/support/users/kieronlittlefishfx/)
* (@kieronlittlefishfx)
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8571584)
* Hello,
We are running on the following specs:
- 6 CPU Cores
- 8GB RAM
- 40GB SSD (and unlimited storage).
* I just put my PHP version back to 5.5 from 7.1 and I’m no longer getting any
errors, from any plugins, but JetPack decided to randomly break weeks after I
updated.
* Thanks
* Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
* (@jeherve)
* Jetpack Mechanic 🚀
* [9 years, 8 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8573340)
* Thanks for the extra details.
* I believe this may be an incompatibility issue with PHP 7.1. We’re looking into
this right now, and I’ll let you know once this is fixed.
* Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
* (@jeherve)
* Jetpack Mechanic 🚀
* [9 years, 6 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8806763)
* This could be an issue between OPcache and WordPress’ XML-RPC requests (which
Jetpack uses to communicate with WordPress.com).
* You can read more about it here:
[https://ethitter.com/2017/01/upgrading-to-php-7-1/](https://ethitter.com/2017/01/upgrading-to-php-7-1/)
* Could you ask your hosting provider to check their server configuration and see
if the fix mentioned in the post above would help?
* Let me know how it goes!
Viewing 9 replies - 1 through 9 (of 9 total)
The topic ‘Enabling JetPack causes 404 errors’ is closed to new replies.
* 
* [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
* [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
* [Support Threads](https://wordpress.org/support/plugin/jetpack/)
* [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)
* 9 replies
* 2 participants
* Last reply from: [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
* Last activity: [9 years, 6 months ago](https://wordpress.org/support/topic/enabling-jetpack-causes-404-errors/#post-8806763)
* Status: not resolved