• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Plesk 502 bad gateway (104: Connection reset by peer) while reading response header from upstream

Busi

New Pleskian
After doing a clean install of my dedicated debian and a clean install of plesk i started getting error 502 bad gateway diffend places already at where i had to put in my license key but i got past that but now everytime i try and add a extension from either zip file or catalog i get it again. the sw-cp-server log shows


2016/10/10 04:41:58 [error] 13365#0: *557 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2.104.126.106, server: , request: "POST /admin/module/install-from-catalog/uuid/f6847e61-33a7-4104-8dc9-d26a0183a8dd?_randomId=97162 HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "digfordiamonds.com:8443", referrer: "https://digfordiamonds.com:8443/admin/module/catalog"


I have already tried to increase
fastcgi_buffers 32 32k;
fastcgi_buffer_size 64k;

with no luck at all. and I'm lost on what to do :(
 
Do you have fail2ban activated? Have you whitelisted localhost (127.0.0.1/8) and your public IPv4 address?
 
Back
Top