Quote:
Originally Posted by YuGiOhJCJ
Now I have a wonderful new message:
"Connection to Steam servers successful.
VAC secure mode disabled."
But a terribly new error message:
"[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed."
Anyway, I am still unable to connect to with my client to my server.
|
This is a good sight. Actually I forgot, you always must to use '+map map_name'.
I think this error is similar as the one solved on this other thread:
Quote:
Originally Posted by Arkshine
Set SELinux to permissive, or disable it, or use amxx 1.8.3-dev
|
Then looks like you were unable to connect to the server, because it were closed once the error was thrown.
Quote:
Originally Posted by YuGiOhJCJ
On my server machine, I have two network cards corresponding to the two network interfaces I have described previously.
Well, as there are more than 1 active network card on my server machine, my "+ip 78.199.90.154" option is correct.
|
If the ip 78.199.90.154 is the ip to your server's computer network board installed on your server, then your are doing it right.
However, you should use this to connect to your server:
Code:
connect 78.199.90.154:27014
Not 'connect 192.168.0.100:27014'.
But if it stills not working, the game is bugged and is not correctly recognizing your network board on '78.199.90.154'.
Then use '0.0.0.0' to tell to the game address to your server all networks boards on your server's computer.
Also note, the ip is showing here:
Code:
$ cat stdout.log
Auto-restarting the server on crash
Console initialized.
Protocol version 48
Exe version 1.1.2.7/Stdio (cstrike)
Exe build: 13:12:29 Aug 29 2013 (6153)
STEAM Auth Server
Server IP address 0.0.0.0:27015
couldn't exec listip.cfg
couldn't exec banned.cfg
$ cat stderr.log
Using breakpad crash handler
Setting breakpad minidump AppID = 10
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Is not the ip your server has on the internet, is the ip to the network board to which your server is bounded to. And '0.0.0.0' means all of them.
For example, my server always shows this:
Code:
506.2 fps 0/32 on cs_italy_mini
Console initialized.
Protocol version 48
Exe version 1.0.0.3 (czero)
Exe build: 13:13:28 Aug 29 2013 (6153)
STEAM Auth Server
Addons zz ' s Multi-Mod Server Loaded with SUCCESS !!!!
Server IP address 192.168.56.1:27013
Metamod version 1.21.1-am Copyright (c) 2001-2013 Will Day <[email protected]>
Metamod comes with ABSOLUTELY NO WARRANTY; for details type `meta gpl'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `meta gpl' for details.
AMX Mod X version 1.8.2-dev Copyright (c) 2004-2006 AMX Mod X Development Team
AMX Mod X comes with ABSOLUTELY NO WARRANTY; for details type `amxx gpl'.
This is free software and you are welcome to redistribute it under
certain conditions; type 'amxx gpl' for details.
stray key in process_key: item_getiteminfo 61
POD-Bot mm: plugin attaching
Taking settings from podbot.cfg
Settings (cvars) for POD-Bot mm loaded from podbot.cfg
Loading & decompressing Experience Data
But that is not my internet ip, it is the ip to my network board to which my server is bounded to.
And my server is always available online and accessible by my internet ip.
If you use the '+ip' as '0.0.0.0' you must to be able to connect to your server using both of your network board ips:
Code:
connect 192.168.0.100:27014
connect 78.199.90.154:27014
Otherwise an '+ip' as '192.168.0.100' only allows you to use 'connect 192.168.0.100:27014', and not 'connect 78.199.90.154:27014'. And vice-versa.
__________________