Recent content by Jan

Fooling around I restored the psa-database from an SQL-dump in /var/lib/psa/dumps, installed the packages using the installer (was fine, this time) and executed plesk repair, which found some inconsistencies in the database. I managed to start access the webserver on 443/tcp. However, when...

Looks like I got the wrong group, 18.0 appears to be Obsidian, but I don't see how to move the thread.

Hi, I'm struggling to recover a plesk-server that has been running for a while. I have no explanation for this; I don't recall doing relevant configuration changes. Seemingly this error-state was triggered by configuring nginx to host an additional webpage on the command-line, i.e. creating a...

Hei, thanks for your message. To be more specific, I try to outline my view on <IfModule mod_proxy_uwsgi.c>. Trivially, there are two possibilities: The module is not loaded. Then postorious cannot be served and links result in http-404 This was the situation on my machine. I did not disable...

Thanks! I'm going to check it next time when restoring a backup. ... hoping that it might take some years before needing to so ;-). Regards, Jan

Hi @Mikhail_S., thanks for your answer. Regarding: I was referring to <IfModule mod_proxy_uwsgi.c> - Sorry for the confusion. IMHO this directive does not make sense. Effectively, it causes the server to answer calls to lists... with http-404 instead of http-500. This was misleading for me...

Is: In the mailman3-configuration example.com / localhost is encoded at various places: /etc/mailman3/mailman.cfg: site_owner: /etc/mailman3/mailman-web.py: EMAILNAME postorious / django3 Web-Host List (https://<domain>/mailman3/admin/sites/site/): example.com Should: 1. and 2. should be...

Edit: To be more specific: Apparently, apache2 is serving the hosts lists.luehr.tech and generating a http-404 /etc/apache2/plesk.conf.d/server.conf is the only apache2-configuration defining a vhost for lists.* - it looks like this: Listen 127.0.0.1:7082 http <VirtualHost 127.0.0.1:7080...

Thanks for your feedback. Regarding 1) I don't recall any configuratiuon changes to this server. The server was basically a Debian 12 clean-install running a backup restore of a Debian 10 host. I didn't do anything else. I could if all configuration files are generated correctly - esp. w.r.t...

Updated: Your idea made the server running, again. Yet, it - IMHO - it is a bug in plesk that restoring the backup resulted in a broken webserver-configuration.

Hi, I'm using mailman3 on plesk and noticed two issues regarding the web-ui When opening the overview of all mailing-lists for a subscription, plesk has a "Manage the list" button for each list in the table. Clicking that button opens a new browser-window to - for example -...

Hi, I've restored a backup from plesk. The backup was restored on a new server to upgrade to Debian 12. Restoring the backup, I noticed: It takes a long time to restore a backup. During that time, neither RAM nor all CPU cores were used. Watching ps, I noticed at a couple of processes were...

Hi, many thanks for integrating mailman3 into plesk. I migrated the old data via plesk / backup-restore All lists and subscribe were apparently migrated by doing so. Only a few problems remain. I think it is better to address any backup/restore problems in a dedicated thread. Regards, Jan

Hi, thanks, that sounds reasonable. Do you know where I can change the settings? Thanks, Jan

Hi folks, I just went to Debian 12 (formerly Debian 10) by restoring a plesk update in my new server. It appears like there's a problem with sites proxying to apache2. This results in http-500 for end-users nginx logs jluehr.de, request: "GET /favicon.ico HTTP/2.0", upstream...