Recent content by BoMbY

Thanks for the answer. There is currently not much going on, on this server (not transferred all domains to it): .---.-------.--------------------------------------.-----------------.------------------.---------------. | E | prior | address | name |...

Hello, there seems to be a 30 seconds delay in SASL authentication, when the Plesk Milter is activated, which causes timeout problems with some clients. Example: Aug 9 17:41:08 lvps91-250-X-X postfix/smtpd[23969]: connect from mail-we0-f177.google.com[74.125.82.177] Aug 9 17:41:38...

Okay, maybe this is a Kernel or Virtuozzo problem, or something like this, because this is running on a vServer - but maybe someone got an idea? This are the ip6tables rules generated by the Plesk Firewall module on my CentOS 6.4 vServer: Chain INPUT (policy DROP) target prot opt...

Well, I'm using Plesk for several years now, and this was the first time a config file (other than the Plesk specific config files in the /conf.d/ directories) in /etc/ was hard replaced by an update. But sure, I'll be more careful now, as I now know, I cannot depend on that anymore. Edit: And...

Wait, what? Are you just saying the passwords aren't stored securely (salted hash), or as plain text in a secondary location?

This seems to be a silent update, something after MU #53. I got an error with the domain template generation, because my nginx.conf was replaced with the default version, but my "custom/domain/nginxDomainVirtualHost.php" depended on that config.

Sounds more like an incomplete backup task, with the offline-option enabled, to me.

Hi, just want to let you know: The auto update this night has replaced my modified nginx.conf with the default version ... Regards, BoMbY Edit: Seems like the Plesk auto update upgraded nginx to "1.5.0-1.13060711.centos6" this night? This isn't in the changelog and this isn't MU #53, right...

Hello again, I've done a dist upgrade to 10.04 and updated Plesk to 10.3.1. The ip6tables accepts the new icmpv6 subtypes now, but Plesk is still not providing them. Is there a trick to tell plesk it is working now? Thanks and Regards, BoMbY

Okay, I was wrong about the netmask - the problem seems to be, it doesn't accept the last 0 anymore. If I use "89.0.0.1/15" for example, it seems to work.

Hello, since I've upgraded to 10.3.1, the Plesk firewall does not allow to safe rules containing IP ranges like 89.0.0.0/15 or 209.85.128.0/17, only the netmasks /8 and /16 seem to be accepted. It was working well in 10.2.0 - is there a way to get the old behavior back? Thanks and regards...

Okay, maybe you are not supporting IPv6 on Ubuntu 8.04, but ICMPv6 in ip6tables seems to be the only thing not working right. Wouldn't it be possible to implement a fallback rule for older systems, other than the one I'm currently getting?

This is not what I get on my system (Ubuntu 8.04), I get what I've previously posted: Could this be because some older Linux versions are not supporting the type or code for ICMPv6 (I think I've read this somewhere)?

Well, I thought maybe something like "allow ping on IPv4, but not on IPv6", so both option would be nice. Maybe it would be nice to make it possible to choose the destination (and protocol - currently only TCP and UDP can be selected) freely? So if I've more than one IP address, i could create...

Okay, if I set Ping to allowed in Plesk, it get's translated to in ip6tables. I would expect an ICMPv6 rule: