Newest fxserver builds: http://localhost:port/info.json does not work

FiveM Discussion Bug reports
1

Hello,
using txAdmin with newest builds (2802 and 2807) gives this error:
Monitor Status: Partial
FXServer /info.json:
Failed to retrieve FXServer data.
The server must be online for this operation.
Check the terminal for more information (if verbosity is enabled)

When I revert back to build 2740, everything works fine.

Problem is that txAdmin restarts server every 5 minutes (says crash detected) even tho server is running as it should.

Some info about machine:
Node Version: v12.13.0
OS Type: Linux (linux/x64)
OS Release: 5.4.0-42-generic

As I said, I change nothing but fxserver build. 2740 works fine, 2802 and 2807 keeps restarting server every 5 minutes.

2

txAdmin fetches info.json from localhost like that:

http://localhost:${port}/info.json

So I created two servers, one on port 30120 using build 2740 and one on port 30121 using build 2802. When I started both, i tried to get the info.json.

The one using build 2740 worked fine:

$ wget localhost:30120/info.json
--2020-08-11 00:29:05--  http://localhost:30120/info.json
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:30120... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:30120... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified
Saving to: 'info.json'

info.json                                              [ <=>                                                                                                            ]   6.76K  --.-KB/s    in 0s      

2020-08-11 00:29:05 (103 MB/s) - 'info.json' saved [6921]

The other one using build 2802 ended up with error:

$ wget localhost:30121/info.json
--2020-08-11 00:29:44--  http://localhost:30121/info.json
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:30121... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:30121... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2020-08-11 00:29:45--  (try: 2)  http://localhost:30121/info.json
Connecting to localhost (localhost)|127.0.0.1|:30121... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2020-08-11 00:29:51--  (try: 3)  http://localhost:30121/info.json
Connecting to localhost (localhost)|127.0.0.1|:30121... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2020-08-11 00:29:57--  (try: 4)  http://localhost:30121/info.json
Connecting to localhost (localhost)|127.0.0.1|:30121... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2020-08-11 00:30:03--  (try: 5)  http://localhost:30121/info.json
Connecting to localhost (localhost)|127.0.0.1|:30121... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

If I use domain name instead of localhost, then I sucesfully get info.json from both. txAdmin uses localhost tho.

3

Works perfectly fine for me on the following version:

“version” is “FXServer-master SERVER v1.0.0.2807 win32”

4

Seems to only be problem on Linux.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal
5

I will wait for more information.
BTW, txAdmin uses dynamic.json instead of info.json.

6

Are you by chance exceeding the default connection limit per IP?

8

That is very unlikely. I found more people with the same issue (build 2802+ on Linux) on txAdmin Discord.
And also I tried it on another machine with the same output.

Weird thing is that using public-ip:port/info.json works, while localhost:port/info.json does not.

9

Latest already fixes this, anyway.

10

Using build 2832 localhost:port/info.json now works.

But public-ip:port/info.json somehow stopped working when called from the machine. Really odd.

$ wget http://82.208.16.150:30120/info.json
--2020-08-13 17:18:12--  http://82.208.16.150:30120/info.json
Connecting to 82.208.16.150:30120... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2020-08-13 17:18:16--  (try: 2)  http://82.208.16.150:30120/info.json
Connecting to 82.208.16.150:30120... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

--2020-08-13 17:18:22--  (try: 3)  http://82.208.16.150:30120/info.json
Connecting to 82.208.16.150:30120... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

$ wget http://localhost:30120/info.json
--2020-08-13 17:18:09--  http://localhost:30120/info.json
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:30120... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:30120... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified
Saving to: 'info.json.4'

info.json.4                                            [ <=>                                                                                                            ]   6.79K  --.-KB/s    in 0s      

2020-08-13 17:18:10 (1000 MB/s) - 'info.json.4' saved [6951]