WHM Changed IP Address, Now Points To Root Of Server -->
May 30, 2007
I'm trying to setup a new SSL host on my server. I changed the IP address in the WHM, and even though the httpd.conf file shows the proper path to the site's directory, when i type in the domain I get the cpanel default page at the apache root directory.
I got up today, went to check my emails and received invalid passwords on all my email accounts. I then went to check in the CPanels and get the same error when I try to login.
Then I try the root and same thing!
BUT all my linked FTP accounts work and the sites are online and working. One is giving a 500 error (cgi program) but besides that, they are all online w/ no changes.
My "host want to do a OS reinstall and let me try and restore my sites from a slave drive. I think thats stupid and shouldnt be needed.
They also automatically say I was hacked...Sure a hacker changed all the cpanel and email passwords but worked it so the linked FTP accounts would work and didnt take any sites offline.
i have a reseller and a client couldn't renew his domain name , so he bought a new domain name and he wants me to move his files (hosted on his old domain name) to his new domain name . how can i do that ?? (his old domain name is hosted on godaddy now)
My client wants to point two domain to the same hosting account. I have already setup the first account for him and it works. How can I make it that when I change the nameserver for the 2nd domain to my server it points to the same hosting account as the 1st domain
We are talking with a datacentre about colocation and im hiring a third party company to manage the servers 'on site' on our behalf.
Im looking for some feedback on the 'colocation agreement' and the 'server management agreement' to make sure were covering everything.
just to be clear, Ive got a server administrator who will access the server virtually so the only points of the agreement will be those tasks that need to be done 'on site'.
the points ive looked at so far are:
colocation agreement > 1u and 2u costs. > Server setup costs. > Power allocation and cost of additional amp's. > Bandwidth overages. > storage space for spares
onsite server management agreement > hardware replacement costs . > Hardware upgrade costs. > status monitoring. > general server management.
1) what else should be covered in the colocation details?
2) what should be included within the 'on site server management' agreement?
3) what should be included under the description 'general server management'.
for example: I think physical reboots should be part of the server management agreement, but how many on average per server per month should be included?
3) should hardware replacement cost be fixed rate per task or hourly, also do you have any suggestions regarding what to expect over a year (nothing exact, just a bit of guidance to help with the budgeting)
Combined these agreements should cover everything that we can not do remotely.
I have read that although chained root ssl certificates can be more difficult to install they are actually more secure since the root certificate cannot be compromised, only the intermediary.
Is this true? It looks like both google and amazon both use chained SGC certs.
I have Plesk 11.5 (service provider mode) on a Windows 2008 server IIS7.Most of my sites are developed in .asp and therefore i use a custom 500-100.asp error page that check s the IP of the visitor then displays either a friendly error, or if its my IP a full error of what has happened (it also emails me the error). This allows me to debug pages easily whilst developing and to keep an eye on anyone trying SQL Injection hacks on my sites (as the error and email also have session variables and IP address).I dont have root access to the server as it is a Webfusion dedicated server.I have following the Plesk documentation -
1) Switch on custom errors for the subscription 2) Look in virtual directories and navigate to error documents 3) Find the error in question (500:100) and change it to point at either a file or URL
FILE - I had the data centre add in the 500-100.asp error page in to the virtual template so that my page is available in the list of virtual files - this didn't work but that maybe because its not a static page??
URL - when i add the path it says its incorrect, if i add a fully qualified address, it accepts it but it doesn't work.give me a specific example of the URL that can be entered relative to the root as the format in the documentation isn't accepted. The last step is to restart IIS which is also an issue as i cant seem to do this from the Plesk panel..It is as if it isn't catching the 500:100 error, and only catching the general 500 error??
I updated my name servers to reflect my new web host two days ago. The name servers have updated, but the site is still pointing to the old host!
I emailed my host about this and they told me to email my registrar. The host says the domain is registered with the new name servers but these name servers are registered with IPs outside of their network. I'm confused and have never had this problem before when changing DNS.
direct root logon to a server is disabled; using another login, obviously. However, I need to be able to SFTP files from my computer to a directory on the server using said login - yet it does not have correct permissions, evidently, and therefore can't even see the directory I need to be able to SFTP files to.
Tried CHOWNing the directory with that usename, giving it 777 permissions, etc.
I'll try to make this long story short, but this morning I logged into one of my servers and it showed a read-only filesystem, which I thought my server guys could fix easily. So I put in a ticket. 6 hours later, they tell me that they think the OS is corrupted and I need a new install. They give me KVM over IP so I can go in and 'do' things. I tried to log in as root and it wouldn't let me, so they finally booted in single mode and I can get in and such. When I try to su - root, it tells me that user root can't be found. I also tried to ftp into and out of the server with no luck. I really need this box back up. If not, I need to get all the accounts saved off so that I can build a new box. Everything is there, so I don't want to give up yet.
We would like to offer root servers to customers, but we worry that they change the IP address to another IP address in our network and make troubles like this. I think, if a customer takes the same IP like our gateway router, our whole network is not reachable anymore. How can I avoid this?
I am actually very inexpirience in server management. I have a small - I believe - problem. I need to get config file onto my computer from my root server. I can access it through terminal, but it is not very confortable. The config file is on root server.
the file is located at //etc/xxx.conf
Do I need to use web browser to do it? If so how?
Or is there a way that I log to my root server through ssh and transfer onto my computer?
creating a basic redirect. What I need is to redirect the root of my server 173.x.x.x to a file called test.php in the root of my folder.example: when I go to http://173.x.x.x I get redirected to http://173.x.x.x/test.php..
My customer has an external facing Apache server that is acting as a reverse proxy to two internal applications. They have:
- external addresses for each app which resolve to different ip addresses, so app1.their_domain.com and app2.their_domain.com resolve to 77.3.170.10 and 77.3.170.11 respectively. - the Apache server has two network interfaces with ip addresses 192.168.10.10 and 192.168.10.11 - the external ip addresses resolve to the above internal addresses - the firewall between the Apache server and the internal app servers is configured to allow traffic from 192.168.10.10 to reach app_server1, and traffic from 192.168.10.11 to reach app_server2, both using port 7777.
I have configured a virtual host in httpd.conf for each ip, i.e.
This works fine in that the external address are being routed to the correct application, however the firewall is blocking requests to the second app as it appears the requests are coming from the Apache servers 'primary' ip address 192.168.10.10 instead of 192.168.10.11.
Is it possible to send requests using the ip address from the relevant VirtualHost?
My server hosted with 1and1.co.uk (and therefore in Germany) has been down since 6PM UK time (20 hours ago) - support is just excruciatingly bad - the structure they have set up to make sure the actual datacentre people aren't customer facing is atrocious... you can't speak to anyone who knows anything, it's so frustrating.
I'm writing this to ask if anyone else has a root server in Germany as the latest fob off is that a router CPU has gone down knocking all those root servers offline. I'm surprised to not have seen any other threads from disgruntled customers if that were the case. They even added the router is in Canada... which begs the question - why would that knock out my German server??
My server isn't even accessible by the serial console and the reboot/recovery system isn't restoring it - they swear it's network related, but surely I'd be able to get in via the serial console?
This is winding me up good and proper, I can't concentrate on any other work and I just find myself trying to find other ways of getting any kind of real information out of 1and1 given their complete lacklustre attitude to coming forward with any themselves. 1 hour of downtime I can put up with, 20 hours without a hint of belivable feedback is just unacceptable...
I've just signed up for my first VPS with CMBHosting and the person in charge, Chetan Bakhru, seems like a genuinely nice, friendly and helpful person. In other words this new service look promising at the moment.
However ...
When I signed up I selected his CentOS/LXAdmin plan because I figured that with a pre-installed control panel like LXAdmin I could avoid as much ssh as possible and simply get "up and running" more quickly. Plus I have some experience managing my own CentOS development machine, and I know that a special software package I plan to install runs on CentOS "out of the box" -- so I was expecting good things from this new VPS.
But when my account was created LXAdmin did NOT create an FTP admin account for me with root access to my VPS!
Instead it created an account that drops me into web server's document root folder, and this is far too limiting for me. I really need FTP root server access -- and I'm surprised that LXAdmin did not provide this access by default.
Not only that, but it appears that I cannot create a new FTP account that has any deeper access than the existing admin account!
Does anyone with LXAdmin experience know if this is the way LXAdmin normally works by default? Or is this perhaps a special configuration created by my new VPS host?
on one my root server runs a DDOS attack, apparently from a Botnet, however all have the same Referer. Who can give me Tipps, how I can prevent the attacks? Preferably evenly stop over the Referer?
i can not login to my decated server by using root. the password is not correct.. becasue i did something wrong with my server. i used chmod 777 -R /public_hmtl and chown to modify my server. and i can not login anymore, LT asked me to reload my server, do i need to reload it?