WPMUDEV Dashboard Activation

I am trying to login and I see this errror.

Your server had a problem connecting to WPMU DEV: "HTTP Error: 403 "Forbidden"". Please try again.

If this problem continues, please contact your host with this error message and ask:

"Is php on my server properly configured to be able to contact https://premium.wpmudev.org/api/dashboard/v1/ with a POST HTTP request via fsockopen or CURL?"

The hosting is from hostgator and they say there's no problem from their end. Please help

  • Nastia
    • Support Rock Star

    Hello Suezen ,

    Welcome to WPMU DEV community!

    Would you please let me know your servers' IP address, so I could check, just in case if this IP is blocked from our end?

    Also please let me know the PHP version running on your network? This information can be found on your cPanel.

    Please advise,

    Cheers,
    Nastia

  • Suezen
    • WPMU DEV Initiate

    Your server had a problem connecting to WPMU DEV: "HTTP Error: 403 "Forbidden"". Please try again.

    If this problem continues, please contact your host with this error message and ask:

    "Is php on my server properly configured to be able to contact https://premium.wpmudev.org/api/dashboard/v1/ with a POST HTTP request via fsockopen or CURL?"

    Here are the details:
    IP Address: 108.167.143.108
    PHP Version: 5.4.45

    Hope this resolves the issue soon.

  • Denitsa
    • WordPress Warrior

    Hey there Suezen,

    I checked this IP and it doesn't seem we're blocking it on our end.

    Regarding your PHP version, I'd recommend having at least 5.6+, since older versions are at their end of life and are no longer supported. Current WP recommendations you can see here actually advise on having PHP 7+.

    Having said that, could you please access your server through FTP, edit the wp-config.php file, find a line like
    define('WP_DEBUG', false);

    and replace it with the following (if the above line doesn’t exist, simply insert next snippet just above the /* That's all, stop editing! Happy blogging. */ comment)

    // Enable WP_DEBUG mode
    define('WP_DEBUG', true);
    // Enable Debug logging to the /wp-content/debug.log file
    define('WP_DEBUG_LOG', true);
    // Disable display of errors and warnings
    define('WP_DEBUG_DISPLAY', false);
    @ini_set('display_errors', 0);

    This will produce a debug log that will be saved to a debug.log file inside the "/wp-content" folder. Please save the file as a .txt and attach it to your next post. If it happens to be larger than 5MB you might need to upload it to a service like Dropbox and provide us with the link here.

    Would you please download the following file and upload it to your server's root directory via FTP? Then try to access it via a link like http://mywebsite.com/curltest.php.

    https://gist.github.com/JRMorris77/2d917b63eb328d17a262f986748fe053

    Let us know what you see when you visit this link!

    All the best,
    Denitsa

  • Suezen
    • WPMU DEV Initiate

    Hey Denitsa

    Thanks for your reply.

    Please find the attached debug file. It says
    [28-Mar-2017 08:21:30 UTC] [WPMUDEV API Error] 4.3 | HTTP Error: 403 "Forbidden" (https://premium.wpmudev.org/api/dashboard/v1/updates [403])

    http://professorjayashankariasstudycircle.com/curltest.php it says
    premium.wpmudev.org is Up and running!
    google.com is Up and running!

    I tried again to login WPMUDEV DASHBOARD but the same error still persists

    Your server had a problem connecting to WPMU DEV: "HTTP Error: 403 "Forbidden"". Please try again.

    If this problem continues, please contact your host with this error message and ask:

    "Is php on my server properly configured to be able to contact https://premium.wpmudev.org/api/dashboard/v1/ with a POST HTTP request via fsockopen or CURL?"

    Please help...

  • Denitsa
    • WordPress Warrior

    Hi Suezen,

    premium.wpmudev.org is Up and running!
    google.com is Up and running!

    Do you have any other websites with the WPMU DEV Dashboard with any problems?

    This means the script you downloaded is actually able to connect to our servers via cURL.

    SInce that's pretty strange, considering the error you're getting, could you send us your FTP credentials so we can take a look around your your server and install?
    You can send us your details using our secure contact form (https://premium.wpmudev.org/contact/#i-have-a-different-question) and this template:

    Subject: "Attn: Denitsa Slavcheva"
    WordPress credentials:
    - WordPress admin username
    - WordPress admin password
    - Login URL

    FTP credentials:
    - Host
    - Username
    - Password

    cPanel/hosting control panel
    - Username
    - Password
    - Login URL

    - Link back to this thread for reference
    - Any other relevant urls

    The subject line ensures that it gets assigned to me.

    Let us know how it goes!

    Have a great day!

    Cheers,
    Denitsa

  • Denitsa
    • WordPress Warrior

    Hey there Suezen,

    Thanks for sending in your creds!

    I was able to login to your server and do some cURL testing, and while it wasn't working at first, it appears all is up and running now.

    Can you please check again if you could connect with the WPMU DEV Dashboard?

    Looking forward to hearing from you!

    Cheers,
    Denitsa

  • Sajid
    • DEV MAN’s Sidekick

    Hello Suezen,
    Hope you are doing good today :slight_smile:

    It seems, Denitsa did not changed any thing on your site in order to make it work. It appears to be a temporary glitch (most hosting keep the changes in DNS cache that cause issues some times) that resolved it self after some time and she confirmed everything is working now.

    But I still flagged her here and sent her a direct message. If there would be any thing else she did, then she or myself will post a reply here. Otherwise, we are all set here :slight_smile:

    Best Regards,
    Sajid - WPMU DEV Support

  • Denitsa
    • WordPress Warrior

    Hello Suezen,
    I trust you're well!

    I couldn't actually tell you what was the exact reason behind the problem here. It seems we've had the same issue with another member on Hostgator, so I had a chat with our sys admins while working on it. Ultimately, after doing some tests, it started working again for reasons unknown, so this might have been a DNS caching thing with Hostgator as Sajid suggested above.

    I don't think you should stumble across this error again in the near future, but if you do, please let us know and we'll be happy to help!

    Have a great day!

    All the best,
    Denitsa

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.