• 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!

Internal problem opening ports

Jpstafe

Jpstafe

Well-Known Member
Joined
Aug 8, 2011
Messages
518
Reaction score
69
Hello otland community, I am trying to open the ports from my notebook, to open an otserv war to play with my team... the issue is that I go into the router configuration, open the ports or activate dmz mode and it keeps giving me ports closed...open the firewall ports, deactivate all types of security and it still doesn't work, is it a problem of poor configuration on my part or the provider that gives me the internet?
1718112630274.png
1718112656667.png
1718112673493.png
1718112697294.png
1718112744105.png
Post automatically merged:

1718112809195.png
 
Sort by date Sort by votes
El Bringy said:
make sure you have enabled NAT and have the correct IPv4 of the pc including the TFS exe (port listener)
Click to expand...
How can I check the nat? in firewall at the ports entry, add the exe. from otserver
Post automatically merged:

Jpstafe said:
How can I check the nat? in firewall at the ports entry, add the exe. from otserver
Click to expand...
C:\Windows\System32\drivers\etc\host:
Lua: 
# localhost name resolution is handled within DNS itself.
#    127.0.0.1       localhost
#    ::1             localhost
    192.168.100.12  testotarg.ddns.net
config.lua
Lua: 
-- Connection Config
-- NOTE: maxPlayers set to 0 means no limit
-- NOTE: allowWalkthrough is only applicable to players
ip = "testotarg.ddns.net"
bindOnlyGlobalAddress = false
1718118398762.png
otclient inti.lua:
Lua: 
-- Servers accept http login url, websocket login url or ip:port:version
Servers = {

    rookie = "testotarg.ddns.net:7171:772"
It fits perfectly for me, with these configurations, but when I pass it to a friend and he tries to enter, it doesn't fit.
 
Last edited:
Upvote 0 Downvote
I recommend adding the ports one by one, sometimes it has a fault and that's why it doesn't load.

tcp 7171 port udp 7171
tcp 7172 port udp 7172
 
Upvote 0 Downvote
adric21 said:
I recommend adding the ports one by one, sometimes it has a fault and that's why it doesn't load.

tcp 7171 port udp 7171
tcp 7172 port udp 7172
Click to expand...
1718123728220.png
1718123769968.png
There I added them one by one, in the Windows firewalls entry, I also added them one by one... I restarted the modem, to see if that was it... and nothing... it still doesn't work...
 
Upvote 0 Downvote
Jpstafe said:
C:\Windows\System32\drivers\etc\host:

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
192.168.100.12 testotarg.ddns.net

config.lua
-- Connection Config

-- NOTE: maxPlayers set to 0 means no limit
-- NOTE: allowWalkthrough is only applicable to players
ip = "testotarg.ddns.net"
Click to expand...
Your IP in config.lua must be set to your public IP (not local network IP). You should not add that row in hosts file.
IDK what OTS engine you are using, but many engines have problems with running on localhost with redirected ports. They are listening on wrong IP or ignore connections from forwarded ports.

To check on what IP your server is listening run cmd in Windows and type:
Code: 
netstat -na
There will be :7171 somewhere and IP on left side. It should listen on 0.0.0.0 or your local network IP (192.168.100.12).
If it listens on 127.0.0.1 then your engine is accessible only from localhost.

It's also known issue of many OTS engines, that if you run server on localhost and it's accessible from internet, it's not accessible from localhost (same PC). So if you configure it to make it work for players, you won't be able to login GOD characters from same PC.

It's much easier to learn Linux, get VPS/Cloud for few $ or even free ( How to get FREE VPS from Oracle Cloud (https://otland.net/threads/how-to-get-free-vps-from-oracle-cloud.279318/) ) and run server on it.
 
Upvote 0 Downvote
Gesior.pl said:
Your IP in config.lua must be set to your public IP (not local network IP). You should not add that row in hosts file.
IDK what OTS engine you are using, but many engines have problems with running on localhost with redirected ports. They are listening on wrong IP or ignore connections from forwarded ports.

To check on what IP your server is listening run cmd in Windows and type:
Code: 
netstat -na
There will be :7171 somewhere and IP on left side. It should listen on 0.0.0.0 or your local network IP (192.168.100.12).
If it listens on 127.0.0.1 then your engine is accessible only from localhost.

It's also known issue of many OTS engines, that if you run server on localhost and it's accessible from internet, it's not accessible from localhost (same PC). So if you configure it to make it work for players, you won't be able to login GOD characters from same PC.

It's much easier to learn Linux, get VPS/Cloud for few $ or even free ( How to get FREE VPS from Oracle Cloud (https://otland.net/threads/how-to-get-free-vps-from-oracle-cloud.279318/) ) and run server on it.
Click to expand...
Thanks for the information, I know that in config.lua in the IP part the global IP goes there-- in numbers, not the IP that generates the NO-IP, the issue when I look for what my global IP is on several pages They give me different ips... and the ip that the no-ip DUC program generates changes every 10 minutes... that is the question too.
in netset -a
I have not been able to find anything related to my ip4 and the necessary ports 7171,7172,80.
Why this is, I don't know.
Lua: 
Conexiones activas

  Proto  Dirección local        Dirección remota       Estado
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:623            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5040           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:16992          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:45769          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49664          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49665          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49666          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49667          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49668          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49669          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49670          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49671          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:6463         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:49701        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:52098        127.0.0.1:52099        ESTABLISHED
  TCP    127.0.0.1:52099        127.0.0.1:52098        ESTABLISHED
  TCP    127.0.0.1:52100        127.0.0.1:52101        ESTABLISHED
  TCP    127.0.0.1:52101        127.0.0.1:52100        ESTABLISHED
  TCP    127.0.0.1:52117        127.0.0.1:52118        ESTABLISHED
  TCP    127.0.0.1:52118        127.0.0.1:52117        ESTABLISHED
  TCP    127.0.0.1:52119        127.0.0.1:52120        ESTABLISHED
  TCP    127.0.0.1:52120        127.0.0.1:52119        ESTABLISHED
  TCP    127.0.0.1:52124        127.0.0.1:52125        ESTABLISHED
  TCP    127.0.0.1:52125        127.0.0.1:52124        ESTABLISHED
  TCP    127.0.0.1:52140        0.0.0.0:0              LISTENING
  TCP    192.168.100.24:139     0.0.0.0:0              LISTENING
  TCP    192.168.100.24:49693   2.23.164.205:443       LAST_ACK
  TCP    192.168.100.24:49694   2.23.164.208:443       LAST_ACK
  TCP    192.168.100.24:49695   2.23.164.208:443       LAST_ACK
  TCP    192.168.100.24:49696   2.23.164.208:443       LAST_ACK
  TCP    192.168.100.24:49797   20.127.250.238:443     ESTABLISHED
  TCP    192.168.100.24:49878   52.226.139.185:443     ESTABLISHED
  TCP    192.168.100.24:52049   3.160.90.81:443        CLOSE_WAIT
  TCP    192.168.100.24:52116   172.64.146.73:443      CLOSE_WAIT
  TCP    192.168.100.24:52123   172.64.146.73:443      CLOSE_WAIT
  TCP    192.168.100.24:52848   162.159.130.234:443    ESTABLISHED
  TCP    192.168.100.24:52885   52.226.139.121:443     ESTABLISHED
  TCP    192.168.100.24:52905   162.247.243.29:443     ESTABLISHED
  TCP    192.168.100.24:52906   162.247.243.29:443     ESTABLISHED
  TCP    192.168.100.24:52908   20.42.65.94:443        ESTABLISHED
  TCP    192.168.100.24:52909   31.13.94.52:443        ESTABLISHED
  TCP    192.168.100.24:52911   104.21.51.77:443       ESTABLISHED
  TCP    192.168.100.24:52917   162.247.243.29:443     ESTABLISHED
  TCP    192.168.100.24:52919   20.110.205.119:443     ESTABLISHED
  TCP    192.168.100.24:52921   3.160.90.8:443         ESTABLISHED
  TCP    192.168.100.24:52923   20.42.65.89:443        ESTABLISHED
  TCP    192.168.100.24:52926   184.31.2.81:443        ESTABLISHED
  TCP    192.168.100.24:52927   204.79.197.203:443     ESTABLISHED
  TCP    192.168.100.24:52928   2.23.164.217:443       ESTABLISHED
  TCP    192.168.100.24:52932   190.123.95.147:443     ESTABLISHED
  TCP    192.168.100.24:52934   184.31.2.81:443        ESTABLISHED
  TCP    192.168.100.24:52935   35.244.182.232:443     TIME_WAIT
  TCP    192.168.100.24:52936   142.251.134.27:443     ESTABLISHED
  TCP    192.168.100.24:52937   2.23.164.146:443       TIME_WAIT
  TCP    192.168.100.24:52938   104.17.245.203:443     ESTABLISHED
  TCP    192.168.100.24:52941   23.197.235.104:443     TIME_WAIT
  TCP    192.168.100.24:52942   20.201.52.37:443       ESTABLISHED
  TCP    192.168.100.24:52943   3.160.90.73:443        ESTABLISHED
  TCP    192.168.100.24:52944   23.197.235.104:443     TIME_WAIT
  TCP    192.168.100.24:52945   52.111.225.21:443      ESTABLISHED
  TCP    192.168.100.24:52946   204.79.197.239:443     ESTABLISHED
  TCP    192.168.100.24:52952   151.101.1.44:443       ESTABLISHED
  TCP    192.168.100.24:52954   104.26.9.44:443        ESTABLISHED
  TCP    192.168.100.24:52955   44.241.7.141:443       TIME_WAIT
  TCP    192.168.100.24:52957   52.223.22.214:443      ESTABLISHED
  TCP    192.168.100.24:52961   141.148.187.134:443    TIME_WAIT
  TCP    192.168.100.24:52963   35.208.249.213:443     ESTABLISHED
  TCP    192.168.100.24:52964   190.123.95.139:80      ESTABLISHED
  TCP    192.168.100.24:52965   2.19.45.2:80           ESTABLISHED
  TCP    192.168.100.24:52966   35.213.89.133:443      ESTABLISHED
  TCP    192.168.100.24:52967   2.19.45.2:80           ESTABLISHED
  TCP    192.168.100.24:52968   35.213.89.133:443      TIME_WAIT
  TCP    192.168.100.24:52969   3.162.185.37:443       TIME_WAIT
  TCP    192.168.100.24:52974   142.250.79.110:443     TIME_WAIT
  TCP    192.168.100.24:52975   20.198.2.181:443       TIME_WAIT
  TCP    192.168.100.24:52978   204.79.197.200:443     ESTABLISHED
  TCP    192.168.100.24:52979   162.159.129.233:443    ESTABLISHED
  TCP    192.168.100.24:52980   158.247.7.204:80       TIME_WAIT
  TCP    192.168.100.24:52983   158.247.7.204:80       TIME_WAIT
  TCP    192.168.100.24:52984   31.13.94.52:443        ESTABLISHED
  TCP    192.168.100.24:52985   204.79.197.219:443     ESTABLISHED
  TCP    192.168.100.24:52986   204.79.197.219:443     ESTABLISHED
  TCP    192.168.100.24:52989   191.237.206.80:443     ESTABLISHED
  TCP    192.168.100.24:52990   104.18.9.90:443        ESTABLISHED
  TCP    192.168.100.24:52991   104.18.9.90:443        ESTABLISHED
  TCP    192.168.100.24:52992   104.18.9.90:443        ESTABLISHED
  TCP    192.168.100.24:52993   104.18.9.90:443        ESTABLISHED
  TCP    192.168.100.24:52994   104.18.9.90:443        ESTABLISHED
  TCP    192.168.100.24:52995   104.18.9.90:443        ESTABLISHED
  TCP    192.168.100.24:52996   204.79.197.237:443     ESTABLISHED
  TCP    192.168.100.24:52997   204.79.197.203:443     ESTABLISHED
  TCP    192.168.100.24:52998   20.198.2.181:443       ESTABLISHED
  TCP    192.168.100.24:52999   2.23.164.208:443       ESTABLISHED
  TCP    192.168.100.24:53000   2.23.164.205:443       ESTABLISHED
  TCP    192.168.100.24:53003   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53004   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53005   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53006   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53007   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53008   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53009   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53010   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53011   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53012   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53013   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53014   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53015   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53016   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53017   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53018   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53019   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53020   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53021   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53022   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53023   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53024   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53025   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53026   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53027   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53028   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53029   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53030   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53031   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53032   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53033   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53034   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53035   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53036   2.23.164.204:443       ESTABLISHED
  TCP    192.168.100.24:53038   52.97.28.194:443       ESTABLISHED
  TCP    192.168.100.24:53039   20.189.173.27:443      ESTABLISHED
  TCP    192.168.100.24:53040   204.79.197.222:443     ESTABLISHED
  TCP    192.168.100.24:65271   3.160.90.59:443        CLOSE_WAIT
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:623               [::]:0                 LISTENING
  TCP    [::]:3389              [::]:0                 LISTENING
  TCP    [::]:5357              [::]:0                 LISTENING
  TCP    [::]:16992             [::]:0                 LISTENING
  TCP    [::]:49664             [::]:0                 LISTENING
  TCP    [::]:49665             [::]:0                 LISTENING
  TCP    [::]:49666             [::]:0                 LISTENING
  TCP    [::]:49667             [::]:0                 LISTENING
  TCP    [::]:49668             [::]:0                 LISTENING
  TCP    [::]:49669             [::]:0                 LISTENING
  TCP    [::]:49670             [::]:0                 LISTENING
  TCP    [::]:49671             [::]:0                 LISTENING
  TCP    [::1]:49698            [::]:0                 LISTENING
  TCP    [::1]:49704            [::1]:49706            ESTABLISHED
  TCP    [::1]:49706            [::1]:49704            ESTABLISHED
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:3389           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5050           *:*
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:45769          *:*
  UDP    0.0.0.0:49605          *:*
  UDP    0.0.0.0:49663          *:*
  UDP    0.0.0.0:49664          *:*
  UDP    0.0.0.0:50202          *:*
  UDP    0.0.0.0:52888          *:*
  UDP    0.0.0.0:53092          *:*
  UDP    0.0.0.0:53094          *:*
  UDP    0.0.0.0:55053          *:*
  UDP    0.0.0.0:56320          *:*
  UDP    0.0.0.0:56688          *:*
  UDP    0.0.0.0:57666          *:*
  UDP    0.0.0.0:58411          *:*
  UDP    0.0.0.0:59037          *:*
  UDP    0.0.0.0:63233          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:49666        *:*
  UDP    127.0.0.1:49671        *:*
  UDP    192.168.100.24:137     *:*
  UDP    192.168.100.24:138     *:*
  UDP    192.168.100.24:1900    *:*
  UDP    192.168.100.24:5353    *:*
  UDP    192.168.100.24:49672   *:*
  UDP    [::]:500               *:*
  UDP    [::]:3389              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:4500              *:*
  UDP    [::]:5353              *:*
  UDP    [::]:5353              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:49665             *:*
  UDP    [::]:53093             *:*
  UDP    [::]:53095             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:5353             *:*
  UDP    [::1]:49669            *:*
  UDP    [fe80::c5a4:735:9560:f4a8%15]:1900  *:*
  UDP    [fe80::c5a4:735:9560:f4a8%15]:49670  *:*
I was finding out about Oracle, you can get a free Linux vps, I just wanted to use my internet to open a server for friends, so we tested for bugs and had a little fun... so as not to go through the work of hiring a server and etc.. If I don't have much knowledge of Linux, here in the forum open a tutorial on how to open servers with Linux? I have 0 knowledge of Linux
 
Upvote 0 Downvote
@Jpstafe
Lua: 
192.168.100.12
7171 - login port
7172 - game port
80   - http      - v
8080 - https     - apache
3306 - for mysql
7173 - for cast
TCP/UDP
Firewall OFF
Defender OFF

Firewall on router option LOW Security or OFF

after all u can use in cmd command:
gpupdate

Engine.exe (tfs) run as admin.
If not working then try use DMZ on your router with IP 192.168.100.12

Your friends have errors in client at login?
 
Upvote 0 Downvote
Paxiz said:
@Jpstafe
Lua: 
192.168.100.12
7171 - login port
7172 - game port
80   - http      - v
8080 - https     - apache
3306 - for mysql
7173 - for cast
TCP/UDP
Firewall OFF
Defender OFF

Firewall on router option LOW Security or OFF

after all u can use in cmd command:
gpupdate

Engine.exe (tfs) run as admin.
If not working then try use DMZ on your router with IP 192.168.100.12

Your friends have errors in client at login?
Click to expand...
Yes, they do, I have tried on another PC, where I am not hosting it and the same thing..
Post automatically merged:

Diarreamental said:
tried using opening the ports from modem instead of router?
Click to expand...
From the router they gave me, it's a Huawei... I told the company to open the ports for me and they don't know xD hahaha I live in an area that is semi-rural, and the internet company here does know how to install the modem It's already a lot, they don't know anything about configuring and etc... they gave me the admin and password of the router
 
Upvote 0 Downvote
Jpstafe said:
Yes, they do, I have tried on another PC, where I am not hosting it and the same thing..
Post automatically merged:


From the router they gave me, it's a Huawei... I told the company to open the ports for me and they don't know xD hahaha I live in an area that is semi-rural, and the internet company here does know how to install the modem It's already a lot, they don't know anything about configuring and etc... they gave me the admin and password of the router
Click to expand...
IPv4 Port Mapping, but check your Security TAB, must be low security or better - off.
If doesnt work with it then open DMZ on IP 192.168.100.12 without port mapping.
 
Upvote 0 Downvote
It happened to me before. I used to host my OT server online from my home machine, and then after a few years, when I tried to host it again, I couldn't. It took me a while to figure out that my internet provider had implemented something called CGNAT (Carrier Grade NAT). I couldn't put any Tibia OT or other games online either. I had to complain to the company, and they told me I had to request them to open the ports for CGNAT so I could host my game online. So, I requested it and they allowed it. I managed to put my OT server online. I'm not sure if your internet provider uses CGNAT, but you may need to talk to them to get your OT server online, understand?


The simple solution is to either hire a VPS or use the Radmin VPN program to solve the problem.
 
Upvote 0 Downvote
Mateus Robeerto said:
It happened to me before. I used to host my OT server online from my home machine, and then after a few years, when I tried to host it again, I couldn't. It took me a while to figure out that my internet provider had implemented something called CGNAT (Carrier Grade NAT). I couldn't put any Tibia OT or other games online either. I had to complain to the company, and they told me I had to request them to open the ports for CGNAT so I could host my game online. So, I requested it and they allowed it. I managed to put my OT server online. I'm not sure if your internet provider uses CGNAT, but you may need to talk to them to get your OT server online, understand?


The simple solution is to either hire a VPS or use the Radmin VPN program to solve the problem.
Click to expand...
Yes I understand, the issue is that they don't know anything, I asked them to open the ports for me and they told me to do it from the router, that they don't know about the subject... I tell you, it's a middle-of-the-road internet provider... like this If they know how to install internet, it's a lot... so imagine... open a CGNAT option inside the router to configure it? Now I'll start searching
 
Upvote 0 Downvote
Hello, I'm still complaining, it's not that I refuse to pay for a host, but I think it's unnecessary, because it's for playing with friends and I'd be spending money for nothing... from what they had me commenting on, they told me what it could be in case I have in the IP the CGNAT is active... so I tested the ip4 and it seems that I do not have it active in the CGNAT... and that could be a reason why the ports cannot be opened, Google gave me that information "If you use a server to access the content of your computer remotely when you are away from home, this type of technology would not allow you to do so. You will also not be able to connect to the NAS server because it requires open ports and CG-NAT will not allow you to open them.
01.png
To check the cgnat in cmd I put tracert > (the ip4)
What Is My IP?
My Public IPv4:
190.105.220.25

My Public IPv6:
Not Detected
My IP Location:
Helvecia, S AR

My ISP:
Pogliotti & Pogliotti Construcciones S.ATrace to the address host25.190-105-220.sitsanetworks.net [190.105.220.25]
over a maximum of 30 jumps:

1 2 ms 2 ms 2 ms 192.168.100.1
2 * 5ms 7ms 10.0.0.1
3 6 ms 4 ms 4 ms host25.190-105-220.sitsanetworks.net [190.105.220.25]

Asking chatgpt it told me this:
Thanks for providing the information. It looks like you have a public IP address (190.105.220.25), which is a good indication that you are not behind CGNAT at the moment. Here are some key points based on the information you've provided:

Public IP address: Your public IP address is 190.105.220.25. This means that your ISP is assigning you a public IP address directly, which is necessary to be able to open ports and host services such as a Tibia server.

Traceroute: The traceroute result shows that your connection directly reaches your public IP address without going through additional private addresses, which is another sign that you are not behind a CGNAT that could complicate opening ports.
So what am I doing wrong? If my public IP appears to not have CGNAT
 
Upvote 0 Downvote
Jpstafe said:
CGNAT
Click to expand...
It's something even worse than NAT. It means that network provider has less IPv4 addresses than clients. So they use CGNAT to use same IP for multiple clients. It's not a big problem for normal users (watch YT, visit sites), but it does not allow clients to host anything using public IP.
You cannot easily detect (using tools ex. 'what is my IP', ping etc.), if "your" public IP is "yours" (not behind CGNAT) - you have to ask your network provider.

You can spend hour or whole day trying to fix NAT/Windows/OTS configuration or
try to get free 24 GB RAM Linux server in 15 minutes ( How to get FREE VPS from Oracle Cloud (https://otland.net/threads/how-to-get-free-vps-from-oracle-cloud.279318/) ) or
just order Linux VPS for 10 EUR [next month 4.5 EUR] ( Cloud VPS 1 | Low Price, High Performance Virtual Private Servers | Contabo (https://contabo.com/en/vps/cloud-vps-1/?image=ubuntu.267&qty=1&contract=1&storage-type=vps1-100-gb-nvme) ).
 
Upvote 0 Downvote
Gesior.pl said:
It's something even worse than NAT. It means that network provider has less IPv4 addresses than clients. So they use CGNAT to use same IP for multiple clients. It's not a big problem for normal users (watch YT, visit sites), but it does not allow clients to host anything using public IP.
You cannot easily detect (using tools ex. 'what is my IP', ping etc.), if "your" public IP is "yours" (not behind CGNAT) - you have to ask your network provider.

You can spend hour or whole day trying to fix NAT/Windows/OTS configuration or
try to get free 24 GB RAM Linux server in 15 minutes ( How to get FREE VPS from Oracle Cloud (https://otland.net/threads/how-to-get-free-vps-from-oracle-cloud.279318/) ) or
just order Linux VPS for 10 EUR [next month 4.5 EUR] ( Cloud VPS 1 | Low Price, High Performance Virtual Private Servers | Contabo (https://contabo.com/en/vps/cloud-vps-1/?image=ubuntu.267&qty=1&contract=1&storage-type=vps1-100-gb-nvme) ).
Click to expand...
Yes, I have seen it in the tutorial, but now they ask you for a minimum of 1 USD, it's not that I don't have it... but I don't have it physically on the card, because in my country you can't acquire the dollar with your debit, so why? Yes, it's bullshit in Argentina, people have dollars physically, we handle Argentine pesos... back then, that way, I was looking to open it from my computer... because until now Google Cloud also withholds 1 USD from you... I didn't do it before , so I don't know how to have those USD on the card
 
Upvote 0 Downvote
Jpstafe said:
Yes, I have seen it in the tutorial, but now they ask you for a minimum of 1 USD
Click to expand...
I'm pretty sure that Hetzner.com and Contabo.com accepts PayPal without any credit card.
On Contabo you order VPSes, so you pay just for servers you order (ex. 10 EUR).
On Hetzner they offer 'cloud' (payment per hour), so you have to pay 20 EUR in advance, but I heard that some people get link from AD that adds 20$ for free and they did not have to pay anything (maybe it works when you use card as payment method, I've used PayPal and had to pay 20 EUR in advance).

IDK how it works in Argentina, but my friend from Poland registered 4 Oracle Free Tier accounts with 4 virtual credit cards (not debit cards) using Revolut app (european bank) and use 4x 4 cores for around 2 years to mine crypto.

If you want to check, if your server is able to run on Hetzner.com machine, I can order some cheap cloud (4 cores, 8 GB RAM) for tests using my Hetzner account. Message me on Discord: gesior.pl
 
Upvote 0 Downvote

Similar threads

Jpstafe
  • Question
Error 10060 on my vps, how do I solve it?
Replies
13
Views
769
highsanta
highsanta
2
  • Question
No one logs into the server, otserv active
Replies
0
Views
278
2057623
2
juansanchez
  • Question
TFS 0.X RSA_Decrypt issue
Replies
0
Views
251
juansanchez
juansanchez
Tibia Idle
  • Question
Solved Znote no send mails
Replies
2
Views
225
Tibia Idle
Tibia Idle
Back
Top