Running another process on port 80

Running another process on port 80

Posted by: rhunter008
Posted on: 2007-08-21 09:07:00

Hi,

I'd like to run a web process on port 80 so that it can be my website. In particular, I am using the Ruby Camping framework. I have it working on other ports, but I really want it to be running on my domain at 80, not on some random port.

When I try to run the process on 80, I get Permission denied - bind(2) (Errno::EACCES)

Is there anyway to do this? Perhaps by "stopping" the webserver running now?

Thanks,
Rob

Re: Running another process on port 80

Posted by: Lensman
Posted on: 2007-08-21 09:33:00

Are you on a dedicated or private server?

Re: Running another process on port 80

Posted by: rhunter008
Posted on: 2007-08-21 09:44:00

Private ... I'm on a cheapo plan.

thanks,
Rob

Re: Running another process on port 80

Posted by: Lensman
Posted on: 2007-08-21 09:54:00

I think you'll have to contact support to get them to not startup apache on your server.

Re: Running another process on port 80

Posted by: rhunter008
Posted on: 2007-08-21 10:02:00

Thanks, I submitted a request. I'll report back with how it goes.

--rob

Re: Running another process on port 80

Posted by: rhunter008
Posted on: 2007-08-21 15:13:00

Can't be done. DH writes to me,

"Unfortunately your account does not allow running your own apache processes on any port, so I can not turn off the web server as you request. You will have to run your website using our provided apache services.

Furthermore it will not be possibly to run any services on a shared server, if we get notifications that you are running any services we will kill the process and potentially someone from our abuse team may be contacting you to stop."

Re: Running another process on port 80

Posted by: Lensman
Posted on: 2007-08-21 15:49:00

I thought you said you were on a (virtual) private server? Instead, are you on a shared server?

That is, are you using the DreamHost-PS service?

Re: Running another process on port 80

Posted by: sdayman
Posted on: 2007-08-21 15:56:00

If it's a cheapo plan, then it'd be shared. But sometimes I shut my eyes real tight and imagine there's nobody else on my server.

-Scott

Re: Running another process on port 80

Posted by: rhunter008
Posted on: 2007-08-21 15:58:00

Sorry, I read your earlier email as an XOR ... and since I'm definitely not on a "dedicated", I said "private". Anyway, I'm on the "My Crazy Domain Insane" plan ($10/month), which I believe is a shared plan.

Re: Running another process on port 80

Posted by: Lensman
Posted on: 2007-08-21 18:34:00

Ah yes, no worries. Yes, that would be a shared plan, apache runs listening to port 80 and there's no stopping it! :)

I happen to have a L1 plan but have signed up for DreamHost-PS. Your choice of plan is orthogonal to whether you sign up for P.S. - I guess I should call it premium rather than private since it's not literally a VPS. Apologies for the confusion.

Anyway, since you get a dedicated IP and are running in a kernel level virtualized environment, you should be able to run a different process listening to port 80 if you can convince DreamHost to not run apache for you.

Tags: permission deniedtry to runbindrubyframeworkcamping