Remote site not accessible (HTTP 413)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author tamlyn

    (@tamlyn)

    7 years, 8 months ago

    Pushing from remote to local rarely works as your local is not generally web-accessible. HTTP 413 means “Request entity too large”. Has your database grown recently? What remote server stack are you using? Maybe try some of these suggestions http://stackoverflow.com/questions/18121227/how-to-avoid-request-entity-too-large-413-error

    devdonkey

    (@devdonkey)

    7 years, 7 months ago

    Im getting an HTTP0 trying to pull from live to local. Any ideas?

    vongoh

    (@vongoh)

    7 years, 7 months ago

    I’m also getting this error trying to push from my localhost to the live site.

    The database pulled down from the live server just fine. Going in the other direction (local to live) is what gives the error. The database is small – just over 1MB (1.08MB).

    The link you referenced above talks about the client_max_body_size directive. Where is this directive and what is it referring to? Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Remote site not accessible (HTTP 413)’ is closed to new replies.