Search results

I guess the duplicate entry should be harmless, but maybe it was a problem for Plesk anyway. I don't know if it'll fix your problem, but at least it shouldn't hurt to remove the duplicate hostname entry.

I'd try changing that line in /etc/hosts to just this:

You can switch from qmail to Postfix if you're running Plesk 9.0. Have you tried that?

That configure reverse option is something on your provider's servers, so that should just work. If it doesn't, contact them. It might be cached on your side though. Flush your DNS cache or check on another machine. And just remove all PTR records in your domain's DNS zones (and in the DNS...

There are two things here and you can take care of at least of one of them. 1. Check your DNS zones in Plesk and see if they have PTR records in them. You should probably delete all of them, since you don't control your own IP range (if you did, you'd know). This should take care of the...

There are a million threads on upgrading PHP and MySQL on these forums and it doesn't have a lot to do with Plesk. Plesk doesn't distribute PHP and MySQL, but uses whatever version of PHP and MySQL is installed on your system (so, usually whatever version is shipped by the distribution you're...

You can install your own phpMyAdmin using a global alias, so you don't need to install it for every domain. Even better: install it on an SSL-enabled domain and let your customers use that copy. Replacing the phpMyAdmin in Plesk is probably not something you want to do yourself, as that one...

There is no Plesk-specific config needed. As far as phpMyAdmin is concerned, you're just running a plain MySQL server (and you are, really).

I wouldn't know why this wouldn't work under Plesk 9. It's the same Apache after all. I just install the phpMyAdmin package from the EPEL repository. That's even easier to set up, and yum keeps it up to date for me.

I've seen the random domain thing happen when DNS zones incorrectly contain PTR records (reverse DNS). You only need one PTR record for an IP address (e.g. server.example.com), and I guess that most people that rent a server don't even manage their own IP ranges (ask your service provider to...

I believe the Apache user is wwww-data or something like that on Debian/Ubuntu.

That's exactly why we don't recommend using Fedora for production servers. It's a nice distro, but long lifecycles are what's really nice for production servers. Check out CentOS for instance, you get seven years of updates per release.

Not all problems need a technical solution. Can't you just tell them that they shouldn't change Plesk's admin password without your knowledge or there'll be trouble? You could also disable the password change button, but of course it can be added again by anyone logged in as admin.

AFAIK there is no configuration in Plesk for this. It should just work. Have you checked /etc/syslog.conf? It should contain this for mail logging:

No log entries sounds suspicous. /var/log/maillog is not used, at least not with Plesk on CentOS, but our /usr/local/psa/var/log/maillog files certainly contain quite a number of entries. Note that Courier (for POP3 and IMAP) also logs to this file.

Please don't crosspost. Answer is in the other thread you opened: http://forum.swsoft.com/showthread.php?t=56750

The maillog file can be found in PRODUCT_ROOT_D/var/log/maillog, which works out to /usr/local/psa/var/log/maillog on our CentOS servers.

The admin can do anything (including running commands as root). You cannot limit admin's powers.

The Plesk administrator's account has been 'admin' for as long as I can remember, not 'root'.

What do you mean by 'your' Plesk username? If you're logged in at the command line, you used a system account to login and you probably know the username you used to log in, right? The Plesk accounts are stored in the psa database.