2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello.
Did you copy any files before modifying /etc/ssh/sshd_config?
If you have done so, I think you should write a startup script to restore the configuration file from the copy and restart sshd.
If you do not have a copy left, try running a startup script that edits the configuration file using a command such as "sed" to restore the configuration file to its original state.
0
Have you considered making a snapshot of the instance, and then converting that into an EBS volume so that you can attach to another instance? This would let you view and edit the files, or clone them onto the new instance.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for the response! Unfortunately, I just tried this variation on my grep method, and still no go.
Am I formatting the launch script correctly? I simply add my 1 line commands to the launch script dialog box when creating a new instance from a snapshot in the Lightsail browser portal. Does it need the bash shebang at the top? Should I use sudo for the command?
I am willing to settle with simply accessing the files for copying purposes now, as I've created a new fresh instance and begun to migrate over: What options do I have to simply access the files if ssh is down on the system? < ---- any insight into this MUCH APPRECIATED! Thanks!
Hi again! Any follow up? Is there a way I can mount the snapshot/back-up I made of the instance so I can copy out the files I need? Thanks!