Tarkov Fika - Missing user-defined parameters for http.json in configuration settings

[Triscuit47]

System Information

Field	Value
Operating System	Windows - Windows 11 22H2
Product	AMP ‘Phobos’ v2.6.0.10 (Mainline)
Virtualization	None
Application	Tarkov (Fika Mod)
Module	GenericModule
Running in Container	No
Current State	Idle

Problem Description

Issue

I am unable to edit any parameters in the http.json file from “[instance location]\tarkov\server\SPT_Data\Server\configs” because the file gets overridden on every server start with the default values. As per Fika documentation the file should look like this.

> {
>   "ip": "0.0.0.0",
>   "port": 6969,
>   "backendIp": "WAN IP",
>   "backendPort": 6969,
>   "webSocketPingDelayMs": 90000,
>   "logRequests": true,
>   "serverImagePathOverride": {}
> }

However, upon changing the parameters, the file gets reloaded with

> {
>   "ip": "<instance local ip>",
>   "port": 6969,
>   "backendIp": "<instance local ip>",
>   "backendPort": 6969,
...
> }

Adding the ability for the user to define the ip addresses as well as the ports via the Configuration page in the Instance Management would be great!

Reproduction Steps

• Create Instance
• Start the server once so the files get created
• Stop the server
• Go to “[instance location]\tarkov\server\SPT_Data\Server\configs\http.json” and edit the file with the required settings and save the file
• Start the server
• Notice the file gets reverted back to the original values

[Greelan]

You can change the binding of the server and that will change the first field (ip). Search for “Server IP Address”

Regarding the backendip, despite what the docs say (they haven’t been updated), it is actually recommended to keep that the same as the ip. This has been discussed quite a bit in their discord, and avoids the issues people have encountered when setting to the wan ip as the docs say

[Triscuit47]

Thank you for the tip! As for the port, If I change the instance’s port will it also change in the file?

LE: Just changed the game port to the one I use and set the instance bind IP to 0.0.0.0 and it works perfectly!