Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Have you tried ensuring that Pretty Permalinks are enabled, by going to Settings -> Permalinks and clicking Save again there?

    If the issue persists after Saving permalinks again, could you post your site URL here, so I can have a look?

    If you want it to remain private, you can also contact us via this contact form:
    https://jetpack.com/contact-support/?rel=support

    If you contact us through our form, please make sure to include a link to this thread in your message.

    Also, can you do as I suggested in that thread, to get us some more info?

    1. Open the dashboard page.
    2. Open your browser console by following this guide:

    https://codex.ww.wp.xz.cn/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis

    3. Click on the Network tab
    4. Refresh the page.
    5. Try to activate or deactivate a module.
    6. If you see any lines in red inside the browser console, click on them. A new panel should appear on the right.
    7. Click on the “Response” tab in that new panel.
    8. Copy the message displayed there.
    9. Paste it in a reply to this email.
    10. If no red lines appeared in the browser console, click on the “Console” tab of the browser console.
    11. Copy any errors displayed there, and send them back to me.

    Once you’ve done that, you can head over to this old Settings page where you should be able to activate and deactivate Jetpack modules:

    http://www.yoursite.com/wp-admin/admin.php?page=jetpack_modules

    Just replace “www.yoursite.com” with your actual domain name first. 🙂

    Thanks!

    Thread Starter wtmtg

    (@wtmtg)

    Thank you, Richard.

    Ok, I am on Chrome, and opened the Developer’s JavaScript Console.

    Here are the errors:

    Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/module/protect/data?_cacheBuster=1511809439982 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/module/akismet/key/check?_cacheBuster=1511809439993 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/module/stats/data?range=day&_cacheBuster=1511809439960 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/site?_cacheBuster=1511809439953 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/updates/plugins?_cacheBuster=1511809440005 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/module/akismet/data?_cacheBuster=1511809440001 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/plugins?_cacheBuster=1511809439951 Failed to load resource: the server responded with a status of 404 ()
    /wp-json/jetpack/v4/connection/data?_cacheBuster=1511809440014 Failed to load resource: the server responded with a status of 404 ()
    VM436:164 WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403
    WrappedWebSocket @ VM436:164
    /wp-json/jetpack/v4/jumpstart Failed to load resource: the server responded with a status of 404 ()
    3VM436:164 WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403

    Thread Starter wtmtg

    (@wtmtg)

    Mmm… something to do with websocket?

    WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403
    WrappedWebSocket @ VM436:164

    Thread Starter wtmtg

    (@wtmtg)

    Mmm… when I refresh the “Settings” page for Jetpack, there are some GET errors:

    GET https://store.example.com/wp-json/jetpack/v4/site?_cacheBuster=1511810581637

    404 ()

    Thread Starter wtmtg

    (@wtmtg)

    Mmm, the Jetpack plugin is the only one active…

    No cache plugin installed…

    Thread Starter wtmtg

    (@wtmtg)

    Ok, I clicked on the “Response” tab for the red errors. Here they are:

    The requested URL /wp-json/jetpack/v4/plugins was not found on this server.

    The requested URL /wp-json/jetpack/v4/site was not found on this server.

    The requested URL /wp-json/jetpack/v4/site/features was not found on this server.

    Request URL:wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data
    Request Method:GET
    Status Code:403 Forbidden

    Thread Starter wtmtg

    (@wtmtg)

    And I have already disabled the ufw firewall:

    $ sudo ufw disable

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Could you post your site URL here, as I suggested earlier?

    If you want it to remain private, you can also contact us via this contact form:
    https://jetpack.com/contact-support/?rel=support

    If you contact us through our form, please make sure to include a link to this thread in your message.

    Thread Starter wtmtg

    (@wtmtg)

    Ok, I submitted the form, with my site URL and a link to this thread.

    Thank you in advance.

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Marking as resolved since you contacted us via email get back to you soon!

    Thread Starter wtmtg

    (@wtmtg)

    Ok, I figured it out, with inspiration from a post on StackExchange. Here is that post:

    https://webmasters.stackexchange.com/questions/61009/how-to-enable-use-of-htaccess-in-apache-on-ubuntu#61022

    My specific error has nothing to do with the Jetpack plugin (which is great by the way, keep up the great work =D ).

    My error was in my configuration of my Apache2 web server.

    When I was troubleshooting, I thought maybe my code for redirecting HTTP requests to HTTPS was incorrect…

    But that was fine. Here it is:

    RewriteEngine On
    RewriteCond %{HTTPS} !=on
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

    Then I took another look at my CONF file:

    000-default-le-ssl.conf

    A guide online suggested I use this:

    <Directory /var/www/html/example.com/public_html>
    Require all granted
    </Directory>

    The “Require all granted” was the problem.

    The final working code was:

    <Directory /var/www/html/example.com/public_html>
    #Require all granted
    AllowOverride All
    </Directory>

    Thank you Jetpack time for spending some time on this. Cheers. Happy Holidays.

    Thread Starter wtmtg

    (@wtmtg)

    …and restart the Apache2 server…I always forget this one…

    # sudo systemctl restart apache2

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Hey, that’s great, so glad you figured it out! Happy holidays to you too! 🙂

    Dear Richard,

    I too solved this issue with AllowOverride All on my site.

    But https://httpd.apache.org/docs/2.4/misc/security_tips.html#systemsettings explicitly discourages this directive as a security risk.

    What override(s) are actually needed for JetPack and the REST API?
    Is there some background information online?

    Regards,
    Paul

    Plugin Contributor Richard Archambault

    (@richardmtl)

    @paul-guijt: Could you please start your own thread, as per the Forum Welcome?

    https://ww.wp.xz.cn/support/plugin/jetpack#new-post

    Thank you!

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

The topic ‘recommended features failed to activate. Api404error (part 2)’ is closed to new replies.