Linux Server 1141 crashing randomly. Linux Server 1317 crashing on startup

FiveM Client Support
4

Having the EXACT same issue:

terminating with uncaught exception of type Botan::Invalid_Argument: base64_decode: invalid base64 character '$'

after that, a SIGABRT error.

5

I would suggest you attempt to upgrade your server to the latest artifacts

6

Well i had the exact same issue 10 minutes ago i’ll try what you said

7

:popcorn:

8

Working solution ? i have this same problem … but this last version server artifacts working ?

9

yes PSA: update your server to pipeline ID 1313 or above

10

k Thx,
I already thought that some cheater with injector would not pretend to do something
facePalm

11

1317 Crashes during startup:

Stacktrace:

/proc/self/maps:
402f7000-40307000 rwxp 00000000 00:00 0 
41a68000-41af8000 rwxp 00000000 00:00 0 
41dab000-41e8b000 rwxp 00000000 00:00 0 
24ee7d80000-24ee7e00000 rw-p 00000000 00:00 0 
f137b780000-f137b800000 rw-p 00000000 00:00 0 
f20ad838000-f20ad840000 rw-p 00000000 00:00 0 
f707d980000-f707da00000 rw-p 00000000 00:00 0 
10d942085000-10d942100000 ---p 00000000 00:00 0 
10d942100000-10d942103000 rw-p 00000000 00:00 0 
10d942103000-10d942104000 ---p 00000000 00:00 0 
10d942104000-10d94217f000 r-xp 00000000 00:00 0 
10d94217f000-10d942180000 ---p 00000000 00:00 0 
10d942180000-10d942183000 rw-p 00000000 00:00 0 
10d942183000-10d942184000 ---p 00000000 00:00 0 
10d942184000-10d9421ff000 r-xp 00000000 00:00 0 
10d9421ff000-10d94a085000 ---p 00000000 00:00 0 
1c39d8400000-1c39d8480000 rw-p 00000000 00:00 0 
1e423fc80000-1e423fc83000 rw-p 00000000 00:00 0 
1e423fc83000-1e423fd00000 r--p 00000000 00:00 0 
24117be80000-24117bf00000 rw-p 00000000 00:00 0 
243500900000-243500980000 rw-p 00000000 00:00 0 
2e7baf880000-2e7baf8af000 rw-p 00000000 00:00 0 
30a135700000-30a13580a000 rw-p 00000000 00:00 0 
3370a6700000-3370a6780000 rw-p 00000000 00:00 0 
375d7fe80000-375d7fe83000 rw-p 00000000 00:00 0 

Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
Unhandled exception in Mono script environment: System.NullReferenceException: Object reference not set to an instance of an object
(null)web2@server:~/fivem/main/server-data$
12

this same problem

image
image980×488 11.1 KB

13

Same here.

What build is last known to be stable?

14

same here (zap-hosting)

15

Also here

16

just finished updating my server with more resources. though it was zaphosting down or my bad resources. so what should we do now?

17

For now we just have to find a reliable Server Build.

18

Same problem here !
I think we have to wait !
most of servers are down

19

Same here. Just started the server for a minute then crashed again. Now, im trying to update the artifact first. See if this the solution or not.

20

please let me know when u finish

21

im on zaphosting. should i update the server manually?

22

It looks like the problem is fixed!
Try to start your servers again and give me a feedback…

23

Ladies and gents, as an update: If you are caught up in the whirlwind of servercrashes and you updated the artifacts to find that you now get a crash on startup, look through your server terminal and find the last resource to load before the crash. In your server.cfg, comment out the resource right below the last successfully loaded resource and try starting again. Rinse and repeat until you’ve weeded out the resources incompatible with the latest artifacts build. The unofficial ESX discord has had reports of vehicles, tabby and other resources causing issues with startup on the latest build. Our personal issue with the latest build was a vehicle. Server is now running without any issues.