Search results

Usually you don't need /home at all. What is there in /home anyway? All subscription users should have their $HOME under /var/www/vhosts. Growing partitions is safe. I would copy the content of /home to e.g. /home2, then kill the mountpoint and the entry in /etc/fstab, rename /home2 to /home...

Only if it has write access to /var/log/.

Does the dovecot user have write access to that logfile?

What is the exact line in the sources.list[.d]?

du only considers files that are actually present in the file system. It is possible to create a file, keep it open and delete it. Such a file will still be able to be used for all practical purposes while it is open, keeping its allocated disk space until it is closed, when the space will be...

We have everything (mail, subdomains) except www. of our main domain hosted on our plesk server. /well-known/ is mounted via sshfs, and there's a cronjob copying the certs over (and reloading nginx). Bit kludgy, but works so far.

Some subprocess might be dropping privileges, though. And that would be blocked by the --- for "other".

What are the permissions of /mnt?

Assuming this is a v6 problem, that should be ::1/128.

Waaait ... that's an nginx error. htaccess won't help there because nginx doesn't touch htaccess. Were those websites mistakenly set to nginx only instead of nginx proxy to apache?

Could you please screenshot what exactly you selected?

You seem to have a fundamental misunderstanding how VPS work. When memory allocation is dynamic, your provider might have underprovisioned/overbooked the VPS host and not actually have enough physical memory to guarantee you these 8GB. Probably another tenant on the same VPS host started to use...

But you didn't restore the Plesk backup with Plesk?

Probably yes. Does any of the nameservers you configured in Plesk, old or new, show up there?

Should be restorable with a current version. After all, the recommended way to upgrade the OS and Plesk is to migrate/restore, so it has to be able to process older backups.

What kind of backup?

try aptitude instead, it should be able to provide suggestions how to fix this

I think you have misunderstood something here. The nameservers from the hoster are only relevant for your domains' NS records if they are supposed to be authoritative for those domains (i.e. configured as such at the domain registrar). If your domains and nameservers are at a completely...

Don't forget to set RemoteIPInternalProxy 192.168.2.2 too.

No. Hosting of server and domain is separate in principle, you don't have to change the domain registrar when you move your server elsewhere, so this is not a bug.