Server is currently offline!

[malice987]

Okay here is my problem,
Ive started up my OT server, i just finished the setting up the server and in "otserv" my server keeps saying that it is currently offline.

The game is working LAN however i haven't had anyone check it though its WAN, would someone please check this for me if not try and resolve my problem.

The IP is "goliathus.no-ip.org"

Thank you for your time

 

[Peroxide]

try 127.0.0.1

 

[malice987]

I mean when i upload the server to otservlist.org - Open Tibia Server it says that the server is offline, can you try it..
8.6 | goliathus.no-ip.org

 

[Eternal Life]

if it says that, then the server is off... you can try cheking at canyouseeme.org or .com not sure and check if your port is open if not then is close so that means you need to portforward

 

[malice987]

It says port 7172 to closed, but i opened it?

 

[Peroxide]

when you added the server to otserv list was the otserver online at the time?

 

[malice987]

Yes it was, it got added then said it was offline, i went too canyouseeme.org and it says that port 7172 is closed ><
I have opened it the same way i opened port 7171..

 

[malice987]

Success: I can see your service on 125.160.123.326 on port (7171)
Your ISP is not blocking port 7171

Error: I could not see your service on 125.160.123.326 on port (7172)
Reason: Connection timed out

7171 works, 7172 does not

 

[Eternal Life]

hmmm did you do the exact same thing for 7172?, make sure

 

[malice987]

lollo.png picture by smite12-34 - Photobucket

 

[Tekno92]

Do you own a router? http://whatismyip.org/ rewrite the ip address from this site. Press 'start -> launch -> cmd -> ipconfig -> Look at the line saying Address IP and rewrite.

 

[Eternal Life]

did you allow port 7172 trough firewall?

 

[malice987]

Yeah ><

 

[Cykotitan]

It cant be this anyway, server status port is 7171 not 7172.
and both seem to be unreachable right now

as a final measure try disabling/uninstalling any antivirus or 3rd party firewall applications, windows firewall (only temporarily to see if it's the cause) and try restarting your router just in case it doesn't apply this kind of changes instantly

and verify that 124.181.145.212 is the correct IP for the no-ip host, if you have a dynamic IP

 

[megachock]

Ehmm did you forward the ports in the modem 192.168.1.1???

 

[Cykotitan]

if you read the posts on the previous page, you'll see he did that already