Skip to content
  • Solutions
    By Role
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    By Infrastructure
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
  • Product
    • Plesk Features
    • Plesk Editions
    • What’s new
    • Pricing
    • Roadmap
    • Lifecycle Policy
    • Extensions Catalogue
  • Pricing
  • Extensions
    Featured Extensions
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    Bundles and packs:
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack

    See all Extensions

  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
Plesk 360 login
Free Trial

Knowledge Base

NGINX SSL reverse proxy error: recv() failed (104: Connection reset by peer) while reading response header from upstream

 
2022apachednsdomainsgo

Symptoms

  • Multiple nginx errors similar to the following are found in /var/www/vhosts/example.com/logs/proxy_error_log:
2022/11/28 15:08:12 [error] 2680#0: *636733 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 15:42:35 [error] 2680#0: *649874 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 15:45:50 [error] 2680#0: *651394 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 16:58:16 [error] 2680#0: *683892 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 15:08:12 [error] 2680#0: *636733 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 15:42:35 [error] 2680#0: *649874 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 15:45:50 [error] 2680#0: *651394 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"
2022/11/28 16:58:16 [error] 2680#0: *683892 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 203.0.113.2, server: example.com, request: "POST /wp-comments-post.php HTTP/1.0", upstream: "http://203.0.113.1:7080/wp-comments-post.php", host: "example.com", referrer: "http://example.com/how-to-test/"

Cause

This error can appear due to the use of the Nginx reverse proxy web server without ensuring that you are passing your SSL when proxying all connections.

Resolution

1. Log into Plesk

2. Go to Domains > example.com > Hosting & DNS > Apache & nginx Settings

3. Add the following line in Additional nginx directives

proxy_ssl_server_name on;

4. Scroll down and press OK to apply the changes.

If this additional setting is needed for several domains, you can apply it by using the information in the following article:

How to update the "Additional nginx directives" field for all/several domains in Plesk – Plesk

Additional information

NGINX - Alphabetical index of directives

 

Tweet
Share
Share
Email
0 Shares
Read the full article
Related Posts

How to Host a Go App on Plesk

Read More »

Your Complete .htaccess Guide: Including .htaccess Basics and More

Read More »

NGINX vs Apache – Which Is the Best Web Server in 2024?

Read More »
Knowledge Base

How to enable Nginx caching in Plesk?

Read More »

Domain is down on Plesk: HTTP Error 403.503 – Forbidden

Read More »

Upload of a big file on websites hosted in Plesk fails: client intended to send too large body

Read More »

Pages of a website hosted in Plesk fail to load: Size of a request header field exceeds server limit

Read More »

Hosting Wiki

  • Django
  • Server Redundancy
  • Google Cloud CDN
  • Bare Metal Server
  • PhpMyAdmin
  • phpPgAdmin
  • Oracle VM Server
  • Server Virtualization Software
  • Windows Server
  • Linux
  • PHP
  • MongoDB
  • HTTP/3
  • HTTP/2
  • Domain
  • Hosting Control Panel
  • Plesk
  • Lighttpd
  • Apache Tomcat
  • NGINX
  • Apache
  • Web Server
  • Static DNS
  • DNS Server
  • DNS Forwarding
  • Reverse DNS
  • SSL
  • Colocation Hosting
  • Reseller Hosting
  • Cloud Hosting
  • VPS Hosting
  • Dedicated Hosting
  • Shared Hosting
  • Free Hosting
  • Managed Hosting
  • HTTP
X-twitter Linkedin Youtube Reddit Github
  • Product
  • Login
  • Pricing
  • Editions
  • For Partners
  • Partner Program
  • Contributor Program
  • Affiliate Program
  • Plesk University
  • Company
  • Blog
  • Careers
  • Events
  • About Plesk
  • Our Brand
  • Resources
  • User and Admin guides
  • Help Center
  • Migrate to Plesk
  • Contact Us
  • Hosting Wiki
  • Forum
  • Legal
  • Legal
  • Privacy Policy
  • Imprint

© 2025 WebPros International GmbH

Part of the WebPros®  Family