# Error when starting the server

**URL:** <https://www.ruby-forum.com/t/error-when-starting-the-server/137056>\
**Category:** Ruby\
**Created:** [May 8, 2008, 4:48pm UTC](https://www.ruby-forum.com/t/error-when-starting-the-server/137056 "2008-05-08T16:48:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cornelombaard](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e274bd/32.png) [@cornelombaard](https://www.ruby-forum.com/u/cornelombaard)\
**Post date:** [May 8, 2008, 4:48pm UTC](https://www.ruby-forum.com/t/error-when-starting-the-server/137056/1 "2008-05-08T16:48:46Z")

</div>

I get the following when I want to start the rails server:

Server Error: Address already in use - bind(2)  
/usr/lib/ruby/1.8/webrick/utils.rb:73:in `initialize’: Address already  
in use -  
bind(2) (Errno::EADDRINUSE)

---

<div class="post-metadata">

**Author:** ![cornelombaard](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e274bd/32.png) [@cornelombaard](https://www.ruby-forum.com/u/cornelombaard)\
**Post date:** [May 8, 2008, 6:50pm UTC](https://www.ruby-forum.com/t/error-when-starting-the-server/137056/2 "2008-05-08T18:50:46Z")

</div>

Corne Lombaard wrote:

> […] Address already

I’m not familiar with Rails, but it seems you’re trying to start Ruby’s  
web server (Webrick). This server sits listening on port 80 for  
requests. You probably already have some other server listiening on this  
port. E.g. Apache. So make Webrick listen on some other port (E.g. 81).

---

<div class="post-metadata">

**Author:** ![cornelombaard](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/e274bd/32.png) [@cornelombaard](https://www.ruby-forum.com/u/cornelombaard)\
**Post date:** [May 8, 2008, 11:18pm UTC](https://www.ruby-forum.com/t/error-when-starting-the-server/137056/3 "2008-05-08T23:18:45Z")

</div>

Albert S. wrote:

> Corne Lombaard wrote:
> 
> > […] Address already
> 
> I’m not familiar with Rails, but it seems you’re trying to start Ruby’s  
> web server (Webrick). This server sits listening on port 80 for  
> requests. You probably already have some other server listiening on this  
> port. E.g. Apache. So make Webrick listen on some other port (E.g. 81).

The default webrick server port is 5432 or 3000 from what I remember.  
Shouldn’t conflict with apache unless you configure it differently. You  
might also check if its a DHCP conflict, IE: go around your house and  
check each ip via:  
Linux - ifconfig  
Windows - ipconfig

Regards,

- Mac