Fatal error after Jetpack update

  • I manage a lot of sites for clients. including two multisites, and 11 of them have both this plugin and Jetpack. Today Jetpack was updated to v10.1, and this WSOD happened on all those sites:

    `PHP Fatal error: Uncaught InvalidArgumentException: Container doesn’t have a value stored for the “password.generator” key. in /wp-content/plugins/passwords-evolved/src/DependencyInjection/Container.php:94
    Stack trace:
    #0 /wp-content/plugins/passwords-evolved/src/Plugin.php(79): PasswordsEvolved\DependencyInjection\Container->offsetGet(‘password.genera…’)
    #1 /wp-content/plugins/passwords-evolved/pluggable.php(59): PasswordsEvolved\Plugin->get_password_generator()
    #2 /wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(109): wp_generate_password(10, false)
    #3 /wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(26): Automattic\Jetpack\Connection\Client::build_signed_request(Array, ‘{“package_versi…’)
    #4 /wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(430): Automattic\ in /wp-content/plugins/passwords-evolved/src/DependencyInjection/Container.php on line 94
    `

    I renamed this plugin folder, loggged in (had to set new password, too) visited Plugins page to get it deactivated automatically, undo rename, reactivate. Result for single sites: Ok. For multisites I had to activate, then deactivate, on each subsite before network activating again.

    I guess it’s Jetpack doing something wrong here, but as it is this plugin that throws the exception, I would appreciate your comment on this “incident”.

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

  • Same issue on our site

    Same here:

    Fatal error: Uncaught InvalidArgumentException: Container doesn't have a value stored for the "password.generator" key. in ~/public_html/wp-content/plugins/passwords-evolved/src/DependencyInjection/Container.php:94 

Stack trace: #0 ~/public_html/wp-content/plugins/passwords-evolved/src/Plugin.php(79): PasswordsEvolved\DependencyInjection\Container->offsetGet() 

#1 ~/public_html/wp-content/plugins/passwords-evolved/pluggable.php(59): PasswordsEvolved\Plugin->get_password_generator() 

#2 ~/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(109): wp_generate_password() 

#3 ~/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(26): Automattic\Jetpack\Connection\Client::build_signed_request() 

#4 ~/public_html/wp-content/plugins/passwords-evolved/src/DependencyInjection/Container.php on line 94
    • This reply was modified 3 years, 2 months ago by davemac.
    Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Hi!

    I work on the Jetpack team and wanted to jump in, just in case I can offer any help.

    We haven’t made any changes to that part of the plugin in the past few months, neither was WordPress’ wp_generate_password function. However, that function includes a filter, random_password, that can be leveraged by just about any plugin out there.

    I wonder if it were possible that all your sites used a third plugin that would be hooking into random_password. Would it be possible for you to check that?

    hi @ jeherve, I did a grep through some sites and there were no other instances of random_password that I could find.

    Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Thanks for giving this a try.

    I ran a few more tests on my end and managed to reproduce the issue. I’ve opened an issue here so we can start looking into this:
    https://github.com/Automattic/jetpack/issues/21165

    Until the problem is solved in Jetpack, you should be able to bypass the issue by adding the following code snippet to your site, via a functionality plugin:

    add_filter( 'jetpack_package_versions', '__return_false', 99 );

    Sorry everyone for the trouble!

    Thread Starter Knut Sparhell

    (@knutsp)

    Thank you for chiming in and investigate, @jeherve

    Plugin Author Carl Alexander

    (@carlalexander)

    Heya @knutsp. Sorry that I just saw this. Did the fix JetPack did solve the issue?

    Also thank you so much @jeherve for digging into it! ??

    Thread Starter Knut Sparhell

    (@knutsp)

    Seems so. The latest Jetpack update (10.2) went smoothly everywhere.

    Thread Starter Knut Sparhell

    (@knutsp)

    Now Jetpack 10.8 is out and the exact same problem is back

    Uncaught InvalidArgumentException: Container doesn't have a value stored for the "password.generator" key. in .../plugins/passwords-evolved/src/DependencyInjection/Container.php:94

    Is it possible to protect against this going fatal?

    @jeherve

    • This reply was modified 2 years, 7 months ago by Knut Sparhell.

    This is still an issue with the latest version of Jetpack v11 and Passwords Evolved v1.3.2. However it seems limited to Jetpack sites which are not properly connected to WordPress.com. This is making it a bit hard to pinpoint a solution. I’ve posted more details on these threads:

    https://github.com/Automattic/jetpack/issues/23835

    https://github.com/carlalexander/passwords-evolved/issues/13

    From my experience disconnected Jetpack and reconnected does workaround the issue however it doesn’t solve the root issue.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Fatal error after Jetpack update’ is closed to new replies.