Title: The gateway did not receive a timely response from the upstream server or applic
Last modified: August 30, 2016

---

# The gateway did not receive a timely response from the upstream server or applic

 *  [seLuFerrando](https://wordpress.org/support/users/seluferrando/)
 * (@seluferrando)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/the-gateway-did-not-receive-a-timely-response-from-the-upstream-server-or-applic/)
 * Goog morning,
    I can’t connect my jetpack. I haven’t active pluggin, except jetpack.
   I tried with default themes to. I I increased memory allocated in wp_config.php
   to 96M.I get all times the same error 504. In grupomarsal.com/phpinfo,php you
   can see php info.
 * Thanks in advance.
 * [https://wordpress.org/plugins/jetpack/](https://wordpress.org/plugins/jetpack/)

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

 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [10 years, 6 months ago](https://wordpress.org/support/topic/the-gateway-did-not-receive-a-timely-response-from-the-upstream-server-or-applic/#post-6559824)
 * I’m sorry to hear you’ve run into issues.
 * Could you check your server error logs around the time when you experienced the
   issue, to find out more about the error?
 * If you don’t know how to access your server error logs, your hosting provider
   should be able to help.
 * Let me know how it goes.
 *  Thread Starter [seLuFerrando](https://wordpress.org/support/users/seluferrando/)
 * (@seluferrando)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/the-gateway-did-not-receive-a-timely-response-from-the-upstream-server-or-applic/#post-6559831)
 * The debug of jetpack say:
 * Parece que su sitio no se puede comunicar correctamente con Jetpack.
 * SELF:
    Array ( [headers] => Array ( [server] => nginx [date] => Mon, 21 Sep 2015
   14:33:57 GMT [content-type] => text/plain;charset=utf-8 [connection] => close[
   x-pingback] => [https://jetpack.wordpress.com/xmlrpc.php](https://jetpack.wordpress.com/xmlrpc.php)[
   expires] => Wed, 11 Jan 1984 05:00:00 GMT [cache-control] => no-cache, must-revalidate,
   max-age=60 [pragma] => no-cache [x-hacker] => Jetpack Test [x-ac] => 3.ams _dfw)
 *  [body] => {“error”:”Jetpack not connected”,”error_description”:”We were unable
   to find a Jetpack instance on your site. Please connect Jetpack to your WordPress.
   com account from within your WordPress admin.”}
    [response] => Array ( [code]
   => 400 [message] => Bad Request )
 *  [cookies] => Array
    ( )
 *  [filename] =>
    )
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [10 years, 6 months ago](https://wordpress.org/support/topic/the-gateway-did-not-receive-a-timely-response-from-the-upstream-server-or-applic/#post-6559832)
 * Did you have a chance to look at your server error logs to find out more about
   the problem? Jetpack’s debug won’t help us much here, I’m afraid.

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

The topic ‘The gateway did not receive a timely response from the upstream server
or applic’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

## Tags

 * [timeout](https://wordpress.org/support/topic-tag/timeout/)

 * 3 replies
 * 2 participants
 * Last reply from: [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * Last activity: [10 years, 6 months ago](https://wordpress.org/support/topic/the-gateway-did-not-receive-a-timely-response-from-the-upstream-server-or-applic/#post-6559832)
 * Status: not resolved