AC Server JSON on loop and not running on Kunos

I hope someone can assist me with this.
I used to be able to run servers with absolutely no problem. I had to do a router reset (which I have done before), redid my port forwarding like before, but for some reason the server does not work.
Using AC Server manager or CM it seems to be doing the same thing. I can find the server on LAN and join my own server. But it is not visible to others, I can find my server under Kunos but only with an error reading that "cant connect to server"
Once I run the server and test the ports, it does show that the forwarding is working fine. I've searched everywhere for a solution but thus far couldn't find anything. Anyone hear that knows how to fix this? (From South Africa, and unfortunately doesn't seem like there is any AC compatible servers for rent either in my area)
I have done a re-check with Steam, updated and changed to different CM.
Herewith a log of trying to run a server:

18:11:18.160: > Server CFG Path : H:\Games insalled\SteamLibrary\steamapps\common\assettocorsa\server\presets\SERVER_00\server_cfg.ini
18:11:18.160: > Entry List Path : H:\Games insalled\SteamLibrary\steamapps\common\assettocorsa\server\presets\SERVER_00\entry_list.ini
18:11:18.161: > Assetto Corsa Dedicated Server v1.15
18:11:18.161: > Protocol version: 202
18:11:18.162: > 2022-06-28 18:11:18.1593401 +0200 SAST m=+0.006997000
18:11:18.162: > Num CPU: 8
18:11:18.171: > LOCAL IP 0: fe80::70e8:54e1:b8f6:25cc%Ethernet
18:11:18.172: > LOCAL IP 1: 192.168.0.134
18:11:18.172: > Using cfg path: H:\Games insalled\SteamLibrary\steamapps\common\assettocorsa\server\presets\SERVER_00\server_cfg.ini
18:11:18.173: > Car list:
18:11:18.173: > _ks_abarth500_assetto_corse_
18:11:18.174: > Client interval HZ: 18
18:11:18.174: ‽ WARNING: pitstop window needs a valid range
18:11:18.174: > AUTH_PLUGIN_ADDRESS
18:11:18.174: ‽ WARNING: Admin Password not set, admin commans disabled
18:11:18.175: > TRACK=imola
18:11:18.175: > CARS=["ks_abarth500_assetto_corse"]
18:11:18.176: > Loading PRACTICE session
18:11:18.176: > SESSION: Practice
18:11:18.176: > TYPE=PRACTICE
18:11:18.176: > TIME=50
18:11:18.177: > LAPS=0
18:11:18.177: > OPEN=1
18:11:18.177: > WAIT TIME=0
18:11:18.178: >
18:11:18.178: > DynamicTrack: first session, resetting grip
18:11:18.178: > Trying to load DRS zones from: content/tracks/imola/data/drs_zones.ini
18:11:18.179: > Loading ZONE_0 {0.901 0.116}
18:11:18.179: > Weather update. Ambient: 19.263884 Road: 25.40082 Graphics: 3_clear
18:11:18.180: > Wind update. Speed: 0 Direction: 0
18:11:18.180: > CHECKSUM: system/data/surfaces.ini=41949b9f7045cad2af3f5eb951d170a9
18:11:18.197: > CHECKSUM: content/tracks/imola/data/surfaces.ini=e1b7060d2b15a5a47d8487dcd41307e7
18:11:18.205: > CHECKSUM: content/tracks/imola/models.ini=b3919ed35facb1aa35cf1e97d4215fb8
18:11:18.205: > ACD CHECKSUM:c49c2576b0624f262120c4e9fcefb542
18:11:18.206: > Loading blacklist
18:11:18.206: > Opening entry list: H:\Games insalled\SteamLibrary\steamapps\common\assettocorsa\server\presets\SERVER_00\entry_list.ini
18:11:18.207: > Found car CAR_0
18:11:18.207: > CAR: 0 ks_abarth500_assetto_corse (0) [ []] [] Ballast: 0 kg
18:11:18.208: > CAR: 0 ks_abarth500_assetto_corse (0) [ []] [] Restrictor: 0
18:11:18.208: > open setups/ks_abarth500_assetto_corse.ini: The system cannot find the file specified.
18:11:18.209: > Found car CAR_1
18:11:18.209: > CAR: 1 ks_abarth500_assetto_corse (1) [ []] [] Ballast: 0 kg
18:11:18.209: > CAR: 1 ks_abarth500_assetto_corse (1) [ []] [] Restrictor: 0
18:11:18.210: > open setups/ks_abarth500_assetto_corse.ini: The system cannot find the file specified.
18:11:18.210: > Found car CAR_2
18:11:18.210: > CAR: 2 ks_abarth500_assetto_corse (2) [ []] [] Ballast: 0 kg
18:11:18.211: > CAR: 2 ks_abarth500_assetto_corse (2) [ []] [] Restrictor: 0
18:11:18.211: > open setups/ks_abarth500_assetto_corse.ini: The system cannot find the file specified.
18:11:18.212: > Found car CAR_3
18:11:18.212: > CAR: 3 ks_abarth500_assetto_corse (3) [ []] [] Ballast: 0 kg
18:11:18.212: > CAR: 3 ks_abarth500_assetto_corse (3) [ []] [] Restrictor: 0
18:11:18.213: > open setups/ks_abarth500_assetto_corse.ini: The system cannot find the file specified.
18:11:18.213: > Random seed: 489922610
18:11:18.213: > Starting TCP listener at port 9600
18:11:18.214: > Session has 0 laps, will not save json
18:11:18.214: > NextSession
18:11:18.214: > SESSION: Practice
18:11:18.215: > TYPE=PRACTICE
18:11:18.215: > TIME=50
18:11:18.216: > LAPS=0
18:11:18.216: > OPEN=1
18:11:18.216: > WAIT TIME=0
18:11:18.217: >
18:11:18.217: > DynamicTrack: first session, resetting grip
18:11:18.218: > Weather update. Ambient: 17.91235 Road: 23.525234 Graphics: 3_clear
18:11:18.218: > Wind update. Speed: 0 Direction: 0
18:11:18.218: > No laptime available, use car index for grids
18:11:18.219: > POS: 1, SessionID:0
18:11:18.219: > POS: 2, SessionID:1
18:11:18.219: > POS: 3, SessionID:2
18:11:18.220: > POS: 4, SessionID:3
18:11:18.220: > SENDING session name : Practice
18:11:18.221: > SENDING session index : 0
18:11:18.221: > SENDING session type : 1
18:11:18.221: > SENDING session time : 50
18:11:18.222: > SENDING session laps : 0
18:11:18.222: > Server started
18:11:18.222: > Starting HTTP server on port 8081
18:11:19.208: > Registering to AC central server
18:11:19.208: > CALLING http://93.57.10.21/lobby.ashx/regis...ixed_setup=0&timed=0&extra=0&pit=0&inverted=0
18:11:19.912: > RESPONSE: OK,0,8081
18:11:19.912: > CONNECTED TO LOBBY
18:11:19.941: > RESTARTING FROM SESSION 0
18:11:19.941: > Session has 0 laps, will not save json
18:11:19.942: > NextSession
18:11:19.942: > SESSION: Practice
18:11:19.943: > TYPE=PRACTICE
18:11:19.943: > TIME=50
18:11:19.943: > LAPS=0
18:11:19.943: > OPEN=1
18:11:19.944: > WAIT TIME=0
18:11:19.944: >
18:11:19.944: > DynamicTrack: first session, resetting grip
18:11:19.944: > Weather update. Ambient: 18.406862 Road: 24.243723 Graphics: 3_clear
18:11:19.945: > Wind update. Speed: 0 Direction: 0
18:11:19.945: > SENDING session name : Practice
18:11:19.945: > SENDING session index : 0
18:11:19.946: > SENDING session type : 1
18:11:19.946: > SENDING session time : 50
18:11:19.946: > SENDING session laps : 0
18:11:19.946: > SENDING http://93.57.10.21/lobby.ashx/ping?session=1&timeleft=3000&port=9600&clients=0&track=imola&pickup=1
18:11:20.428: > OK
18:11:34.010: > PAGE: /JSON|76561198865429863
18:11:34.013: > Serve JSON took 6 ms
18:11:46.816: > PAGE: /JSON|76561198003334669
18:11:46.860: > Serve JSON took 45 ms
18:11:49.597: > PAGE: /JSON|76561198859213169
18:11:49.614: > Serve JSON took 17 ms
18:11:50.216: > PAGE: /JSON|76561197963580870
18:11:50.225: > Serve JSON took 9 ms
18:11:53.207: > PAGE: /JSON|76561198321136499
18:11:53.233: > Serve JSON took 26 ms
18:11:53.273: > PAGE: /JSON|76561198306860351
18:11:53.284: > Serve JSON took 11 ms
18:11:56.318: > PAGE: /JSON|76561199147261333
18:11:56.343: > Serve JSON took 25 ms
18:12:00.169: > PAGE: /JSON|76561198304290747
18:12:00.218: > Serve JSON took 49 ms
18:12:01.577: > PAGE: /JSON|76561198332880262
18:12:01.595: > Serve JSON took 19 ms
18:12:04.725: > PAGE: /JSON|76561199184693261
18:12:04.756: > Serve JSON took 31 ms
18:12:06.240: > PAGE: /JSON|76561199058685435
18:12:06.285: > Serve JSON took 46 ms
18:12:12.089: > PAGE: /JSON|76561198023282885
18:12:12.097: > Serve JSON took 9 ms

Any help will be appreciated.
 
I hope someone can assist me with this.
I used to be able to run servers with absolutely no problem. I had to do a router reset (which I have done before), redid my port forwarding like before, but for some reason the server does not work.
Using AC Server manager or CM it seems to be doing the same thing. I can find the server on LAN and join my own server. But it is not visible to others, I can find my server under Kunos but only with an error reading that "cant connect to server"
Once I run the server and test the ports, it does show that the forwarding is working fine. I've searched everywhere for a solution but thus far couldn't find anything. Anyone hear that knows how to fix this? (From South Africa, and unfortunately doesn't seem like there is any AC compatible servers for rent either in my area)
Well, firstly the "JSON on loop" stuff is normal and correct. Each of those entries like "18:11:34.010: > PAGE: /JSON|76561198865429863" represents a real AC client somewhere in the world asking your server for info (not certain, but this may be the thing that the game client calls a "ping"). The log is showing that your server is hearing the request and answering it, so I'm not sure what is going wrong.

Also, I don't think I've ever managed to connect to my own local server via both LAN and the normal online option - recently it has only ever worked via LAN for me (but in years gone by I could have sworn that I was able to connect to it via the online option). So: the fact that you can't join your own server via the online option isn't a concern as such, but clearly if other people can't join it then something must indeed be wrong.

Finally, I guess that if the only thing you changed since it worked OK was the router setup, then you have probably left something out by accident. Can you list the things you put into the router?
 
Last edited:
Hi Neilski

Connection to my own online server has never really worked for me either. I generally connect via LAN. Usually my online server would at least show the info on my side, where at the moment is reads that "Internal error"
So the JSON loops is normal? (Thank you for that)

On the router after the reset, my APN was redone with assist from the ISP (In my case Afrihost). The port forwarding before the reset was set to
1. 9600 TCP and UDP
2. 8081 TCP and UDP

But I have tried various combinations, giving each its own forwarding setup as well didn't seem to make a difference either. I also tried running a static IP address but with no luck either. Could it be a Windows firewall issue perhaps? And if so what would I need to change to fix it?

1656585048641.png

 
But I have tried various combinations, giving each its own forwarding setup as well didn't seem to make a difference either. I also tried running a static IP address but with no luck either. Could it be a Windows firewall issue perhaps? And if so what would I need to change to fix it?
Not really sure what can be wrong...
The Windows Firewall might be playing a role but if you didn't make changes to its settings (or reset them) then this seems a little unlikely. The nuclear option there would be to completely disable it (briefly!) and see if anything changes.
I don't personally have AC port forwarding set up right now on my current router and am unable to remember the precise details of what I needed to do last time around but hopefully someone else can lend a hand to confirm settings.
 
Back
Top