During development of our rails application, I went through the initial try/error phase. But it seems that there is always space for new problems.
I have been testing the HTTPS, so I run the WEBrick servers on standard ports 80 and 443 and the WEBrick server went down immediatelly with a strange error:
[2006-07-12 00:01:14] INFO WEBrick 1.3.1
[2006-07-12 00:01:14] INFO ruby 1.8.2 (2004-12-25) [i386-mswin32]
[2006-07-12 00:01:14] WARN TCPServer Error: Only one usage of each address(protocol, network address, port) of socket is allowed – bind(2) ((sorry for the transation))
C:/Win32app/ruby/lib/ruby/1.8/webrick/utils.rb:62:in `initialize': NOnly one usage of each address(protocol, network address, port) of socket is allowed – bind(2) (Errno::EADDRINUSE)
from C:/Win32app/ruby/lib/ruby/1.8/webrick/utils.rb:62:in `new'
from C:/Win32app/ruby/lib/ruby/1.8/webrick/utils.rb:62:in `create_listeners'
from C:/Win32app/ruby/lib/ruby/1.8/webrick/utils.rb:59:in `each'
from C:/Win32app/ruby/lib/ruby/1.8/webrick/utils.rb:59:in `create_listeners'
from C:/Win32app/ruby/lib/ruby/1.8/webrick/ssl.rb:87:in `listen'
from C:/Win32app/ruby/lib/ruby/1.8/webrick/server.rb:63:in `initialize'
from C:/Win32app/ruby/lib/ruby/1.8/webrick/httpserver.rb:24:in `initialize'
from script/server.secure:65:in `new'
from script/server.secure:65:in `dispatch'
from script/server.secure:82
I am pretty sure I didn’t runn any web server on my machine. Fortunately I have Unix tools on my Windows machine and netstat -a -b gave me a good hint.
Skype occupies these standard ports! So, if you need to test your rails application on a standard port, just shut down Skype. Do not forget to turn Skype on afterwards. It is a great tool.