Is it possible to change the default Language to Spanish (or other)?
RESOLUTION
Yes. It can be done at the “Server->Server preferences” page in Plesk CP with “Default locale” setting. Of course you have to have additional language packs installed.
Is it possible to change the default Language to Spanish (or other)?
RESOLUTION
Yes. It can be done at the “Server->Server preferences” page in Plesk CP with “Default locale” setting. Of course you have to have additional language packs installed.
National characters are not shown in Plesk CP.
RESOLUTION
First of all, your product license key must have the Language Pack support feature. If it does not, you have to purchase it separately. Also, you will need to download and install the appropriate language pack.
How do I install a language pack?
RESOLUTION
A language pack is a regular shell script. Access the server console and execute the following command:
#sh ./language-pack-name.sh
My language is not listed in available language packs. I want to translate Plesk into my language. What shall I do?
RESOLUTION
If you cannot find your language at http://www.swsoft.com/en/download/lp/, it is possible to make your own language pack using localization kit that is avalable at http://swdn.swsoft.com/en/extensions/localization/plesk/
I cannot find CS game module on my FreeBSD Plesk 7.5.
RESOLUTION
Unfortunately, Plesk for FreeBSD doesn’t support CS game server.
Get error during Battlefield 1942 or CounterStrike modules configuration.
RESOLUTION
Errors:
0: /opt/psa/admin/plib/common_func.php3:169
psaerror(string ‘Can not create system user: ‘, string ‘cs-gs-mng failed: Can not create system user’)
1: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:146
ServerManager->createSystemUser_()
2: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:155
ServerManager->csSysUser()
3: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:235
ServerManager->viewSteamClientLicense(string ‘/tmp/cs_X64ipE’)
4: /opt/psa/admin/htdocs/modules/cs-gs/steam-autoinstall.php:92
1.- Gameserver-Installation
2.- vorhandene Installation verwenden
3.- 0: /opt/psa/admin/plib/common_func.php3:169
psaerror(string ‘Can not create system user: ‘, string ‘cs-gs-mng failed: Can not create system user’)
1: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:146
ServerManager->createSystemUser_()
2: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:155
ServerManager->csSysUser()
3: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:298
ServerManager->setCSDir(string ‘/hlds_l’)
4: /opt/psa/admin/plib/modules/cs-gs/ServerManager.php:289
ServerManager->getCSDir()
5: /opt/psa/admin/plib/modules/cs-gs/GSConfigForm.php:64
GSConfigForm->assign()
6: /opt/psa/admin/htdocs/modules/cs-gs/game-server-config.php:53
Please make sure that $PRODUCT_ROOT_D/admin/sbin/mod_wrapper has right permissions:
# ls -al $PRODUCT_ROOT_D/admin/sbin/mod_wrapper
—s–x— 1 root psaadm $PRODUCT_ROOT_D/admin/sbin/mod_wrapper
If not, set right ones:
# chmod 4110 $PRODUCT_ROOT_D/admin/sbin/mod_wrapper
Get the error “The server does not support password authentication method.” during Battlefield2 module configuration.
RESOLUTION
I do the following actions and get the error:
1. Modules
2. Game Server Operators
3. Add Game Server
4. Remote server connection details
5. Enter IP, User name, Password
6. Get Error: Failed to connect to the hosting account: bf2mng failed:
Unable to connect to XX.XX.XX.XX The server does not support
password authentication method. You should ask your game hosting
account provider to enable password authentication method.
Most probably ’sshd’ is not configured to support password authentication on the server.
Try to changed PasswordAuthentication in /etc/ssh/sshd_config to “yes” and restart ’sshd’:
# Change to yes to enable tunnelled clear text passwords
PasswordAuthentication yes
How can I run Rootkit Hunter with update option?
SYMPTOMS:
After running Plesk security check in the watchdog module I see a message
similar to the following: “Your system contains some unknown version
numbers. Please run Rootkit Hunter with the –update parameter or fill in the contact form (www.rootkit.nl)”
CAUSE:
Rootkit Hunter found new packages versions which are not listed in it’s database.
RESOLUTION:
Rootkit Hunter usually updates the database automatically. You can force update with following command:
$PRODUCT_ROOT_D/admin/sbin/modules/watchdog/rkhunter –configfile $PRODUCT_ROOT_D/etc/modules/watchdog/rkhunter.conf –update
How could a default administrative password and/or an email for a default mailman mailing list be changed?
RESOLUTION
If you forgot your mailman admin password you could run the following utility to change the password:
$MAILMAN_ROOT_D/bin/mmsitepass
If you want to redefine both the mailman admin email and the password remove current settings with the command:
$MAILMAN_ROOT_D/bin/rmlist -a mailman
and set them up anew through the interface: Server > Setup Mailman
$MAILMAN_ROOT_D path value is defined in the /etc/psa/psa.conf file.
Mailman can’t send messages to subscribers showing error in maillog: “Failure_to_exec_mailman_wrapper. WANTED_gid_110,_GOT_gid_101. (Reconfigure_to_take_101?)/did_0+0+1/”
RESOLUTION
Mailman doesn’t post messages to lists and the following message appears in maillog:
Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system’s mail server executed the mail script as group: “mem”. Try tweaking the mail server to run the script as one of these groups: [mail, postfix, mailman, nobody, daemon], or re-run configure providing the command line option: ‘–with-mail-gid=mem’.
To solve this issue follow the steps below.
- Check that /var/qmail/bin/mm_wrapper has right permissions as listed below:
# ls -al /var/qmail/bin/mm_wrapper
-r-xr-sr-x 21:06 /var/qmail/bin/mm_wrapper
If not, change the permissiond and ownership to the right ones:
# chmod 2555 /var/qmail/bin/mm_wrapper
- Make sure that ‘popuser’ UID (user ID) and GID (group ID) are 110:
# id popuser
uid=110(popuser) gid=110(popuser) groups=110(popuser)
- If popuser GID is 101 (as reported in the above error) or other number, it is needed to be changed to 110.
- Stop services which use ‘popuser’ user and group: mailman, qmail, courier-imap, xinetd or inetd. Then check that no other uses 110 GID and change popuser’s GID to 110 in /etc/group file and in /etc/passwd (using `vipw` utility):
/etc/group:
popuser:x:110:
/etc/passwd:
popuser:x:110:110:POP3 service user:/:/bin/false
- Run the following command to rebuild qmail configuration files:
# $PRODUCT_ROOT_D/admin/sbin/mchk –with-spam
-Then you need to find out all files which are owned by previous popuser GID (for example 101) and change their ownership to the new popuser group ID:
# find /var /usr/lib/mailman -gid 101 -print0 | xargs -r0 chgrp popuser
On FreeBSD:
find /usr/local/psa -group 101 | xargs chgrp popuser
- Make sure that all users in /var/qmail/users/assign has group ID110.
- Start the services back.