Website problems

[nwj38]

#I launch the Velocity website, like normal. I use it, like normal, and it works just fine.

After a certain amount of time, though (might be around 30-60 minutes), the website stops working, and when I try to reload it, it shows an error message.

Weirdly, going back into the repository terminal and entering "./launch.sh" again, going back to the non-functional site, and reloading it seems to make it work again. I've been going back into the terminal to launch the site again several times since this seems to work repeatedly.
Does anyone know why this happens? Is there any way to keep the site functioning permanently?
(I'm basically clueless on this computer language stuff)

[CrossScarDev]

You have to keep the codespace open. GitHub automatically closes them if you don't keep editing or inputting in them, so you might have to go back to that tab and open a file or something every once in a while.

[nwj38]

So... What you mean to say, is that the website stops working after a certain period of time because the codespace gets closed by GitHub, and every time I go into the terminal and type in ./launch.sh, it re-opens the codespace? And this is the only way to keep the site working?

[CrossScarDev]

Wait, is there a message above where you type in ./launch.sh? If so, please paste it in here.

[nwj38]

Above the ./launch.sh prompt, after I use ./install.sh? Aside from the installation messages, I don't think there's anything to note.

Now that I think about it, the only message that tends to appear after ./launch.sh is "Client decided to terminate with reason 1".

[CrossScarDev]

That seems to be a common issue with Velocity, as it has been reported in other issues. I'm pretty sure it's an issue with Velocity.

[nwj38]

Is it, though? If it was specifically Velocity causing the issue, wouldn't it show me an internal server error inside of the Velocity UI instead of making the entire site unresponsive?

If it is indeed an issue with Velocity, am I able to report it to a Velocity repository?

[CrossScarDev]

It is probably an issue with velocity because velocity is written in JS with node and that is a node based error. If you are uncertain, you can also try running Velocity directly by running:

cd Velocity
npm start

in the terminal.