Recent content by Powie

doesn't help... also exist on docker port forwards by ipv6. investigating more n ngnx config now

Only on one Server, we are facing the issue that No Sites are reachable by IPv6. Theres the upstream Error in the logs. No Idea why.. We tried the plesk repair tool and also checked fail2ban but got No Idea. IT works on Pages with nginx only settings, but Not for default Setups with...

Thanks for this, It seems that this fixes the issue. It seems that also the database was linked to the wrong user account. Error: Warning: Database "joomla_8" The database 'joomla_8' belongs to the other subscription 'xxxxxxxxxx' and cannot be backed up. To fix it reassign the database via the...

Any idea? On daily backups this log entry is generated: Warning: Application "joomla" Unable to back up APS controller data. Error: resource of type aps.environment with id f878015c-8d3a-4c3b-a90f-613f3ae1c961 not found by brokers Tryed plesk repair db, but this doesn't help.

Additionally, we have found a second curiosity. It happens on the same servers after 18.0.34 and is also related to smtp. Also some user cannot login, denied by these message : > The mail system > > <xxxxxxxx . com>: SMTPUTF8 is required, but was not offered by host >...

We have more than one box with this prob. actually, at the next system., switching to qmail and back can't fix it. Maybee you want to have a look into. Debian 9.13 also!

There are no changes in this file after switching back to postfix.....

With a bad feeling....... Switched to qmail, and back to postfix. Fixed the problem!

Same problem here after the latest Plesk Update.... Removing the slash from saslauthd_path: /private/plesk_saslauthd only produces other errors......

And just as an addon. Via https it's possible to add a repo by: https://gitlab-ci-token:<TOKEN>@gitlab....... If I try this, Plesk responds with" this an unsecure password". .......

Wow... Thx @IgorG .. The fix works!

+1 this is a must have feature. Today we have the repo two times on the server and must push to two different origins to deploy live or staging. Expected is: Push with tag "live" deploy to www.example.com Push with tag "dev", deploy to staging.example.com

We have our own Gitlab, offering SSH at port 2224. We have absolutely no problem in using Gitlab with ceratin tools. The Plesk Extension isn't possible to connect to gitlab. I think it's a problem by the extension and how known_host are stored. As the SSH user of the domain I can pull and push...

Yes..... the rule is: you can only have one slave dns extension at a time. Install a second one breaks the other.....

hmm..... nothing changed on the server, only displayed.