• 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 I can't login on server with global ip

rudger

Active Member
Joined
Oct 1, 2010
Messages
253
Solutions
1
Reaction score
32
Location
The Netherlands
I'm using latest linux ubuntu and otx2 client 8.6.

When I use 127.0.0.1 on my ipchanger I can login but when I use my global_ip I can't login.

Does anyone know why that is?
This doesn't happen with tfs 1.2.

Code:
   worldId = 0
   ip = "196.211.89.72"
   worldType = "open"
   bindOnlyGlobalAddress = false

No error on console but on tibiaclient when I try to login:
Code:
Error: Network Error.(-1)

Maybe a strange console output:
Code:
WARNING: MYSQL Lost connection, attempting to reconnect...

When I'm trying to run the server with fresh otx2 same error.
It happens on all 0.3/0.4 servers.

All passwords and settings are fine.
 
Last edited:
You might need to setup a static primary network interface.

What does your /etc/network/interfaces file look like?

One of my servers look like this:
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 95.85.51.190
        netmask 255.255.255.0
        gateway 95.85.51.1
        dns-nameservers 8.8.4.4 8.8.8.8 209.244.0.3
Where 95.85.51.190 is my "global ip".
 
@Znote

Unfortunately it didn't work

Code:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 83.13.104.38
        netmask 255.255.255.0
        gateway 192.168.2.251
        dns-nameservers 210.70.63.75 210.70.63.76

Code:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 83.13.104.38
        netmask 255.255.255.0
        gateway 192.168.2.251
        dns-nameservers 4.2.2.1 8.8.8.8

What about resolv.conf

Should it be

Code:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1

or

Code:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 4.2.2.1
nameserver 8.8.8.8
 
Last edited:
You shouldn't need to do anything in resolv.conf, my suspicion is that the server is not running through its appropriate network interface based on this (Error: Network Error.(-1)).
I remember I had the issue before, not quite sure how I solved it. :/

Perhaps since in config.lua you have set "bindOnlyGlobalAddress" to false it is unable to determine or select any network interface.

Try to compile the server with the __DEBUG_NET_DETAIL__ flag/definition. It might give us more to work with.
 
bindOnlyGlobalAddress = true doesn't work either. I will try to compile with the flag.

@Znote

I've done this:

Code:
# Config for 64Bits
#DEBUG_FLAGS="-Ofast -march=core2 -fomit-frame-pointer -DNDEBUG"
OPTIONAL_FLAGS="-D__DEBUG_NET_DETAIL__"

Is that correct?
 
Last edited by a moderator:
It seems to already be in there
Code:
# check if we want a debug build
debugBuild=no
AC_ARG_ENABLE(debug, [  --enable-debug       enable debuging],
   [DEBUG_FLAGS="-D__DEBUG__ -D__DEBUG_MOVESYS__ -D__DEBUG_CHAT__ -D__DEBUG_HOUSES__ -D__DEBUG_LUASCRIPTS__ -D__DEBUG_MAILBOX__ -D__DEBUG_NET__ -D__DEBUG_NET_DETAIL__ -D__DEBUG_RAID__ -D__DEBUG_SCHEDULER__ -D__DEBUG_SPAWN__ -D__SQL_QUERY_DEBUG__ -O0 -g3"]
   debugBuild=yes
)

Compile it with the --enable-debug command.
 
@Znote
I've done this:

Code:
sh ./autogen.sh && ./configure --enable-debug --enable-server-diag --enable-mysql --enable-root-permission && make -j 2

But there is nothing different

Should I try login with 127.0.0.1?

When connecting with 127.0.0.1 I can't logout I can only click exit.
 
Last edited:
Back
Top