PDA

View Full Version : Port 3000 help


trinsic
10-08-2006, 08:33 PM
I'm quite new to this all and learning as I go. I have installed ServerCP and everything went well but when I goto http://<myip>:3000 it comes up with unable to establish a connection.

Is this because port 3000 isn't being listened or maybe even something else? This has been my first error since I started with dedicated servers and ssh etc.

Anyhelp thanks :)

Dub
10-09-2006, 03:04 AM
Hello,

So you go to http://yourip:3000 and it gives you cannot connect? Make sure your using the right IP? Check for any possible firewall blocking ports 3000,3500 (ask DC, quiet often they install one of their own to prevent IRC,etc). Try https://yourip:3500

- Steve

trinsic
10-09-2006, 05:56 AM
IP is correct but 3500 didn't work either. I will check my DC tonight thought for blocked ports.

trinsic
10-09-2006, 06:29 AM
Ahh man still no fix. DC isn't blocking 3000 or 3500. Is there any checks I can do to see if ServerCP may not be working correctly?

trinsic
10-10-2006, 12:05 AM
Ok great got it working. For some reason iptables was not starting.

pilmiph
10-10-2006, 09:33 AM
Maybe you could help me. I just had to replace my NIC. I couldn't configure it in Kuduz (kept rebooting when I tried to assign a static IP) but I was able to configure it in the GUI for CentOS. Now when I try http://localhost:3000 I get the same error that you were getting. Do I need to point DSM to the new IP address somehow? I am new to this as well.

pilmiph
10-10-2006, 10:36 AM
I took a look into the services and the dsm service has the following message in the status box: dsm dead but subsys locked. Any ideas?

Jeremy
10-28-2006, 03:31 AM
Can you give the output of dmesg?

and try /etc/init.d/network restart

and tail -f /var/log/messages

See if there are any errors in there post it here.

If i were you.. Dont install the GUI just the minimal for centos.

On install don't use a firewall, and disable SELinux.