Search results

I can confirm after using the "Webserver Configurations Troubleshooter" and chose to "Rebuild"->"All" - nginx -t reports no more warning (or errors)

thanks to @learning_curve for reminding me about the config troubleshooter, I used it to regenerate all the webmail configs.

is there a way to repair the webmail config like there is the cmd for the vhost config: plesk repair web domain.tld?

I did a recent update from debian 9 to 10 and I did encounter the same issue - and today there was an update to the bind package which changed my /lib/systemd/system/bind9.service back to containing "type=forking" and the missing -f. is there something broken with my bind install that is does...

no its a problem with how plesk generates the nginx config for domains with alias domains.

okay but @Tim_Wakeling also does not seem to use kolab so my problem is exactly the same as his. but I will try to open a new support ticket. but it seems its a problem with /usr/local/psa/admin/conf/templates/default/domain/nginxDomainVirtualHost.php Line 9 is missing the http2 directive code...

no.

yes I have also lots of these lines: nginx: [warn] protocol options redefined for 192.168.101.1:443 in /etc/nginx/plesk.conf.d/vhosts/xxxx.at.conf:6 nginx: [warn] protocol options redefined for 192.168.101.1:443 in /etc/nginx/plesk.conf.d/vhosts/xxxx.at.conf:23

no it does not change anything about the warning, it only adds some additional server_name entries to the upper "offending" server section.

I have the same issue. some domains have this warning - I have no extra config in /etc/nginx/conf.d/ or in the main nginx config file. Its affecting subscriptions with alias domains which redirect to the main domain. see this plesk generated config: and the plesk generated part for the alias...

any eta on a fix?

Okay I can also reproduce the issue on the same server - I created a subscription testdomain.local and added three local git repositories. then I created a backup for this subscription. deleted all three repositories did the restore from the backup for the "whole subscription" and after the...

Should I open a normal thread here in the forum about this error when restoring?

I can report that it also happens if I only restore a site or subdomain from the backup. the only error in the restore log relevant is: "Failed to restore the extension git: This directory is already protected." though I have no idea what this could mean.. and also it only shows up two times...

Username: TITLE Backup restore git repository missing PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.44 Update #3 on Debian 9.13 PROBLEM DESCRIPTION When restoring a full plesk server backup created on a 18.0.44 U3 Debian 9.13 to an fresh install 18.0.45 U2...

sorry quick followup: I only removed the Type=forking from then I followed the link above to fix apparmor then I made sure apparmor is running and then I could start bind again

But I can report that I have the same issue after following the upgrade steps! after changing it to -f $OPTIONS I get: Jul 27 01:12:11 lemon named[2607]: open: /etc/named.conf: permission denied Jul 27 01:12:11 lemon named[2607]: loading configuration: permission denied Jul 27 01:12:11 lemon...

May I hijack this thread for a question of my own regarding the dist-upgrade? switching to MSMTP wants me to wants me to uninstall dovecot - is this really necessary? will this remove mailboxes from the server or will they be there after I reinstall dovecot after the upgrade? what happens if I...

Hi, yes bind9 is needed for the DNS management functionality of plesk - maybe this will help you: https://talk.plesk.com/threads/dns-does-not-start-via-systemd.351184/ it seems you bind9 is also started with /usr/sbin/named $OPTIONS but it should be /usr/sbin/named -f $OPTIONS

follow-up: fortunately they realised the issue and fixed it!