Cirkus Serveri Forum
    • CoD4xAdmin
    • Recent
    • Popular
    • Groups
    • Users
    • Register
    • Login

    Error: Init failure. Server returned code 400 and message Error: Empty rcon value

    Scheduled Pinned Locked Moved
    Support
    4
    31
    2.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Beni
      last edited by

      The password from Database is same like from config.json

      https://prnt.sc/119l6vx

      1 Reply Last reply Reply Quote 0
      • B
        Beni
        last edited by

        I make know database in plesk
        https://prnt.sc/119l7po

        1 Reply Last reply Reply Quote 0
        • NeHoN
          NeHo Administrators
          last edited by

          Plesk has a plugin for node js applications, you have to set there the root and else, I don't remember what I had to change but in order to run node applications you need to tweak plesk.

          Check this https://www.youtube.com/watch?v=36I_YZZaMPs

          I keep hitting the 'Escape' key - but I'm still here. ...

          1 Reply Last reply Reply Quote 0
          • B
            Beni
            last edited by

            Hello neho pls help
            That’s what write me plesk
            What I need now to do ?

            Hello,

            The application fails with the following error, the module ../server couldn't be found:
            ==> /var/log/apache2/error.log <==
            App 4797 output: module.js:550
            App 4797 output: throw err;
            App 4797 output: ^
            App 4797 output:
            App 4797 output: Error: Cannot find module '../server'
            App 4797 output: at Function.Module._resolveFilename (module.js:548:15)
            App 4797 output: at Function.Module._load (module.js:475:25)
            App 4797 output: at Module.require (module.js:597:17)
            App 4797 output: at Module.require (/usr/share/passenger/helper-scripts/node-loader.js:80:25)
            App 4797 output: at require (internal/module.js:11:18)
            App 4797 output: at Object.<anonymous> (/var/www/vhosts/unlucky-gaming.co/www:7:14)
            App 4797 output: at Module._compile (module.js:653:30)
            App 4797 output: at Object.Module._extensions..js (module.js:664:10)
            App 4797 output: at Module.load (module.js:566:32)
            App 4797 output: at tryModuleLoad (module.js:506:12)
            [ E 2021-04-12 20:58:18.2114 31768/T2p age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/www/vhosts/unlucky-gaming.co/: The application process exited prematurely.
            Error ID: 69014f85
            Error details saved to: /tmp/passenger-error-HyXwQN.html

            [ E 2021-04-12 20:58:18.2225 31768/Tk age/Cor/Con/CheckoutSession.cpp:276 ]: [Client 7-2] Cannot checkout session because a spawning error occurred. The identifier of the error is 69014f85. Please see earlier logs for details about the error.

            ==> /var/www/vhosts/unlucky-gaming.co/logs/webadmin.unlucky-gaming.co/error_log <==
            [Mon Apr 12 20:58:18.399112 2021] [core:error] [pid 31800] [client 195.214.233.10:47218] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: https://webadmin.unlucky-gaming.co/
            [Mon Apr 12 20:58:18.399149 2021] [core:error] [pid 31800] [client 195.214.233.10:47218] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: https://webadmin.unlucky-gaming.co/

            The current configuration is invalid:

            These are the files in the node project:

            ​

            I've fixed the configuration as follows:

            The log files are showing issues with your node application:

            ==> /var/log/apache2/error.log <==
            [ E 2021-04-12 21:04:28.1583 8809/Tr age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co: A timeout occurred while spawning an application process.
            Error ID: 9bd06fba
            Error details saved to: /tmp/passenger-error-ENHg9r.html
            [ E 2021-04-12 21:04:28.1681 8809/T8 age/Cor/Con/CheckoutSession.cpp:276 ]: [Client 1-1] Cannot checkout session because a spawning error occurred. The identifier of the error is 9bd06fba. Please see earlier logs for details about the error.
            App 12091 output: Trace: You required the Node Cluster module, which is incompatible with Passenger, a non-functional shim was returned and your app may still work. However, please remove the related code as soon as possible.
            App 12091 output: at Module.require (/usr/share/passenger/helper-scripts/node-loader.js:63:12)
            App 12091 output: at require (internal/module.js:11:18)
            App 12091 output: at Object.<anonymous> (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/shortid/lib/util/cluster-worker-id.js:3:15)
            App 12091 output: at Module._compile (module.js:653:30)
            App 12091 output: at Object.Module._extensions..js (module.js:664:10)
            App 12091 output: at Module.load (module.js:566:32)
            App 12091 output: at tryModuleLoad (module.js:506:12)
            App 12091 output: at Function.Module._load (module.js:498:3)
            App 12091 output: at Module.require (module.js:597:17)
            App 12091 output: at Module.require (/usr/share/passenger/helper-scripts/node-loader.js:80:25)
            App 12091 output: at require (internal/module.js:11:18)
            App 12091 output: at Object.<anonymous> (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/shortid/lib/index.js:11:23)
            App 12091 output: at Module._compile (module.js:653:30)
            App 12091 output: at Object.Module._extensions..js (module.js:664:10)
            App 12091 output: at Module.load (module.js:566:32)
            App 12091 output: at tryModuleLoad (module.js:506:12)
            App 12091 output: at Function.Module._load (module.js:498:3)
            App 12091 output: at Module.require (module.js:597:17)
            App 12091 output: at Module.require (/usr/share/passenger/helper-scripts/node-loader.js:80:25)
            App 12091 output: at require (internal/module.js:11:18)
            App 12091 output: at Object.<anonymous> (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/shortid/index.js:2:18)
            App 12091 output: at Module._compile (module.js:653:30)
            App 12091 output: Your mongoDB Username, Password is wrong in file app/config/config.json . Could not connect to database! MongooseServerSelectionError: connection <monitor> to 127.0.0.1:3306 closed
            App 12091 output: Unhandled rejection MongooseServerSelectionError: connection <monitor> to 127.0.0.1:3306 closed
            App 12091 output: at NativeConnection.Connection.openUri (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/mongoose/lib/connection.js:845:32)
            App 12091 output: at _mongoose._promiseOrCallback.cb (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/mongoose/lib/index.js:345:10)
            App 12091 output: at Promise (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/mongoose/lib/helpers/promiseOrCallback.js:31:5)
            App 12091 output: at Promise._execute (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/bluebird/js/release/debuggability.js:384:9)
            App 12091 output: at Promise._resolveFromExecutor (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/bluebird/js/release/promise.js:518:18)
            App 12091 output: at new Promise (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/bluebird/js/release/promise.js:103:10)
            App 12091 output: at promiseOrCallback (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/mongoose/lib/helpers/promiseOrCallback.js:30:10)
            App 12091 output: at Mongoose._promiseOrCallback (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/mongoose/lib/index.js:1135:10)
            App 12091 output: at Mongoose.connect (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/node_modules/mongoose/lib/index.js:344:20)
            App 12091 output: at Object.<anonymous> (/var/www/vhosts/unlucky-gaming.co/webadmin.unlucky-gaming.co/server.js:37:10)
            App 12091 output: at Module._compile (module.js:653:30)
            App 12091 output: at Object.Module._extensions..js (module.js:664:10)
            App 12091 output: at Module.load (module.js:566:32)
            App 12091 output: at tryModuleLoad (module.js:506:12)
            App 12091 output: at Function.Module._load (module.js:498:3)
            App 12091 output: at Module.require (module.js:597:17)
            App 12091 output: at Module.require (/usr/share/passenger/helper-scripts/node-loader.js:80:25)
            App 12091 output: at require (internal/module.js:11:18)
            App 12091 output: at loadApplication (/usr/share/passenger/helper-scripts/node-loader.js:243:2)
            App 12091 output: at setupEnvironment (/usr/share/passenger/helper-scripts/node-loader.js:214:2)
            App 12091 output: at Object.<anonymous> (/usr/share/passenger/helper-scripts/node-loader.js:133:1)

            Note this investigation is a coding issue related to the application itself and it will need to be handled from your side.

            1 Reply Last reply Reply Quote 0
            • NeHoN
              NeHo Administrators
              last edited by

              Can you start the application with npm start from application root, there was another person who also used plesk and they told him the same, its always application issue.

              So for start lets ignore plesk and start the application manually via putty, if in that case there is an error let me know so that I can start from there and help you out.

              I can not give you support for plesk since I don't use it, but if you cant run the application manually I will help you out with that.

              So start the application with npm start, if it runs visit your_ip:3000 and check if you can see the app runing

              I keep hitting the 'Escape' key - but I'm still here. ...

              1 Reply Last reply Reply Quote 0
              • B
                Beni
                last edited by

                How i can start npm in root?

                NeHoN 1 Reply Last reply Reply Quote 0
                • NeHoN
                  NeHo Administrators @Beni
                  last edited by

                  @beni navigate to application root

                  cd /var/www/vhosts/webadmin.unlucky-gaming.co
                  

                  Start the application

                  npm start
                  

                  I keep hitting the 'Escape' key - but I'm still here. ...

                  1 Reply Last reply Reply Quote 0
                  • B
                    Beni
                    last edited by

                    In plesk i stop npm like u say, then i start the command npm start and now is this problem https://prnt.sc/11g5kov
                    in putty i get this one problem too https://prnt.sc/11g5quu

                    1 Reply Last reply Reply Quote 0
                    • NeHoN
                      NeHo Administrators
                      last edited by

                      Port 3000 is already in use, that means that you already run my application, probably Plesk auto restarts. Make sure you stop the application in Plesk and then run it without plesk

                      I keep hitting the 'Escape' key - but I'm still here. ...

                      1 Reply Last reply Reply Quote 0
                      • B
                        Beni
                        last edited by

                        But on plesk node is off https://prnt.sc/11gikpl

                        1 Reply Last reply Reply Quote 0
                        • B
                          Beni
                          last edited by

                          What can i do 😞

                          1 Reply Last reply Reply Quote 0
                          • B
                            Beni
                            last edited by

                            https://prnt.sc/11j026g

                            @Neho i have problem with Mongo pls help

                            1 Reply Last reply Reply Quote 0
                            • SMiLeYS
                              SMiLeY
                              last edited by

                              config.json database information is wrong. Check it; double check it, then edit if need be and try again.

                              1 Reply Last reply Reply Quote 0
                              • B
                                Beni
                                last edited by

                                @Smiley

                                root@vps-2afb9ed9:~# mongo
                                MongoDB shell version: 3.2.11
                                connecting to: test
                                2021-04-16T18:54:43.849+0200 E QUERY [thread1] Error: network error while attempting to run command 'whatsmyuri' on host '127.0.0.1:27017' :
                                connect@src/mongo/shell/mongo.js:229:14

                                1 Reply Last reply Reply Quote 0
                                • B
                                  Beni
                                  last edited by

                                  @Neho @Smiley

                                  How i can make new database and new mongodb?

                                  https://prnt.sc/11j2ete

                                  Thats what Plesk supporter says me

                                  MongoDB shell version: 3.2.11
                                  connecting to: test
                                  2021-04-16T18:54:43.849+0200 E QUERY [thread1] Error: network error while attempting to run command 'whatsmyuri' on host '127.0.0.1:27017' :
                                  connect@src/mongo/shell/mongo.js:229:14

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    Beni
                                    last edited by

                                    @Neho
                                    You write me:
                                    Port 3000 is already in use, that means that you already run my application, probably Plesk auto restarts. Make sure you stop the application in Plesk and then run it without plesk.

                                    Thats was true antivirus was on port 3000.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post

                                    1

                                    Online

                                    191

                                    Users

                                    268

                                    Topics

                                    1.2k

                                    Posts
                                    Powered & Designed by NeHo