[WildCard65]

Check your router's port forwarding settings maybe? Make sure it forwards the port to your computer's lan ip and if your lan ip changed(because of dynamic ips thing), update the port forward settings)

[Maxximou5]

Please note that you've been using +ip when the correct usage is -ip. This may fix your issue. Try your outside ip if not try it with -ip 0.0.0.0

[St00ne]

+1 for Baca, I just realised the same thing.
I know it's been a long time :p
@Maxximou5: I'm sorry but I think it's +ip (any command available ingame, and ip is one of them, has the + prefix). The - prefix is for commands only available at launch, i.e. some kind of locked parameters.

PS: just tested and both work. Anyway, like said earlier, no need to write it.

[Maxximou5]

Don't necro post a 5 year old thread.

Originally Posted by St00ne @Maxximou5: I'm sorry but I think it's +ip (any command available ingame, and ip is one of them, has the + prefix). The - prefix is for commands only available at launch, i.e. some kind of locked parameters.

If you're launching a server, you always use -ip first, don't use +ip.
https://developer.valvesoftware.com/...dicated_Server

-ip Specifies the address to use for the bind(2) syscall, which controls on which IP addresses the program is reachable on. It must either be a local address (an addresses of the host it runs on) or 0.0.0.0 (the wildcard). This has nothing to do with externally-visible addresses in NAT setups.

[St00ne]

Ok thx
I think public IP can be set by net_public_adr and the -ip is for internal IP.
I was just saying that even though you say it's a different thing, +IP works ('old but still works' as they say on Valve Forums) and was supposed to be pointing to the same IP that you use when you write -ip, that is to say, the internal IP program is running on.
Regards