Problem with Jetpack Publicize – Connect returns 404 page

  • Resolved aandreachi

    (@aandreachi)


    9 years, 8 months ago

    Problem I am having is that when I try to connect our blog to any social media platform it results in a 404 error. Just going to get this out of the way – I have tried all common troubleshooting methods.

    Our WP site is hosted with Godaddy and we also have a WordPress.com account. We have a somewhat complicated reverse proxy set up between our parent site (hosted elsewhere) and our WP site. The long and short of it is our parent site is “www.x.com” and our WP site is “blog.x.com”. End User sees our WP site as “www.x.com/blog” although there is no actual “/blog” directory with a WP install. It is more complicated than that and I did not set it up.

    Everything is working properly after making some tweaks to some internal WP site files to ensure the “/blog” is not getting dropped from the URL, especially in the WP-admin pages.

    Jetpack is installed in WP and I have (supposedly) connected it to our WordPress.com account. Our WordPress.com account displays the URL and I am able to view current web stats in both the WordPress.com dashboard as well as the WP site dashboard. However, WordPress.com displays the “This site cannot be accessed” message.

    When I run the Jetpack debugger I get the “It looks like your site cannot communicate properly with Jetpack” notification. Despite that, the web stats are working and I’m not seeing any other Jetpack error message. Requests to the /xmlrpc.php file are providing the expected results (our web server’s version of the “this page only accepts HTTP POST requests”).

    Regarding the 404 page when I try to connect a social media platform,
    I have updated the publicize_api_url filter in publicize-jetpack.php so the “/blog” is retained in the URL (https://public-api.wordpress.com/blog/connect/?jetpack=publicize). Without this the request will resolve to a 404 page no matter what.

    I have tried disconnecting/re-connecting Jetpack a few times.

    I understand it would be easier to trouble shoot if the URL was available – I would be willing to provide it via email to a developer but not publicly (neither the URL or site are offensive in any way).

    Our internal web filter is not blocking any requests from WordPress.com.

    First question is HOW WordPress.com actually accesses a WP site – how can it able to see the URL and web stats when connecting via Jetpack but “not able to access the site”?

    According to our Godaddy server logs for the WP-site, WordPress.com is making successful GET requests (200 Response) to the “/feed/” file, so it seems WordPress.com is able to access our site after all(?)

    Second, why would Jetpack not be able to communicate with the WP site if the /xmlrpc.php is not blocked?

    There are also POST requests to the xmlrpc.php file from Jetpack that succeed which means they are not getting lost due to our internal web server config.

    Third, I think the use of “/connect/” in the URL might be to blame – our internal web config (using IIS) might not be handling it properly since there is no actual directory. Does that string have to be in the URL for a WordPress.com or Jetpack request?

    Any advice/suggestions would be much appreciated. I can provide more details if necessary, I’m not expecting to get a complete solution to this but but maybe some answers to the questions above will at least redirect me into the right direction – I’ve been at this for over 3 full days now.

    thanks in advance.

    https://www.ads-software.com/plugins/jetpack/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer ??

    Thanks for that information – but can you let me know what site you’re having this problem? Once I have that information, I’ll be better able to help.

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

    Thanks!

    Thread Starter aandreachi

    (@aandreachi)

    Thanks, I just submitted a ticket now and referenced this URL and post number. I look forward to your response.

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer ??

    Thanks! We should be in touch (if we haven’t been already) soon.

    I’ll mark this as resolved as we’re helping you via email now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Problem with Jetpack Publicize – Connect returns 404 page’ is closed to new replies.