Can someone show me a tutorial on exactly how to point a domain name to my VPS? Not just a simple masked forwarding, I want it to actually point to my VPS so that basically [url]is the same as [url]
Does anyone know if the VPS tutorial thread (the one that told you exactly how to do everything) was distributed anywhere else apart from WHT? Because of the recent site problems, that thread was one of the lost ones.
How do I add a domain name to my vps account? Where is the vps detail tutorial? I brought a vps plan so I could learn at least 100 things about managing my own vps through hypervm and webmin.
If you have a thing or two to teach about managing it, please reply with how to do so and so.
I am at school now. I will get home later and then I can get back to my hobby of teaching myself how to manage a vps. I have a lot of time on my hand to learn how to manage a vps.
Ive looked for a long time now trying to find the perfect tutorial to migrate my clients (on cPanel) to my VPS without downtime. Every tutorial i found doesnt tell you how to make it so you dont have any downtime at all.
I know you can point the DNS from the old server to the new server by editing it through cpanel but i have more than 100 clients and it would be DAMN annoying to edit every single one of them one by one. Is there a faster way? Anyone have a tutorial that i can follow?
today i changed the password for the admin panel for a customer (username eg. mylogin). 10 minutes later he called me and said that he cannot get into his emailaccount anymore. Checked the password and saw that the emailpassword for his emailaddress (eg. mylogin@mydomain.com) is now the same from the admin panel login. So i changed the emailpassword and checked the admin panel login - it now has the emailpassword. What a mess.. I'm running Plesk Panel 11.5.30 MU47.
I'd like to have the ability to offer hosting in two geographical and network diverse locations for both Apache and MySQL. Two entirely different instances, with different everything. ie: high avail to the max. Obviously the MySQL part is harder due to the dynamic nature.
I can appreciate the technical aspects of the question - such as data needing to replicate to 2 locations, dealing with static versus dynamic data, etc. In short, there's a few ways this could be done.
I've not been able to find a guide in my Google searches, but I'm sure this is something that has been setup before.
If you're someone with experience in having had set this up, perhaps it would be easiest if we just speak directly and work something out, either via payment or giving you a dedicated server on my network. My AIM name is IGSOBEHELPER.
Please note that I am hoping to start a technical discussion about this, hence I am not posting the message in the employment section. I hope this is not off topic because of this.
Is there a Windows GUI software for remote Admining servers that run on Red Hat Linux?
FYI: Currently I use Putty for remotely managing our servers.
So if you can recommend a GUI like Windows desktop software for remotely Admining servers running Red Hat Enterprise, I would very much appreciate that.
FYI: we have like 10 dedicated severs, so a desktop GUI that would allow one to monitor/manage multiple servers would be best. But if the GUI that you think is best can only remotely connect/manage one server at a time, requiring disconnecting to connect to the other server to Admin it, that is fine.
Also, I would love to hear what you think is the best book, best tutorial and reference guide for remotely Admining servers running RHEL? I am not looking for one of those books that are 1000 pages, but something that is a few 100 pages and can be read in 1 month assuming a few hours per day of reading.
write a tutorial how to set up a server without a control panel. A step by step guide how to set up the dns, add doamins. create accounts, create ftp users, create databases, create db
I am trying to create an ssh key pair to allow rsync without passwrods between two debian boxes.
I have Main server which I want to push data to Backup server
I have followed the tutorial at [url]but this does not work when I ssh or rsync eaither from main server to backup server or ther other way it still requires password.
Im starting to use private/pub keys for ssh access, so far i can access the server via ssh w the key (ive disabled pass access in sshd_conf) but when i want to copy accounts from this server (the one w ssh key) trough the whm interface to another who hasnt key it doesnt work... am i missing something?
i have my own centos server . i want to let some of my friends to login to my box using ssh keys , so i set an authorized_keys file to have their pubic_keys.
Now , my question is how can i limit the commands they can execute?
i mean let them just only "rsync" their files from their boxes to mine , without any ability to execute any other commands or even loging to my box!
I'm having a problem with SSH keys (they don't work out of the box correct with cPanel) I bilieve the error is in my sshd_conf, but if someone could assist me with what settings that should be uncommented that would be helpful.
Anyways, just some history of what I did so far:
Generated a passphraseless key within Server(A1). Took the public key (not the private, left the privat on the server itself) and transferred it to a file authorized_keys on Server(B2).
Chmod that file to 600. Then ran the following command:
First I still get asked for a passphrase (which is wierd since it's suppose to be passphraseless), then when I just press enter (to signify that there is no passphrase), I get the following error:
removing my ssh key from the server. I want to be able to login with just a password. I have to change one of my servers and I cannot do it with the keys enabled.
I had previously had this working. However, I changed the second VPS and now I can't remember how I set it up.
I will call it SourceVPS and BackupVPS.
I am trying to setup SSH keys to allow me to SCP backups from the sourceVPS to the backupVPS.
The SCP command I am trying to run on the SourceVPS is:
Code: scp -i /root/.ssh/VPS_root_access_key -pr /root/movetest.txt root@server.BackupVPS.com:/backup/ Previously, I had the SSH keys between the SourceVPS and BackupVPS so the above command would move a file from one to the other (instead of movetest.txt, that is normally the name of the backup file being moved).
Can someone walk me through the steps for setting up the SSH keys? I am on Cpanel/WHM and Centos 4.6
when populating and attempting to write keys to authorized_keys I'm receiving the following error:
Quote:
Could not create directory '/home/Administrator/.ssh'
Long version:
I've been grinding my wheels with this for a long time now. Basically I'm attempting to get rsync set up to backup some data directories on my Windows 2k3 Server through a batch file with task scheduler to bqbackup. I've been back and forth with both Scott and Rsync.net's tech support about this issue - both of which have been great... but essentially keep hitting the same impasse with Scott appearing to have hung his hat stating he's not familiar enough with windows and rysnc.net telling me to wait for their GUI client that should be launching "soon." In the meantime I'm just running the backup manually until I can get this key issue figured out.
Here's what's going on: I've been mainly using BQ's Guide and Rsync's Guide to try and accomplish this.
After executing ssh-keygen -t rsa -N ''
I receive the following message:
Quote:
Generating public/private rsa key pair.
Enter file in which to save the key (/home/Administrator/.ssh/id_rsa):
If I accept the default value it gives me I receive this error:
Quote:
Could not create directory '/home/Administrator/.ssh'.
Open /home/Administrator/.ssh/id_rsa failed: Not a directory.
Saving the key failed: /home/Administrator/.ssh/id_rsa.
Now my thoughts were this was occurring because my %homepath% is actually:
Quote:
c:documents and settingsadministrator.DOMAIN
(DOMAIN replacing actual text)
I'm able to change the default path location and create the RSA file elsewhere using the cygdrive format... so when prompted for the path to save I instead input:
Quote:
/cydrive/c/docume~1/administrator.DOMAIN/
and am able to create the RSA file... so mission accomplished... so far, I believe I'm past this, the snafu is now occurring on writing these keys to the authorized_keys file on BQBackup...
Quote:
C:Program FilescwRsyncin>rsync -av "/cydrive/c/documents and settings/administrator.DOMAIN/.ssh/id_rsa.pub" <login>@<host>:.ssh/authorized_keys Could not create directory '/home/Administrator/.ssh'. The authenticity of host '<host> (<ip>)' can't be established. RSA key fingerprint is 18:02:d9:95:06:a9:70:74:86:b7:76:41:f6:71:a0:a4.
(<login>@<host> replacing actual login & host... it's definitely connecting)
That pesky '/home/Administrator/.ssh' pops up again. I'm not sure if that's what's causing the issue or not. I'm not even sure why the %homepath% for my administrator account on the server is set to administrator.DOMAIN, but AFAIK I can't log in to a local account on a Win2k3S box, correct?
Now, you'll notice that the command I issued to upload the keys I got from the RSync.net instructions. BQ's instructions for step 3 are pretty foreign to me.
I've gone further than this and attempted other things such as SSH'ing into my BQ server using putty and attempting to write the keys that way with no luck. I can't fully remember the errors I encountered doing so, though.
in order to secure my server against instrusion, i disabled ssh root login and created a user for myself. however in order to access the user i need to enable SSH Password authentication
I dont enable password authentication all the time and i keep it disabled unless i need to do something via ssh.
Now my question will be, is there a way to keep the user i created and keep the root login disabled and password authentication disabled but use ssh keys for the user i created?
I was informed that if i opt to login to ssh via the user i created, the only way to do that is to enable password authentication as it cannot work with ssh keys. is this true?
I really hope someone can help me how to use the user i created together with ssh keys so i dont have to enable password authentication when loggin to ssh
Currently I have a server that has direct root SSH access disabled (have to login as regular user then su to root), but I am currently working on setting up authentication via SSH keys, but I can't seem to get it working with direct root SSH access disabled? Is this normal, and if so is there anyway to work around it?
Basically I'd like to be able to authenticate both ways; both with SSH keys or by logging in as a regular user and su to root.
