Search results

Ah, not I had not expected mail to stop working. And you are right of course - it shouldn't happen. I would love to know if it was due to the domain being disabled. My thinking is that, at one time, migrating a disabled domain did not migrate, for example, database users. This was a bug fixed...

I'm guessing this is sort of expected. The migrated domain is recreated to use the appropriate settings for having an exclusive IP. I would guess that if y.y.y.y had been an external IP, it would not have been changed. The thing that may have triggered this is the domain being suspended, but...

Hmmm.. Check the domain's php.ini (/var/www/vhosts/domain.tld/etc I think) ; For Win32 only. ; http://www.php.net/manual/en/mail.configuration.php#ini.sendmail-from sendmail_from = address@domain.com ; For Unix only. You may supply arguments as well (default: "sendmail -t -i"). ...

Thanks for this modified file, gggino. It has allowed me to rebuild the static files that were not building on my system and I'm really grateful! However, can I ask why you had to make so many modifications? Did you find it was doing things you didn't want? Specifically, why not just set...

OK, here's a bit of an update. I changed all the values of stat_ttl in dom_params to 12 and run the statistics program for one domain and .... no change (at least on 10.4.4 -- I know this is the 12.x section of the forum so I need to emphasize this) But then I did succeed in rebuilding the...

I'm having the same problem (But on Plesk 10). In my case, the value of stat_ttl in dom_param for the domains in question is 3 rather than the wanted 12. If you take a look at http://kb.odin.com/en/6246 you'll see more detail on the stat_ttl issue. You'll see that there is a stat_ttl value...

You need to check the logs. One possibility is that your system is being attacked by a botnet or an individual who is constantly trying to guess passwords or access xmlrpc.php. Both of these can cause quite a high load. Also, you should limit the number of apache processes that can run at any...

I'm sure you have fixed this by now, but for future reference there are two ways around this. First, search your system to see if you have the appropriate psa-qmail rpm downloaded somewhere (e.g. in /root/psa/something ) - you can use the locate command to look for it. Then you can use the rpm...

You shouldn't really have the Atomic repo enabled unless you need something from it specifically - it isn't something to enable and forget about, if you see what I mean. It is quite an advanced repo, with many interesting packages and personally I can't live without it, but you need to be...

Ideally this shouldn't be in httpd.conf because this file is prone to be overwritten by Plesk, especially during an upgrade. The best solution is to put it in /etc/httpd/conf.d/mod_deflate.conf (create the file if it doesn't exist) (exact location may vary from os to os -- this is where you'd...

Not really, no. There are two issues to deal with. First of all, a normal SSL certificate ONLY works with the domain (the WHOLE domain) you use when you request it. So, for example, an SSL certificate for www.domain.tld will not work with mail.domain.tld In order to cover *.domain.tld you...

It might be worth checking that you aren't running out of disk space or inodes. I'm not sure that a reboot would resolve a problem with lack of disk space unless it cleaned some files out on boot, so it is unlikely that I'm correct, but it is worth checking just the same.

Try this from your PC: ping mail.domain (does it return the correct address?) telnet mail.domain 25 (does it connect or not?) Also try it from your server. It may be that port 25 is blocked, or that the IP is wrong.... Oh, also CNAME for MX record is not recommended. I suggest you...

You need to resolve the problem of being blacklisted before you continue. What caused it? A spam outbreak? If that has been resolved then you can de-blacklist. There is no problem with having just one IP. Typically, in terms of DNS, the test that is done by receiving mailservers is simply...

There's no need for a dedicated IP and SSL for each domain. The idea is that you have only one domain (e.g. yourhostingcompany.tld) with a dedicated IP and SSL certificate (which is then configured to be used for email as well as web). Then (and this is the crucial bit), you tell your...

This option only works with Postfix, not Qmail. So if you are not using it already, you will need to switch to Postfix. However, if you only have two IPs, all you really need to do is route traffic on port 25 to go out via the other IP. If that's all you want to do, you have a couple of...

The iptables code that Leonard was suggesting would only work for SSH (port 22) not 443 (https). But anyway, as you say, the IPs are from all over the place and you can't restrict 443 otherwise nobody would be able to connect to secure sites. Does this second site need https? If not, just...

ON the face of it, this looks like an attempt to attack/compromise the site . All the IPs look different in your screen shot, so firewalling them may be difficult

For the domain you will be basing your namservers on, you need to create nameserver host records via your registrar's control panel. So, if you want to use ns1.yourdomain.com and ns2.yourdomain.com as namservers, you have to: 1) In Plesk, add A records in yourdomain.com pointing...

I don't fully understand the problem, so take what I say with a pinch of salt: The concept of primary/secondary and master/slave is more of a convenience or convention than anything. In terms of DNS records, there is no difference between ns1 and ns2. They are both nameservers and nothing...