Few questions about this awesome repo

[cryptopool-builders]

First off thanks for taking the time to code this.
I wrote an automated installer for another popular script and came up with the idea today to add a console section to that scripts admin area since the admins have to do a lot of work both on the web and in ssh.

I was wondering if though, not all users of the script would actually be using domain names and it just gets setup to use the server IP with a self generated cert. And then the others would be domain based with a letsencrypt cert.

Is it possible to use this script with just server ip and self generated cert? Also is there a way to keep the connection persistent, so that if they start a task in the console, move to another page on the site and then come back to the console its the same session? Ill gladly donate some coffee money to help get this going in the project I am wanting to use it for.

[cryptopool-builders]

So couple of issues when trying this out I get the following errors:
https://pastebin.com/VpSWHFEi

when running wsproxy it starts on...

[Status]: Starting wsProxy on port 5999...

when i try to
sudo wsproxy -s -k /etc/letsencrypt/live/thepool.life/privkey.pem -c /etc/letsencrypt/live/thepool.life/chain.pem

i get an error of

sudo: wsproxy: command not found

[stuicey]

Not sure I entirely understand the scenario you've laid out but can get the general gist of it.

The wrapper version of this seems to be what you'd want to use - you can set the SSH connection details inside the HTML delivered to your users. I know some users have tokenised the connection details and deliver the page with user specific connection details on the fly.

The client is a normal SSH client so it would act the same way as any other client - e.g. PUTTY. So you'd need additional setup to make the session persistent. For example if you had TMUX/Screen installed on your server you could force SSHy to passthrough the command to join one of those
persistent sessions.

wsproxy won't be in root's environment path so if you need to execute it under root - you'd have to use the full path. Its bad practice to run services under root so I'm not sure why you'd want to do it like this.