Hello,
Browser : Firefox 85, with No-Script add-on Local system : like-Debian Linux Droplet : Debian
Hello, i am new here,
I can access droplet through the terminal and SSH, no problem. However, I want that installed program to perform its action. And when I close the terminal, the action stops.
So I go to the DigitalOcean panel, “access console” and open a new window.
Do I always have to reset the root password at the beginning?
To find a solution, I had turned off No-Script completely, but it did not help.
Thanks in advance for suggestions
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there, @sobeit2020
I will also recommend you not to use the DigitalOcean console for anything else than re-gaining access to your droplet. The Copy/Paste functionality of our web console is a bit odd; the code backing it is custom due to the way the VNC window is implemented for accessing your Droplet. It isn’t a good idea, in my experience, to rely on the console for long copy/pasting like an SSH key.
I will also suggest using screen in order to keep the process running after closing the ssh session.
Hope that this helps! Regards, Alex
Nice, thanks for answers, i will definitely try them out, that sounds very clear/
but firts, after tornado changes from the weekend, i have other problem, @ https://www.digitalocean.com/community/questions/regaining-access-to-droplet-thorugh-ssh-after-original-ssh-directory-is-gone @alexdo @bobbyiliev @KFSys
Hi @sobeit2020,
First, let’s talk about the Copy and Paste option. This is a known let’s say feature. Usually, when someone wants to Copy and Paste, we urge them to us SSH rather than the WebConsole. The WebConsole is more for a last resort resource when everything else is not working. So wouldn’t advive you to use it the way you intend to.
Now, you mentioned you have a command you want to run but when you exit your SSH session it stops. There are a few ways you can bypass this, the first one is to use SCREEN. The screen commands, create a new screen in your SSH session which you can detach from and leave the command running inside it.
Usually, it can be done the following way:
screen -S NameOfScreen
It won’t visibly change but you’ll be in. In there run the command you need to run and once you are done do CTRL + A, CTRL +D. This will detach you from the screen seession and return you to your normal shell. The command will keep running. To return to that screen session, you can do
screen -list
See the name of the ScreenSesion and then use;
screen -r NameOfScreen
and that’s it.
Now there are more smart ways to do what you intend like using the service supervisord and stuff like that but it will require some knowledge to use it.
Regards, KFSys
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.