IRC (Nginx problem or unix?)

I have installed Webmasters Conference Room CR4 with a fresh install of
Nginx (0.8.34). I do not have much experience running my own IRC channel
and I’m not sure if this even has anything to do with Nginx. But when I
installed it under apache/whm, the chat worked right away with out any
issues. Now when I installed it on a Nginx setup, I get a time out.

The IRC program is set up to run on a subdomain on port 8000.
(chat.example.com:8000). I am currently listening to port 80 for _
servers, do I need to do some sort of passthrough in the nginx.conf
file? specifically for this subdomain? Is this even an ngixn problem?
i.e. am I missing something in the unix side that would prevent me from
making this program work?

Thanks

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,70748,70748#msg-70748

On Sat, Apr 3, 2010 at 00:21, flash [email protected] wrote:

The IRC program is set up to run on a subdomain on port 8000. (chat.example.com:8000). I am currently listening to port 80 for _ servers, do I need to do some sort of passthrough in the nginx.conf file? specifically for this subdomain? Is this even an ngixn problem? i.e. am I missing something in the unix side that would prevent me from making this program work?

Whatever that is, it doesn’t seem to be an IRC server (unless it’s
based on one and it provides a webinterface), not is the documentation
enlightening. If you want :8000 you should listen on :8000, nginx
won’t guess that for you, neither will whichever UNIXâ„¢ flavor you’re
using. Nor will “a timeout” help you get answers.

Check the nginx logs, check the manual for that server (especially its
system requirements), dig around; repost.


() ascii-rubanda kampajno - kontraŭ html-a retpoŝto
/\ ascii ribbon campaign - against html e-mail

http://webmaster.com/cr.htm

it is an IRC server and yes it does provide it’s own interface. (which
is why I don’t think this is an nginx problem, but I’m just trying to
remove all possibilities.

Thanks

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,70748,70994#msg-70994

This turned out to have a simple solution - all I needed to do was to
open the :8000 and :7000 ports in my iptables.

Still learning the ins and outs of command line unix.

Flash

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,70748,71133#msg-71133

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs