I just got a new box. How can I log into it without the domain?

Can I do it with the IP and a port number?

I tried http://serverIP/admin

https://ip:8443

Thankyou!

Is there any way to allow client ftp access before the name servers go into effect. Can a client log into the server using the IP?

yes, they can ftp to the ip# that thier site is on.

Okay, I kinda figured that would be the case. I must not have it set up correctly yet.

*tinkers some more*

Thanx for the response.

Can anyone tell me why I can't make a FTP connection to my server using my IP. I'm using WS_FTP.

Can you provide us with the settings you are using? (skipping the password of course). Also do you have any firewalls in place? Is it all accounts..or just one? etc.....

well..first...check to make sure ftp is running...

ssh in to your box as admin, then su - (to root)...netstat -anp | grep :21 ...if you find proftpd listening on port21..that means your ftp is running...if not...start with getting your ftp online.

your ftp username is setup under the hosting tab, it is NOT the client login. So after you add your site under hosting, physical hosting, you have to select a ftp username/password combo. Try those.

Yes, I have a FTP Login and password set in Hosting.

Then if proftpd is running...and you don't have a firewall blocking your connection....use that username/password...it should work...

if it doesn't...suggest checking your /var/log/secure to see if you have actually reached the server or not...

if you are reaching the server, just not connecting...please provide the error messages that your server is giving you...

heh

I went to [Restart Services] and I can't get Apache web server to start. "Unable to exec Start/Stop utility"

ok..I thought we were working on your ftp...not your apache....lol

anyway...sounds like you have some major issues with your plesk..I might suggest re-applying the latest plesk path (6.0.1).

figs.

*sigh*

The files in /usr/local/psa/admin/bin are not ok. You can force the reinstall of psa rpm.

I think I might have been able to handle what would have been a major learning experience for me, if this stuff was working right. Now I gotta deal with "issues". LOL.

*toils away in frustration on a friday night*

hehe

Just simply run the plesk6.0.1 patch again...but instead of using rpm -Uvh ...use rpm -Uvh --force for the rpms....that will force the rpms to reinstall and fix the files back to how they should be.

how?

Follow the release notes at plesk.com ....just use rpm -Uvh --force ...instead of rpm -Uvh ...

http://download1.plesk.com/psa6.0.1/psa-6....723.13.i586.txt

okay, I'm not nearly as dumb as I seem (I swear!).

I haven't found them here, so can someone please please please give me some links to resources for complete newbs on things like SSH and "loging into the 'root'".

Thankyou.






And stop laughing. I can hear you! hehe

goto the link I gave you in the above post:
http://download1.plesk.com/psa6.0.1/psa-6....723.13.i586.txt

you have to register at plesk.com to get there...but really..they wont' charge you to do so...(and you are supposed to be registered to get the patches anyway.)

Scroll down to this section:

Plesk RPM Upgrade Procedure
============================

and do what it says...just don't use rpm -Uvh ..but instead use rpm -Uvh --force ...since you already have the patch on your server ..(unless you don't have plesk6.0.1 ..in which case...you can use the rpm -UVh).

IE: this command:
rpm -Uhv courier-imap-1.7.3-31psa.rh9.i586.rpm
psa-6.0.1-rh9.build030723.13.i586.rpm
psa-courier-imap-add-6.0.1-rh9.build030723.13.i586.rpm
psa-locale-6.0.1-rh9.build030723.13.noarch.rpm
psa-logrotate-3.6.6-2.rh9.i586.rpm
psa-proftpd-1.2.7rel-rh9.build030723.13.i586.rpm
psa-proftpd-xinetd-1.2.7rel-rh9.build030723.13.i586.rpm
psa-qmail-1.03-rh9.build030723.13.i586.rpm
becomes this command:
rpm -Uhv --force courier-imap-1.7.3-31psa.rh9.i586.rpm
psa-6.0.1-rh9.build030723.13.i586.rpm
psa-courier-imap-add-6.0.1-rh9.build030723.13.i586.rpm
psa-locale-6.0.1-rh9.build030723.13.noarch.rpm
psa-logrotate-3.6.6-2.rh9.i586.rpm
psa-proftpd-1.2.7rel-rh9.build030723.13.i586.rpm
psa-proftpd-xinetd-1.2.7rel-rh9.build030723.13.i586.rpm
psa-qmail-1.03-rh9.build030723.13.i586.rpm

Hope that helps (and I am not laughing....I just don't have time to format a how-to tonight)

error: open of courier-imap-1.7.3-31psa.rh9.i586.rpm failed: No such file or directory

:confused:

I hate this. Rackshack sells me a box with crap that doesn't even work and I gotta spend two days learning stuff out of my grasp to fix what I haven't even had a chance to break yet!

because I got error: open of courier-imap-1.7.3-31psa.rh9.i586.rpm failed: No such file or directory
, now I can't complete this and I'm stuck now even with Plesk not running.

couldn't they atleast have given me somethingthat ran right in the first place.

This was the biggest mistake ever.

Zenhex,

Since it's a brand new server with nothing on it yet why not put int a trouble ticket with RS? If the install was bad they can always re-image things for you. Bad installs happen from time to time, though not often.

That being said, you can in fact fix all of these things by yourself as pointed out in the previous posts. However I think that if you're just starting out you'd be better off having everything working correctly from the beginning. It might prevent further problems down the road.

As to what to do and how to do it... There used to be a pretty good thread on the forums here outlining the basics. But it seems to have disappeared with one of the forum updates. The info is all here, just that it's not all in one place anymore.

Here's my personal list of the bare minimums (which I'm sure you can search for and find tutorials):

1.) Change your "root" password (by default it's the same as the admin password.
2.) Upgrade your SSH is necessary.
3.) Get yourself an SSH client you can use to connect to the server via command line (I use Tera Term SSH, but there are several options which are equally good)
4.) Once you've verified that SSH is working, disable Telnet
5.) Register at Plesk.com so that you can get upgrades and other goodies.
6.) Set up a username in the Plesk forum (it's under the Support link at Plesk.com)
7.) Make sure you're Plesk is up to date (Currently 6.01 though that is constantly changing, so check the Plesk site.)
8.) Install a firewall on your server, being careful that you leave port 8443 available. (I use KISS Firewall which has a tutorial on these forums.)
9.) Install chrootkit
10.) Make sure your mailserver is not sitting there with an open relay...the servers used to come with that as a default setting though I think that's changed. Basically go to your Plesk admin panel Servers > Mail. Then whitelist 127.0.0.1/32, click the "Authorization Required" button and choose "POP3" (only... do not check both POP3 and SMTP. One or the other.)
11.) Change your hostname (Nighthawk has released a script which will do this for you if memory serves.)

That's a very bare bones list of things you should do straight off the bat. That'll help to secure your server and get you to a good starting place. I'm sure others will have more suggestions to offer.

Or, if you don't feel like making sure your server is secure and completely up to date, you may want to contract with someone here to do that for you. I'm pretty sure Nighthawk offers this type of service for a reasonable fee and most likely 4PSA too.

There are some very skilled Plesk Administrators who hang out on these forums, the two mentioned above and atomicturtle who was one of the Plesk founders leap to mind immediately. So your learning curve will not be nearly as steep as it could be.

Read everything you can here and at Plesk.com, and keep notes of the changes you make to your server as you make them. Those notes will be invaluable the next time around.

Squire

Just get the tar.gz from plesk.com, untar it...cd to the rpm directory and run just a simple rpm -Uvh --force *

That will just run rpm -Uvh --force on every rpm in the directory...that will take care of any version changes etc...