we're using a subdomain to point to one of our server's IP. (gaming purposes).
And people use this subdomain to connect to the game server.
However, We are going to move to a new server soon with a different IP.
I know, only thing I have to do is change the IP of the subdomain to point to the new server, however I know this will take like 1 to 48 hours to fully work.
Is there a way to force people who's still connecting to the OLD Ip to go to the new IP?
I need to change path to vhost from W:host to D:vhost
I copied all files from W to D drive and created symbollinks. Now all files stored in D:vhost and symbollincs pointing to W:vhost.
If I will use reconfigurator, will it recopy existing files or just will skip them? Because I have millions files in my vhost dir
Also i thought about change drive letter in windows OS. It wil be enough to just stop IIS service and plesk services for switching disk letter?
Can i just some how say plesk that he should search all vhost files in D:vhost? With out process of copying files,becouse thay already exist there are.
I have a dedicated server. It is a Fedora Core 6. It came with "Plesk 30 domain license". However, this license of Plesk doesn't have SpamAssassin enabled. In order to get the license with SpamAssassin, it costs an extra $30 a month.
I believe SpamAssassin by default is in fact installed on the sever, but some of my users are reporting that they are getting Spam. How can I check is SpamAssassin is running? How do I configure SpamAssassin to filter spam on all the e-mail addresses that are created in Plesk?
how to install CentOS by not using the installer. This guide should be great when installing over networks, don't have a graphical console available (for installing over serial), when you're not content with the installer's job, installing CentOS from another distro, or plainly want to learn more about how CentOS works.
Requirements: * Have a host OS that has the "rpm" package manager available. Some distributions have it in their repositories (even if the package manager for the distro itself is not rpm), and knoppix (a linux live/rescue CD) has it aboard too. You can use the first CentOS ISO CD too (use linux rescue at boot), and it has all the necessairy packages aboard * Access to the CentOS base repository. It's on the first CentOS ISO CD * Use your BRAIN. This guide is ment to be interpreted, not copy/pasted
Code: # First, setup your disks to your liking. You can use whatever you want here, # RAID, LVM, etc... Remember your disk configuration because you'll need it # to configure grub, menu.lst and fstab. Using RAID, LVM, or others will require # more configuration than this guide covers. To keep it simple I'm using a # single disk. An example:
$ fdisk /dev/sda $ mount /dev/sda3 /target $ mkdir /target/boot $ mount /dev/sda1 /target/boot
# Depending on the host OS you're using, you may need to initialize the rpm db # on the host OS $ rpm --initdb
# Use the following command to install the packages. I'll be addressing this # command as $rpm.
$ rpm --root /target -i
# Use your shell's tab completion to complete the package filenames. I # deliberatly left out the versions so these instructions apply to a wide range # of versions
# Let's install some basics $rpm setup basesystem filesystem
# Install bash first, this is needed for post-install scripts $rpm bash glibc glibc-common termcap libgcc tzdata mktemp libtermcap
# Install some dependencies (this is mainly to keep the next command smaller) $rpm grep pcre libstdc++ info ncurses zlib gawk sed ethtool
# You may also want to install your favorite editor $rpm nano
# This provides /root with some defaults, like color highlighting on `ls` $rpm rootfiles
# Right now you have system which you can chroot to, so we can start setting up # the basics
# Mount directories for chroot operation $ mount --bind /dev /target/dev $ mount -t proc none /target/proc $ mount -t sysfs none /target/sysfs $ chroot /target
# This constructs /etc/shadow $ pwconv
# Configure fstab $ nano -w /etc/fstab
# Installing the kernel. Do this back outside the chroot in the host OS system $ exit $rpm kernel mkinitrd cpio device-mapper-multipath dmraid gzip kpartx lvm2 nash tar less device-mapper-event
# Install the bootloader, grub. $rpm grub diffutils redhat-logos
# Let's chroot again to configure our bootloader $ chroot /target
# We start by configuring the bootloader. Open /boot/grub/menu.lst, and put the # following there
# If this command gives an error, you can safely ignore this because it's not # of importance. What is important is that grub-install copied the right files # to /boot/grub that we need for booting. $ /sbin/grub-install /dev/sda
# Manually install grub if the previous step failed. - means type it in the grub # shell $ grub $- root (hd0,0) $- setup (hd0)
# Optional packages # You may want to install passwd so you can set passwords ;-) $rpm passwd libuser openldap cyrus-sasl-lib
# These are used to set the keyboard language (loadkeys) $rpm kbd usermode
# ** Right now you should have a bootable system! Here are some tips to help you # through your 1st boot ***
# Most of the system configuration happens in /etc/sysconfig. See
/usr/share/doc/initscripts
for full documentation.
Some quick post-install tips: * Configure your keyboard in /etc/sysconfig/keyboard using the KEYTABLE variable
* Configure networking Take a look at /etc/sysconfig/network-scripts. See ifcfg-lo for an example.
# This recreates the RPM database. If the host OS you used has a different # version of db, rpm will complain with # rpmdb: unable to lock mutex: Invalid argument $ rpmdb --rebuilddb
I have put an Access database inside an access_db folder on Godaddy and written some .asp pages that query it. I am trying to make sure that I take necessary precautions against hackers reading or even writing to the database. Maybe someone can give some remarks about whether any of these concerns are realistic, and if so, why and what I could do about it?
1) Could someone somehow navigate directly to the database and read or write to it (the access_db folder seems to have no read/write permissions as set by default by Godaddy, but how secure is that?)
2) I permit entry through use of a a userid and password that are looked up in an mdb in the same folder (not listed in the html itself). If there’s a match, I store the userid as a session cookie. Then, to visit any other pages, each page first checks to see if the cookie is empty before proceeding. Is it possible for someone to set the cookie themselves and thus break through (can a cookie be set manually?) If so, would it help if I mandated that the cookie be set to something specific (right now it just has to be non-blank) or can they find out what the cookie should be set to as well?
I noticed, that my Plesk install still runs an older Roundcube Installation (somewhere in the 0.9 range) and RoundCube 1.0.3 is currently the latest version available at [URL]
Is it safe to upgrade the Roundcube Installation in psa-roundcube manually from 0.9 to 1.0.x?
I'm trying to create a script to archive logs for 7 days but still delete them from the domlogs daily. Has someone already done this? The ideal solution would be to modify the CPanel script that deletes them after stats run but I'm not sure if thats protected code by CPanel. The other option would be to disable the delete logs after stats run option and to create a script to copy the logs somewhere else via cron and call the script that CPanel uses to delete the logs without restarting apache. This script would also move the files through directories and eventually delete them, therfore preserving the logs for 7 days. Any ideas?
I have created an untested script which should do this but I just need to know how CPanel deletes the logs without restarting apache.
There was a file ftpquickbrute_08.05.2008_10_47_08.log Opened it up it says:
Quote:
FTP Quick Brute (called c99shell v. w4ck1ng-shell (Private Build v0.3)) started at 08.05.2008 10:47:21
No success. connections!
------------------------------------------ Done! Total time (secs.): 3.2036 Total connections: 101 Success.: 0 Unsuccess.:101 Connects per second: 31.53
all day i receved msgs of BFD someone trying acess server, how to stop it, exemple: Executed ban command:
/etc/apf/apf -d 221.186.164.233 {bfd.pure-ftpd} The following are event logs from 221.186.164.233 on service pure-ftpd (all time stamps are GMT -0500):
Oct 25 13:52:37 svr1 pure-ftpd: (?@221.186.164.233) [INFO] New connection from 221.186.164.233 Oct 25 13:52:37 svr1 pure-ftpd: (?@221.186.164.233) [INFO] New connection from 221.186.164.233 Oct 25 13:52:38 svr1 pure-ftpd: (?@221.186.164.233) [WARNING] Authentication failed for user [router] ....
Today I woke up to a couple of emails from people in China and India trying to break into my server. Then as I went to login to WHM I get this message:
This account is currently locked out because a brute force attempt was detected. Please wait 10 minutes and try again. Attempting to login again will only increase this delay.
If you frequently experience this problem, we recommend having your username changed to something less generic.
Are there ways that I can prevent these attacks? I know that the IPs involved are getting banned, but are there any other methods I should be taking?
Over the last few weeks I've been getting emails from WHM stating "x login failures attempts to account root (system) -- too many attempts from this ip"
These emails have been coming in almost hourly and it seems as though somebody is trying to guess the password to the root account and random other accounts.
For now I reduced the amount of failed login attempts to 2 before cPanel blocks the IP.
Is there any other way I can completely stop this person from even attempting to guess my passwords?
For a company I'm working at, two nodes have been brute force attempted through SSH. I've got the logs from both servers in front of me, but could anyone enlighten me of who the ISP is?
I have a managed VPS and I haven't really ever paid too much attention to the logs until now.
I noticed that the APF logs indicate a 2-5 attacks on my server attempting to log in via ssh. My system allows 10 minutes of log in failure attacks before apf bans the ip.
To eliminate the method of attack, I see 2 ways. One way is to change the SSH port; the second is to only allow ssh via specified ip's.
What are the pro's and con's of both... also are there other ways to eliminate these attacks via ssh?
And im getting the following in an email every 10 minutes:
Code: /usr/local/bfd/conf.bfd: line 26: : command not found /usr/local/bfd/conf.bfd: line 38: : command not found /usr/local/bfd/conf.bfd: line 47: : command not found /usr/local/bfd/conf.bfd: line 59: : command not found /usr/local/bfd/conf.bfd: line 60: : command not found /usr/local/bfd/conf.bfd: line 76: : command not found /usr/local/bfd/conf.bfd: line 88: : command not found The email is being sent from:
Now i know this isnt r-fx networks support but none of there support options seem to work so i figured id post here considering the amount of users that are likely to be using bfd (or you should be)
