Page 1 of 1

Runs but wont connect

Posted: Fri Feb 17, 2017 9:41 pm
by ricktee76
Client can't connect on port 6667, i have checked via 'netstat' and the port is open and listening.

Code: Select all

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:6900            0.0.0.0:*               LISTEN      27520/unrealircd
tcp        0      0 0.0.0.0:6697            0.0.0.0:*               LISTEN      27520/unrealircd
tcp        0      0 0.0.0.0:6667            0.0.0.0:*               LISTEN      27520/unrealircd
tcp6       0      0 :::6900                 :::*                    LISTEN      27520/unrealircd
tcp6       0      0 :::6697                 :::*                    LISTEN      27520/unrealircd
tcp6       0      0 :::6667                 :::*                    LISTEN      27520/unrealircd
 
In my unrealircd.conf i have :

Code: Select all

/* Standard IRC port 6667 */
listen {
        ip *;
        port 6667;
};
I have also tried 127.0.0.1 and my IP.
and with the clientsonly option but nothing.
I'm currently running ubuntu 14.04 any ideas or suggestions?

Re: Runs but wont connect

Posted: Sat Feb 18, 2017 4:49 am
by rcschaff
Firewall?

Your Netstat does no good if we don't have more information. Is you IP Public, or on a private lan. Are you behind a NAT Router.

try telnet 127.0.0.1:6667 and see what comes up.

Also try running unreal with -nofork to see if anything pops up as you connect.

Re: Runs but wont connect

Posted: Sat Feb 18, 2017 10:39 am
by ricktee76
thanks rcschaff i will give both of those ideas a try and update.

Re: Runs but wont connect

Posted: Sat Feb 18, 2017 10:45 am
by ricktee76
The IP is public, firewall is disabled.

Running with -nofork :

Code: Select all

  using PCRE2 10.22 2016-07-29
  using TRE 0.8.0 (BSD)
  using OpenSSL 1.0.1f 6 Jan 2014

Loading IRCd configuration..
Configuration loaded without any problems.
Initializing SSL..
Dynamic configuration initialized.. booting IRCd.
UnrealIRCd is now listening on the following addresses/ports:
IPv4: *:6900(SSL), *:6697(SSL), *:6667
IPv6: *:6900(SSL), *:6697(SSL), *:6667
UnrealIRCd started.
This is the error the telnet command is giving:

Code: Select all

could not resolve 127.0.0.1:6667/telnet: Name or service not known

Re: Runs but wont connect

Posted: Sat Feb 18, 2017 3:06 pm
by rcschaff
Is this your computer at home, or through a hosting company?

Re: Runs but wont connect

Posted: Sat Feb 18, 2017 9:28 pm
by ricktee76
its on a hosted server, I have full access so i'll be able to make any necessary changes.

Re: Runs but wont connect

Posted: Sat Feb 18, 2017 9:36 pm
by rcschaff
It it's on a hosted server, you should have been given an IP that you need to bind to. On a hosted Enviroment, you should NEVER bind to *.

Re: Runs but wont connect

Posted: Sun Feb 19, 2017 12:49 pm
by Syzop
See this faq entry: FAQ: Unable to connect to IRC server (VPS/shell)
From the post above I gather you followed step 1, 2 and 3.
Did you check step 4? The firewall. It's very likely to be the problem.

As for your telnet error, that is just because you need to 'telnet 127.0.0.1 6667' and not 'telnet 127.0.0.1:6667'.
I suspect telnet will connect fine, but it's just the firewall.
It it's on a hosted server, you should have been given an IP that you need to bind to. On a hosted Enviroment, you should NEVER bind to *.
This is true if it's a shared shell with other users on it. It's not accurate for a VPS or "root server", which I suspect he is using.

Re: Runs but wont connect

Posted: Sun Feb 19, 2017 12:52 pm
by Syzop
See this faq entry: FAQ: Unable to connect to IRC server (VPS/shell)
From the post above I gather you followed step 1, 2 and 3.
Did you check step 4? The firewall. To quote the FAQ:
Check the firewall

If you cannot connect by IP then you need to check the firewall of the server. Consult the documentation for your Linux distribution or your non-Linux OS.

On some VPS providers like Amazon, you need to configure the firewall in your admin panel as well (these are called Security groups on Amazon EC2).
It's very likely to be the problem. Ubuntu often ships with 'ufw'.

As for your telnet error..
could not resolve 127.0.0.1:6667/telnet: Name or service not known
..that is just because you need to 'telnet 127.0.0.1 6667' and not 'telnet 127.0.0.1:6667'.

I suspect telnet to 127.0.0.1 (with the correct syntax) will connect fine. The firewall is just blocking external connections.
It it's on a hosted server, you should have been given an IP that you need to bind to. On a hosted Enviroment, you should NEVER bind to *.
This is true if it's a shared shell with other users on it. It's not accurate for a VPS or "root server", which I suspect he is using.