PilotOwl has submitted a ticket
Project Fika
#Server - Headless server timeout issue
sand stratusBOT
Thread started by: <@405783913810886657>
@outer lava please attach any applicable log files and mod lists while waiting for help!
You can find your log file at %AppData%\..\LocalLow\Battlestate Games\EscapeFromTarkov\Player.log
If you do not attach any logs, we will close the ticket without warning.
outer lava
I don't know where does the headless dumps it's logs
main goblet
BepInEx/LogOutput.log -- you'll need to create the situation in question and upload logs from when it is timed out since the logs get overwritten each time the client restarts
outer lava
BepInEx/LogOutput.log -- you'll need to create the situation in question and upl...
whenever it times out it doesn't create any new line in the terminal
this is why it is so hard for me to troubleshoot it
main goblet
that's fine, but you need to upload logs from when it happens
outer lava
I only run the server, I don't play on it.
so whenever it happens I need to be notified by the players to restart it manually
outer lava
that's fine, but you need to upload logs from when it happens
can I upload the logs tomorrow?
or in a couple of hours?
main goblet
as long as the intent is to provide the correct logs i don't think anyone will close this ticket
outer lava
only changed 1 thing at the bottom to this ↓
[Info : Fika.Core] Cached local IPs: 0.0.0.0, [correct local IP]
idk how serious the "don't dox yourself" rule is
but after 0.0.0.0 the IP is the correct local IP that is reffering to the Server PC
this is a log from a "currently working but invisible to players" headless client
in the log there are multiple mods
I don't wanted to remove them for this demonstration
but it creates the same exact outcome with and without other mods
sorry for the clutter
main goblet
only changed 1 thing at the bottom to this ↓
`[Info : Fika.Core] Cached local ...
did you happen to cut this log off by chance? bottom of my log for a headless client that is fully loaded has two more lines after the WS Connect() line
outer lava
did you happen to cut this log off by chance? bottom of my log for a headless cl...
no
I didn't cut anything out of it except the line I modified and disclosed
although the line you brought up does show up in the terminal of the headless client
main goblet
should show in the log as well, not sure why it wouldn't unless there was some confusion about which log file goes with which headless console
outer lava
my apologies
apparently it was a super good timing from the headless, or something happened opening the log
because now it is working again..
the the log I uploaded is from a headless restarting
this is why it is missing the last 2 lines
currently I have no timed out headless client.
please give a couple of hours to reproduce the issue and upload a log that connects to my issue
outer lava
To eliminate any misunderstandings
resulting another waiting time
I copied the LogOutput from the same headless when it was still running and right after I stopped it (closing the PowerShell terminal too)
only modifying the local IP in both of them
clear rampart
is that a public ip in there?
outer lava
is that a public ip in there?
sorry about that
clear rampart
what ip is it connecting to? is the server not on the same machine?
and I see some mods I don't think would be necessary on the headless
outer lava
what ip is it connecting to? is the server not on the same machine?
The SPT server is running on the same machine as the headless
the IP is connecting to the same server
clear rampart
why do you not have it set to 127.0.0.1?
outer lava
why do you not have it set to 127.0.0.1?
it was told by the installation manual
clear rampart
it was told by the installation manual
PF or VPN?
outer lava
I didn't know it will accept the loopback IP
outer lava
PF or VPN?
port forwarding
clear rampart
then your spt server should be on 0.0.0.0 which is 'broadcast on all available ips'
I'd guess its timing out on the nat hairpin
so headless script should be local loop
outer lava
so if I change it in the fika-server>assets>configs>fika.jsonc
at the headless section
"scripts": {
"generate":true,
"forceIp": 0.0.0.0
},
it should work?
and pasting the IP there was just overcomplicated it?
clear rampart
no, it should be the loopback as I said
the server window should show 0.0.0.0: 6969 right?
and the script should generate the ps1 as 127.0.0.1
outer lava
the server window should show 0.0.0.0: 6969 right?
at the server section it is 0.0.0.0
"SPT": {
"http": {
"ip": "0.0.0.0",
"port": 6969
but the backedIp it set to the WAN IP as it wasn't working when it was 0.0.0.0 (with the same 6969 port)
outer lava
the players were unable to join
they just got a timout message in the SPT client
as soon as it was changed to the WAN IP it was accessible with no issues
clear rampart
well you are going to have to suffer with the headlesses I'd guess unless its a mod.
I'm going to guess nat loopback is initialized once and if not used its not allowed? but you have mods, so all bets are off
outer lava
well you are going to have to suffer with the headlesses I'd guess unless its a ...
we only did a test with absolutely no mods, just to see if my server PC can actually do the Tarkov server
the mods were only added later
clear rampart
you are only the second time WAN backend has had to be filled in in the hundreds of folks I've helped with this
is your network adapter set as public or private?
outer lava
is your network adapter set as public or private?
public
although automatic DHCP
which I just realised, and should be turned off if I actually want to use it as a server :/
clear rampart
should be private and set to a static
I'd check that again as 0.0.0.0 after as well
outer lava
should be private and set to a static
thank you so much :D
that solved the WAN IP problem
do I need to regenerate the scripts to update them to the "new" 127.0.0.1 IP?
or do they know from the fika.jsonc?
Thank you so much for helping
I am very confident that this has solved all of my problems with the headless
but can I keep this open for a couple of hours to verify if it actually solved the timeout problem?