WPMU DEV Dashboard 3.1 API key invalid

I can't activate WPMU DEV Dashboard.

The new WPMU DEV Dashboard 3.1 doesn't work (null data in all fields) when I upgrade directly from the previous version. For example, it doesn't know who I am, says I've been a subscribed since 1970 and is generally just "empty".

When I uninstall, delete & purge the WPMUDEV settings from the db, reinstall, and then try to activate my account it returns an error that my API key is invalid. If I upgrade I am never prompted to attempt activation.

This is pretty much the stuff from sitemeta that I removed:
select from wp_sitemeta where meta_key like '%wpmudev%';

Please help! I really want to try out the new features. :slight_smile:

  • Shawn
    • The Crimson Coder

    Thanks for the response, PC!

    I've tried that twice already - no luck (see the "When I uninstall" para above which demonstrates the lengths to which I *completely* removed it).

    After installing 3.1 clean and attempting to activate, it reports "invalid API key".

    I should probably note that it's entirely possible that it's just me. I have had issues with activation in the past, last year when my subscription renewed (it took about a week or so before things worked again), but this year the subscription went smoothly a few weeks ago and everything was working fine until I upgraded to WDD 3.1.

  • Aaron
    • CTO

    Are you absolutely sure you're using the right API key from your profile?

    There hasn't been very much changed since the last version as far as the way api requests are made. The only thing I can think is they are stored in transients now the way WP core does. Perhaps you have a plugin or something that affects transients being stored? Do wp core plugin update notifications work?

    Another thing you might try is deleting the other options. Most start with "wdp_un_".

  • Jennifer
    • The Incredible Code Injector

    I'm having the same issue... When I copy paste my api key into the WPMU Dev Dashboard and click activate - get the following error: Your API Key was invalid. Please try again.

    This is a new wordpress multisite install and a brand new account registration.

  • Shawn
    • The Crimson Coder

    I'm 100% positive that the API key is correct. I've been using it so long I may as well have it memorized...but I did copy & paste from my profile page here and from the subscription page here (just in case). I also entered it manually into the system in the api key field in the db. None of them worked.

  • Shawn
    • The Crimson Coder

    Core updates, plugin updates and anti-splog all work fine.

    I just performed the following:
    1) Deactivated the plugin.
    2) Deleted the folder.
    3) Deleted everything that matched this:
    SELECT * FROM wp_sitemeta WHERE meta_key LIKE '%wdp_un_%' OR meta_key LIKE '%wpmudev%'
    4) Reuploaded the plugin.
    5) Network activated the plugin.
    6) Attempted to activate using my API key:
    Your API Key was invalid. Please try again.

  • Aaron
    • CTO

    Ok, i've tested both of your API keys on my own test site and works fine. So it seems to be something specific to your server or site config.

    I'll need you to help me debug. On line 560 of update-notifications.php after $data = unserialize($data); can you add this:
    var_dump($data['membership']);

    Also on line 585 after } else { can you add a:
    var_dump(wp_remote_retrieve_response_code($response));

    Now go clear and re-add your api key, and tell me what it prints in the screen.

  • Shawn
    • The Crimson Coder

    I fiddled with it a bit until I added this to ~@558:
    var_dump($response);
    That returns:

    object(WP_Error)#166 (2) {
      ["errors"]=>
      array(1) {
        ["http_request_failed"]=>
        array(1) {
          [0]=>
          string(146) "SSL certificate problem, verify that the CA cert is OK. Details:
    error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed"
        }
      }
      ["error_data"]=>
      array(0) {
      }
    }
  • Aaron
    • CTO

    Ahhh, SSL!

    that would be your problem. If your server curl/fsockopen setup is configured properly for ssl the https will fail.

    Ok, as a temp patch change this line at the top of the file:
    var $server_url = 'https://premium.wpmudev.org/wdp-un.php';
    to
    var $server_url = 'https://premium.wpmudev.org/wdp-un.php';

    I'll switch it back to http in my bugfix release tonight. The only reason I swtiched to https was privacy, but I guess can't expect all hosting to be configured right.

  • Shawn
    • The Crimson Coder

    That fixed it (https to http)! Thank you!

    However...

    Please don't change it globally on my account - as it would be better to try SSL first, and if that doesn't work, *then* revert to standard http. This will work for servers that aren't capable and will still be more secure for those that are.

    (I'm replacing this server in a couple weeks, so I want the SSL capability when we move to newer hardware & OS.)

  • Aaron
    • CTO

    I think i'm just gonna change it back. It's a request from your server to ours directly, so it's not like it can be intercepted at an internet cafe or something. And the data sent save for the api key isn't any different than what WP core sends to their servers over http.

  • Richie
    • Flash Drive

    Arg, I wish i would have seen this post. I made a post of my own regarding the same issue and Shawn gave me the solution too :p

    Maybe if there is a way to allow us members to click on a plugin category there in the forum and be shown the latest posts related to that plugin - it sure would have made it so i did not make a new posting.

    Thank you again Shawn for your help a few minutes ago.

  • Richie
    • Flash Drive

    HI Arun,

    Ah i did not see that - See the link now.

    BUT

    My post about my API not being accepted is not included in the list.

    https://premium.wpmudev.org/forums/tags/wpmu-dev-dashboard

    https://premium.wpmudev.org/forums/topic/membership-api-failed-wpmu-dev-dashboard-v31

    Maybe when member is keying a question - and we select that the issue is about "Plugins" maybe provide the list of plugins so we can check box that its regarding specifically (that plugin) in my example - "Dev-Dashboard"

    Then even my posting could be tagged correctly. Hope my idea helps the next person.

  • Shawn
    • The Crimson Coder

    It actually already does that. When you select plugin/theme a box appears below that (freeform text) that attempts to autocomplete the name of a plugin if you enter it. After the list populates you can pick the correct plugin/theme from the list in order to activate the correct tagging behavior.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.