#Node.js exiting (exit code 0)

1 messages · Page 1 of 1 (latest)

slender crystal
#

05:13:18 AM [ STDERR] Fatal Error: Node.js exiting (exit code 0)
05:13:18 AM [ STDERR] See console for details↩
05:13:18 AM mSee console for details

elfin fiberBOT
slender crystal
#

Back at it again

slender crystal
#

I know you may not like this but I keep getting overlooked and I would like some guidance @crisp prawn

elfin fiberBOT
crisp prawn
slender crystal
slender crystal
#

Here it is sir @crisp prawn

#

Whenever you can no rush

crisp prawn
elfin fiberBOT
#

@slender crystal
The issue you are having is likely caused by some resource.
:point_right: Steps you can take to troubleshoot and pinpoint the cause:
:one: First check your txAdmin > Live Console and look for errors;
:two: On the CFG Editor and try disabling all resources one-by-one (or in groups) until it starts working again;
:three: Try updating your txAdmin/FXServer;
:four: Go to txAdmin > Settings > FXServer and try different OneSync Options.
:five: Go to txAdmin > Settings > FXServer and take note of the two paths, then go to txAdmin > System > Master Actions > Reset FXServer and deploy a new server with the CFX Default recipe. If it works then that will confirm that the issue is related to a resource. Now you can go to the settings and restore the paths to go back to your previous server before the reset.

slender crystal
#

No errors on the console , and Ive upadated to latest, iIve set up a servber all over again to try to find out whats going on

slender crystal
crisp prawn
slender crystal
crisp prawn
#

i know

slender crystal
#

But I will talk to them for more support

#

This wasnt showing