is there any program for windows that i can put all of my domains and my clients personal info and keep an eye when a domain is going to expire or in which server is a domain... or who client has a domain etc... ?
After upgrading to plesk 12 over the weekend. None of my mail users can authenticate.I'm receiving quite a few error messages such as this for my ipmap users
authpsa: No such user 'email@example.com' in mail authorization database courier-imapd: LOGIN FAILED, firstname.lastname@example.org, ip=[::ffff:22.214.171.124]
I've tried running mchk --with-spam command. But it hangs at the mail_auth_dump for several hours. Checking the cpu on that command and it is sitting idle.I've tried running the mail_auth_dump.worker manually and no better luck. Still nothing on the screen just hangs as if it's asleep.
We use CentOS Linux 7.0.1406 (Core) with Plesk Version 12.0.18 Update #27.
We have the following problem:
When a user clicks on a database in his account and tries to login with phpmyadmin, Plesk prompts for a Password of that specific user. The message is (in german):
The site https://........:8443 responded with: Enter the password to log in as the database user xxxxxx
When i enter the correct password a new phpmyadmin window opens and the user can use his database. A few days ago you didnt have to enter a password at all. When you were logged into Plesk as a user, you could just click "Databases -> Webadmin" and phpmyadmin opened up without Plesk asking for a password.
The question for the password is NOT coming from phpmyadmin. Its from Plesk itself. After i enter the correct password plesk hands the request over to PMA.
For debugging i created a new database for a user and i could enter its database without any problem. No password was required. But the existing old databases now all require a password. So obviously Plesk is not aware of these passwords anymore. I guess they are/were stored somewhere.
I thought I knew enough about my .htaccess stuff to do this, but I can't seem to work it out. What I want to do is if a user visits domain.com/folder, we check to see if the folder exists. If so, show as normal (IE domain.com/support)
If a user visits domain.com/dynamicusername (dynamicusername is not a physical folder), redirect to dynamicusername.domain.com