Search results

You won't see that on a vps because this layer of caching will be done on the physical host.

apt-key add plesk.gpg puts the key in /etc/apt/trusted.gpg.d/plesk.gpg. You need to copy or move it to /etc/apt/keyrings/plesk.gpg, as it apparently isn't there yet.

And the user 'root' indicates that KB might not be the way to fix it. 'admin' obviously works, otherwise the server wouldn't run.

In debian, plesk doesn't even show kernel upgrades as they require a dist-upgrade. In ubuntu, a kernel update might be done automatically by ubuntu itself if it is tagged as a security update.

What's your mysql/mariadb version?

Maybe the error message could be closer to what actually happens? Now it seems to suggest there is something wrong with the file itself.

und lieferst genausowenig Informationen. Außerdem schreibst Du in einem englischsprachigen Forum auf Deutsch. plesk -v pls.

Which steps did you follow?

Mount the new /var somewhere, shutdown database, copy everything over (cp -ai or rsync -avP), reboot to change everything to the new location.

BTW, username is not enough, it has to be username@domain because there is no other way for a mailserver serving multiple domains to know which domain's account you want to access.

This has been moved to plesk's new location (as above) during or after the dist upgrade, and then recently got the pinned key mentioned in another thread: deb [signed-by=/etc/apt/keyrings/plesk-ext-grafana.gpg] https://autoinstall.plesk.com/grafana/deb stable main The versions look fine, too...

ISTR there was something about nginx caching pages regardless of protocol, so if a page was first accessed with http, all the links and ressources of the cached page will be wrong when accessed with https, and vice versa ... no idea whether that's still a problem Having varnish between nginx and...

Hi, in Monitoring I only see empty graphs: I first noticed this after upgrading from debian 9 to 10 and then to 11. There are no errors about grafana or monitoring logged in panel.log, only four [2023-04-13 00:00:01.829] 1920545:643729e1ca6ea ERR [panel] Unable to get key: Repository is not...

Just curious: Do pop3 or SMTP work with SSL?

Does this happen when registry.xml grows too big? It was 65768 bytes here (just over 64KB), and after removing and retrieving it has just 950 bytes.

We proxy through nginx for a reason. Apache in general is slower than nginx, so attacking apache directly puts more load on the server. Best practice is that attack surface should be minimized. Services that don't need to listen on a public IP shouldn't. Apache might have different...

Do you have the Plesk firewall active? It is not enabled by default. And apache2 itself binds to any IP as visible with netstat, while in /etc/apache2/plesk.conf.d/ip_default or vhosts the domains are bound to the IPs, which is completely unnecessary for domains cached by nginx. If no domain is...

I usually use grep "SASL LOGIN authentication failed" /var/log/mail.info |cut -f 5 -d ":"|sort|uniq -dc and null-route the more obnoxious ones with route add -net 194.55.224.0/24 lo if there are several in the same net or route add -host 195.133.40.157 lo for single hosts.

And ssh from a shell on the target server works too?

Okay, I think I know what happened: Starting with the upgrade to 18.0.49, plesk explicitly pins the pgp key for the plesk repositories: add line 'deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.49_10759/ bullseye all' to temporary source list...