• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Mailman 502 Bad Gateway

D

daniiii_e

Basic Pleskian
Hi all,

i have installed Mailman on my Plesk Oynx Server. After i add a Mailing List to a Domain i want to open the configuration page lists.domain.tld but i got a 502 Bad Gateway.

Is this Problem known?


Code: 
2017/01/12 21:26:23 [error] 31871#0: *106 connect() failed (113: No route to host) while connecting to upstream, client: 109.42.0.156, server: ci.nothing.de, request: "GET /cgi-bin/mailman/listinfo/jzl HTTP/1.1", upstream: "http://*.*.*.:8080/cgi-bin/mailman/listinfo/jzl", host: "lists.nothing.info"
2017/01/12 21:26:26 [error] 31871#0: *106 connect() failed (113: No route to host) while connecting to upstream, client: 109.42.0.156, server: ci.nothing.de, request: "GET /favicon.ico HTTP/1.1", upstream: "http://nothing:8080/favicon.ico", host: "lists.nothing.info", referrer: "http://lists.nothing.info/cgi-bin/mailman/listinfo/jzl"
2017/01/12 21:27:59 [error] 31871#0: *139 connect() failed (113: No route to host) while connecting to upstream, client: 109.42.0.156, server: ci.nothing.de, request: "GET /cgi-bin/mailman/listinfo/jzl HTTP/1.1", upstream: "http://nothing:8080/cgi-bin/mailman/listinfo/jzl", host: "lists.nothing.info"
2017/01/12 21:28:02 [error] 31871#0: *139 connect() failed (113: No route to host) while connecting to upstream, client: 109.42.0.156, server: ci.nothing.de, request: "GET /favicon.ico HTTP/1.1", upstream: "http://nothing:8080/favicon.ico", host: "lists.nothing.info", referrer: "http://lists.nothing.info/cgi-bin/mailman/listinfo/jzl"


This was my log at the installation:

Code: 
After this operation, 36.2 MB of additional disk space will be used.
Selecting previously unselected package mailman.
(Reading database ... 126785 files and directories currently installed.)
Preparing to unpack .../mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb ...
dpkg: error processing archive /var/cache/apt/archives/mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
find: `/usr/lib/mailman': No such file or directory
Selecting previously unselected package psa-mailman-configurator.
Preparing to unpack .../psa-mailman-configurator_17.0.17-ubuntu14.04.build1700161028.14_amd64.deb ...
Unpacking psa-mailman-configurator (17.0.17-ubuntu14.04.build1700161028.14) ...
Errors were encountered while processing:
 /var/cache/apt/archives/mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ERROR: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Please contact product technical support.
exit status 1

Testet on two different Plesk Servers


I think it is a bug

---------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Product version: Plesk Onyx 17.0.17 Update #12
Update date: 2017/01/12 21:45
Build date: 2016/11/17 16:00
OS version: Ubuntu 14.04
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2

PROBLEM DESCRIPTION

Problem with the Mailman installation. After The Installation Bad Gateway on lists.domain.tld

STEPS TO REPRODUCE

install mailman

--------------------------------------------------------------
 
Last edited:
Try to reinstall mailman component with

# plesk installer --select-release-current --remove-component mailman
# plesk installer --select-release-current --install-component mailman
 
Hi
I have done this already. The Problem ist still present. Ist mailman working in you plesk Installation?

I have this Problem with a new plesk Installation i have testet it in a Demo virtual machine
 
Code: 
psa-mailman-configurator is already the newest version.
Suggested packages:
  lynx listadmin
The following NEW packages will be installed:
  mailman
Preconfiguring packages ...
0 upgraded, 1 newly installed, 0 to remove and 15 not upgraded.
1 not fully installed or removed.
Need to get 0 B/4223 kB of archives.
After this operation, 36.2 MB of additional disk space will be used.
(Reading database ... 126785 files and directories currently installed.)
Preparing to unpack .../mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb ...
dpkg: error processing archive /var/cache/apt/archives/mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
find: `/usr/lib/mailman': No such file or directory
Errors were encountered while processing:
 /var/cache/apt/archives/mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ERROR: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Please contact product technical support.
exit status 1

Code: 
Installation started in background
Auflösung der Paketabhängigkeiten wird geprüft.
Pakete werden installiert
Reading package lists...
Building dependency tree...
Reading state information...
psa-mailman-configurator is already the newest version.
Suggested packages:
lynx listadmin
The following NEW packages will be installed:
mailman
Preconfiguring packages ...
0 upgraded, 1 newly installed, 0 to remove and 15 not upgraded.
1 not fully installed or removed.
Need to get 0 B/4223 kB of archives.
After this operation, 36.2 MB of additional disk space will be used.
(Reading database ... 126785 files and directories currently installed.)
Preparing to unpack .../mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb ...
dpkg: error processing archive /var/cache/apt/archives/mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
find: `/usr/lib/mailman': No such file or directory
Errors were encountered while processing:
/var/cache/apt/archives/mailman_1%3a2.1.16-2ubuntu0.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: Ein Fehler ist aufgetreten bei dem Versuch, Pakete zu installieren.
Achtung! Ihre Software ist vielleicht nicht betriebsbereit.
Bitte kontaktieren Sie den technischen Produktsupport.
 
Code: 
2017/01/08 11:54:52 [error] 31656#0: *241719 connect() failed (113: No route to host) while connecting to upstream, client: 89.204.138.104, server: xxxxxxxx, request: "GET /cgi-bin/mailman/options/xxxxx HTTP/1.1", upstream: "http://192.168.133.108:8080/cgi-bin/mailman/options/jzl/xxxxxx", host: "xxxxxxx"
 
Last edited:
You must log in or register to reply here.

Similar threads

Mario Chamorro
Input Webmail 502 Bad Gateway
Replies
0
Views
2K
Mario Chamorro
Mario Chamorro
A
Issue 502 Gateway error with HTTP POST Requests but not GET requests
Replies
3
Views
2K
Maarten
M
T
Issue Unable to access to my Plesk interface (502 Bad Gateway)
Replies
1
Views
902
Kaspar
K
A
Issue Server Error 502 Bad Gateway /
Replies
11
Views
4K
dlabsnl
D
F
Issue upgrade ssd make plesk down
Replies
3
Views
1K
Peter Debik
P
Back
Top