Search results

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.

I think you have a fundamental misunderstanding how a MitM attack works. In case of such an attack, the attacked user wants to contact the plesk server, but instead contacts the MitM server because someone managed to tweak DNS or routing or whatever. Now why would that MitM server tell the...

And that's exactly what it does. Your user authenticated as user@localdomain.com, and then tried to send as user1@externaldomain1.com. Which was corrected to the address the user authenticated with.

This is in the context of MitM attack. Why would a MitM require STARTTLS?

That's the same file you tried this on before (chattr follows the symlink). You are supposed to edit the resolvconf.conf file, like explained in @AYamshanov's link.

What exactly is complaining about insufficient storage? After all, if you haven't removed the old mail spool yet, you haven't gained any space on the root filesystem.

No. You are getting that message because the server detected an incoming mail as spam and lists the reasons for the classification and their respective score. Blocked RBL queries do not count towards the score (they're all listed as 0.0), so it means that mail does already get a high score from...

Where did you put that? Directly in nginx.conf, under conf.d/, under plesk.conf.d/ ..?

Not only cron; those settings are only applied to the respective fpm pool. Generally, you can use /opt/plesk/php/8.3/bin/php -i to view the effective config and the files it got loaded from.