github-starred/cobalt
2
0
Fork 0
mirror of https://github.com/imputnet/cobalt.git synced 2026-07-30 15:14:55 -05:00
Code Issues 4.8k Packages Projects Releases Wiki Activity

Node Start Failed #329

New Issue
Closed
opened 2025-11-09 09:46:26 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-09 09:46:26 -06:00
Owner
Copy Link
Copy Source

Originally created by @Gareryer on GitHub (Jun 29, 2024).

cobalt@usr:~/htdocs/cobalt.website.com$ npm start

> cobalt@7.14.5 start
> node src/cobalt

fatal: not a git repository (or any of the parent directories): .git
node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: git rev-parse --short HEAD
fatal: not a git repository (or any of the parent directories): .git

    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:889:11)
    at execSync (node:child_process:961:15)
    at shortCommit (file:///home/cobalt/htdocs/cobalt.website.com/src/modules/sub/currentCommit.js:7:13)
    at file:///home/cobalt/htdocs/cobalt.website.com/src/cobalt.js:16:19
    at ModuleJob.run (node:internal/modules/esm/module_job:262:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:474:24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:109:5) {
  status: 128,
  signal: null,
  output: [
    null,
    Buffer(0) [Uint8Array] [],
    Buffer(69) [Uint8Array] [
      102,  97, 116,  97, 108,  58,  32, 110, 111, 116,  32,
       97,  32, 103, 105, 116,  32, 114, 101, 112, 111, 115,
      105, 116, 111, 114, 121,  32,  40, 111, 114,  32,  97,
      110, 121,  32, 111, 102,  32, 116, 104, 101,  32, 112,
       97, 114, 101, 110, 116,  32, 100, 105, 114, 101,  99,
      116, 111, 114, 105, 101, 115,  41,  58,  32,  46, 103,
      105, 116,  10
    ]
  ],
  pid: 2773,
  stdout: Buffer(0) [Uint8Array] [],
  stderr: Buffer(69) [Uint8Array] [
    102,  97, 116,  97, 108,  58,  32, 110, 111, 116,  32,
     97,  32, 103, 105, 116,  32, 114, 101, 112, 111, 115,
    105, 116, 111, 114, 121,  32,  40, 111, 114,  32,  97,
    110, 121,  32, 111, 102,  32, 116, 104, 101,  32, 112,
     97, 114, 101, 110, 116,  32, 100, 105, 114, 101,  99,
    116, 111, 114, 105, 101, 115,  41,  58,  32,  46, 103,
    105, 116,  10
  ]
}

Node.js v22.3.0

I'm deploying on vps through Node 22 LTS

Originally created by @Gareryer on GitHub (Jun 29, 2024). ``` cobalt@usr:~/htdocs/cobalt.website.com$ npm start > cobalt@7.14.5 start > node src/cobalt fatal: not a git repository (or any of the parent directories): .git node:internal/errors:983 const err = new Error(message); ^ Error: Command failed: git rev-parse --short HEAD fatal: not a git repository (or any of the parent directories): .git at genericNodeError (node:internal/errors:983:15) at wrappedFn (node:internal/errors:537:14) at checkExecSyncError (node:child_process:889:11) at execSync (node:child_process:961:15) at shortCommit (file:///home/cobalt/htdocs/cobalt.website.com/src/modules/sub/currentCommit.js:7:13) at file:///home/cobalt/htdocs/cobalt.website.com/src/cobalt.js:16:19 at ModuleJob.run (node:internal/modules/esm/module_job:262:25) at async ModuleLoader.import (node:internal/modules/esm/loader:474:24) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:109:5) { status: 128, signal: null, output: [ null, Buffer(0) [Uint8Array] [], Buffer(69) [Uint8Array] [ 102, 97, 116, 97, 108, 58, 32, 110, 111, 116, 32, 97, 32, 103, 105, 116, 32, 114, 101, 112, 111, 115, 105, 116, 111, 114, 121, 32, 40, 111, 114, 32, 97, 110, 121, 32, 111, 102, 32, 116, 104, 101, 32, 112, 97, 114, 101, 110, 116, 32, 100, 105, 114, 101, 99, 116, 111, 114, 105, 101, 115, 41, 58, 32, 46, 103, 105, 116, 10 ] ], pid: 2773, stdout: Buffer(0) [Uint8Array] [], stderr: Buffer(69) [Uint8Array] [ 102, 97, 116, 97, 108, 58, 32, 110, 111, 116, 32, 97, 32, 103, 105, 116, 32, 114, 101, 112, 111, 115, 105, 116, 111, 114, 121, 32, 40, 111, 114, 32, 97, 110, 121, 32, 111, 102, 32, 116, 104, 101, 32, 112, 97, 114, 101, 110, 116, 32, 100, 105, 114, 101, 99, 116, 111, 114, 105, 101, 115, 41, 58, 32, 46, 103, 105, 116, 10 ] } Node.js v22.3.0 ``` I'm deploying on vps through Node 22 LTS
GiteaMirror added the instance hosting help label 2025-11-09 09:46:26 -06:00
GiteaMirror commented 2025-11-09 09:46:27 -06:00
Author
Owner
Copy Link
Copy Source

@wukko commented on GitHub (Jun 29, 2024):

as error implies, you need the .git folder & git installed.

clone the repo as tutorial says to do, or use a docker image!

@wukko commented on GitHub (Jun 29, 2024): as error implies, you need the .git folder & git installed. clone the repo [as tutorial says to do](https://github.com/imputnet/cobalt/blob/current/docs/run-an-instance.md#:~:text=clone%20the%20repo%3A%20git%20clone%20https%3A//github.com/imputnet/cobalt), or use a docker image!
GiteaMirror commented 2025-11-09 09:46:27 -06:00
Author
Owner
Copy Link
Copy Source

@Gareryer commented on GitHub (Jun 29, 2024):

as error implies, you need the .git folder & git installed.

clone the repo as tutorial says to do, or use a docker image!

This is the exact guide I followed & I think the folder is present
Screenshot 2024-06-29 at 13-51-53 CloudPanel File Manager

@Gareryer commented on GitHub (Jun 29, 2024): > as error implies, you need the .git folder & git installed. > > clone the repo [as tutorial says to do](https://github.com/imputnet/cobalt/blob/current/docs/run-an-instance.md#:~:text=clone%20the%20repo%3A%20git%20clone%20https%3A//github.com/imputnet/cobalt), or use a docker image! This is the exact guide I followed & I think the folder is present ![Screenshot 2024-06-29 at 13-51-53 CloudPanel File Manager](https://github.com/imputnet/cobalt/assets/126243956/6d01076b-4440-4a21-b118-8bf6665a1a18)
GiteaMirror commented 2025-11-09 09:46:27 -06:00
Author
Owner
Copy Link
Copy Source

@wukko commented on GitHub (Jun 29, 2024):

it's not, there's no .git folder

@wukko commented on GitHub (Jun 29, 2024): it's not, there's no `.git` folder
GiteaMirror commented 2025-11-09 09:46:28 -06:00
Author
Owner
Copy Link
Copy Source

@wukko commented on GitHub (Jun 29, 2024):

consider using the docker image instead, it's easier to setup and will update itself.

@wukko commented on GitHub (Jun 29, 2024): consider using the docker image instead, it's easier to setup and will update itself.
GiteaMirror commented 2025-11-09 09:46:28 -06:00
Author
Owner
Copy Link
Copy Source

@Gareryer commented on GitHub (Jun 29, 2024):

consider using the docker image instead, it's easier to setup and will update itself.

Alright, I will do that now

@Gareryer commented on GitHub (Jun 29, 2024): > consider using the docker image instead, it's easier to setup and will update itself. Alright, I will do that now
GiteaMirror commented 2025-11-09 09:46:28 -06:00
Author
Owner
Copy Link
Copy Source

@ihatespawn commented on GitHub (Jun 30, 2024):

consider using the docker image instead, it's easier to setup and will update itself.

Alright, I will do that now

did you do it? if yes, did it work?

@ihatespawn commented on GitHub (Jun 30, 2024): > > consider using the docker image instead, it's easier to setup and will update itself. > > Alright, I will do that now did you do it? if yes, did it work?
GiteaMirror commented 2025-11-09 09:46:28 -06:00
Author
Owner
Copy Link
Copy Source

@Gareryer commented on GitHub (Jul 1, 2024):

consider using the docker image instead, it's easier to setup and will update itself.

Alright, I will do that now

did you do it? if yes, did it work?

No, the docker method didn't work. I just wish the NodeJs can run successfully with 'npm start'

@Gareryer commented on GitHub (Jul 1, 2024): > > > consider using the docker image instead, it's easier to setup and will update itself. > > > > > > Alright, I will do that now > > did you do it? if yes, did it work? No, the docker method didn't work. I just wish the NodeJs can run successfully with 'npm start'
GiteaMirror commented 2025-11-09 09:46:29 -06:00
Author
Owner
Copy Link
Copy Source

@ihatespawn commented on GitHub (Jul 1, 2024):

consider using the docker image instead, it's easier to setup and will update itself.

Alright, I will do that now

did you do it? if yes, did it work?

No, the docker method didn't work. I just wish the NodeJs can run successfully with 'npm start'

did you get any errors when using the docker method?
it works very good for me

@ihatespawn commented on GitHub (Jul 1, 2024): > > > > consider using the docker image instead, it's easier to setup and will update itself. > > > > > > > > > Alright, I will do that now > > > > > > did you do it? if yes, did it work? > > No, the docker method didn't work. I just wish the NodeJs can run successfully with 'npm start' did you get any errors when using the docker method? it works very good for me
GiteaMirror commented 2025-11-09 09:46:29 -06:00
Author
Owner
Copy Link
Copy Source

@Gareryer commented on GitHub (Jul 1, 2024):

consider using the docker image instead, it's easier to setup and will update itself.

Alright, I will do that now

did you do it? if yes, did it work?

No, the docker method didn't work. I just wish the NodeJs can run successfully with 'npm start'

did you get any errors when using the docker method? it works very good for me

docker installation was successful but to bind it with domain that's where am having issue. I'm getting SSL handshake error

@Gareryer commented on GitHub (Jul 1, 2024): > > > > > consider using the docker image instead, it's easier to setup and will update itself. > > > > > > > > > > > > Alright, I will do that now > > > > > > > > > did you do it? if yes, did it work? > > > > > > No, the docker method didn't work. I just wish the NodeJs can run successfully with 'npm start' > > did you get any errors when using the docker method? it works very good for me docker installation was successful but to bind it with domain that's where am having issue. I'm getting SSL handshake error
GiteaMirror commented 2025-11-09 09:46:29 -06:00
Author
Owner
Copy Link
Copy Source

@wukko commented on GitHub (Jul 20, 2024):

I'm getting SSL handshake error

if you're using cloudflare, you must follow their instructions to configure SSL on your server. this is not related to cobalt.

@wukko commented on GitHub (Jul 20, 2024): > I'm getting SSL handshake error if you're using cloudflare, you must follow their instructions to configure SSL on your server. this is not related to cobalt.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
3rd party app support
bug
can reproduce
can't reproduce
documentation
duplicate
feature request
help wanted
instance hosting help
invalid
main instance issue
need more info
needs fixing
next major
not an issue
pull-request
Mirrored from GitHub Pull Request
 question
region lock issue
security
service request
skill issue
web ui
No labels instance hosting help
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cobalt#329