• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Linux Not being able to connect to server

Glecko

Advanced OT User
Joined
Aug 21, 2007
Messages
1,015
Reaction score
240
Location
Spain
Ok, I have have tried like everything by now and I still can't manage to connect to my server. I use Ubuntu (newest version) and followed this guide to setup my server:
http://otland.net/f479/ubuntu-nothi...gotten-server-modernaac-mysql-lighttpd-89001/

I forwarded my ports (7171,7172 and 80) both on my router, on the iptables of ubuntu and on the firewall. I am still not able to connect to the server.
For some time, I was able to see my website from another computer connected to the same router, but other people were not able to see it. Whenever I check at vapus if I can host, it says all 3 ports are blocked. I reseted my computer and the router several times, and I'm sure I have no-ip and all that installed on my dedicated server.

I use the newest rev (5680, client 9.54), and every time I try to log in, instead of getting an error like (could not connect to server) the loading screen just disapears. When I try the same with another random direction it tells me the error, which makes me supose the client finds something.
I got to say, on my Windows PC it works perfectly.

Any ideas of what's going wrong? Thanks :)

EDIT: I also checked with the comand:
sudo netstat -anltp|grep :pORT
And according to it, TFS is actually listening to 7171 and 7172, and apache2 is listening to 80.
 
Last edited:
I don't know what exactly you mean...
This is what shows up with the iptables -L -n

Code:
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:7171 
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:7171 
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:7172 
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:7172 
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:80 
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:80
 
sometimes i encounter problems that are server-specific only problems, if your unsure of this try compiling another server (from subversions) and connecting to it, if it works, you know everything is fine (except the server)
 
I doubt it is server specific, since the same happens with my website (port 80). I cannot figure out what exactly could be causing trouble.
 
you cant access any ports? im not sure if all linux iptables say 0.0.0.0 but thats not set in your router port forwarding is it? as should be forwarded to remote ip listeded in (sudo) ifconfig
 
you cant access any ports? im not sure if all linux iptables say 0.0.0.0 but thats not set in your router port forwarding is it? as should be forwarded to remote ip listeded in (sudo) ifconfig

My ports are forwarded in my router, yeah (in my Router, I went to NAT->Sua Only and added ports 7171,7172 and 80 for the local IP of my server)
I'm sorry if this is not what you meant, I didn't exactly understand what you mean xD
 
I'm using one of the newest revs (5680, version 9.54) and no, i can't reach the login screen. After I try to log in, the "Loading your character list" just disapears (doesnt give any errors, just disapears)
 
You've done something wrong and that's it.
It's normal that people are not answering when they have no knowledge to answer you.
Which means, they don't know or you haven't told them enough.

Ok, enough of moralizing.
I'll tell you what i would do to debug this problem but don't expect me to sit and look on your logs, then tell you to do.
You can learn from the net if you know what to learn.

Firstly, i would recommend you to check if this services are listening on public interfaces (for example, not on loopback one).

Secondly, i wouldn't waste my time on guessing.
Why don't you use some kind of sniffer like tcpdump or wireshark (gui so probably easier for you) and check what's going on with information.
1) Make sure you got machine in external network to make connection requests (like a friend, or shell account, or bot, your imagination).
2) Listen on external interface and see if you're getting packets from the source)
3) Listen on internal interface if packets are rewritten by your NAT
4) Listen on target server if it's getting his packets routed correctly.
5) Do the same for other way back (is the response going out, is it reaching your gateway, is it rewritten to correct target, and finally check if it's not filtered on WAN interface).
Have fun, because playing with computers is fun
 
I tried to be as informative as I could in the main post :p

About your points, as I already stated before:

1 and 2)No PC outside of my LAN are able to see the website/connect to the server (no packets at all). I don't know exactly how to check if the "connection request" reaches the server,
3) I'm not exactly sure of what you mean, but I checked with multiple programs (like firebind), at it actually tells me that my ports are forwarded in my router,
4 and 5) My server has no programms installed but Teamviewer, Apache and No-ip. None of them should be blocking port 80. I forwarded the ports on both iptables and the UFW, and when I check, the tfs program and apache are actually Listening to the ports they need.

My question is, if my router doesn't block the packages, and the ports on the server are actually being listened by the programs, what else could be blocking the packages?
(I disagree with the part that playing with computers is fun, I'm sitting hours and hours breaking my head over this and I don't see the fun part about it xD)
 
That's because you're really doing it wrong.
It's not about trying different things and methods but about understanding.

As i told you, if you really want to fix it just download some packet sniffer, learn how it works (wireshark is really easy), and trace the packet as far as you can.
Then, you'll see where problem lays, and you can ask more concrete question.
 
Teamviewer or Apache could be using port 80, but if you said that the ports are still blocked there's your problem. Make sure they are open (recommended website to do so is: Open Port Check Tool) if at anything else I say end all unnecisarry programs that are running and try again. If not look up in google, I bet you'd find something in there related to Linux and port forwarding. As for ports 7171/7172 you must have done it wrong since nothing is associated with those ports.
 
Back
Top