Search results

Which version of proxmox do you have? proxmox 7+ is actually based on debian 11, so it is a lot closer to ubuntu 20 or 22 than to 18. Updates within a release should be fine either way.

The thing is, Redis and memcache require application support to be useful, while with varnish you'd rather have to take care of not caching things that should be dynamic. Like setting the browser caching parameters.

First try with other software that doesn't hide the actual problem. Second, email sending limits are for sending mail from the server. Using Outlook on port 465, you are trying to send mail to the server. Different direction, different filter.

Have you tried reordering the entries in /etc/passwd? It should use the first match for a uid ...

That may be, but the vps host will still use all otherwise unused ram for caching. How exactly it is assigned depends on whether you have a separate device/filesystem for your vps or it lives within the host filesystem. If you have a separate physical device passed through to your vps, there may...

I think you would need to have the hosting set to "Dedicated FPM application" for this to be able to work on a domain-basis at all. Otherwise that would not be possible as the normal "FPM application served by ..." pool is not unique to the individual domain.

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?