Navigating the terminal

I think this is a really simple question… I’m trying to follow workshop 24 where @vasileios demonstrates building a full server. I’m not even sure I need to do this… I just want to host my own website which is due to renew on Wix on May 20, so I’m trying to hurry!

When I open my terminal it says this:

That is from whatever last thing I was following (I just follow along even though I don’t understand any of it)
I don’t remember how to get out of whatever that is. The SSH which I set up before doesn’t seem to be working from there.

Thank you for any help! I googled commands, but I didn’t get anywhere.

Hey @Jen!
The thing with Wix is that they use a proprietary editor, which can’t be transferred into any other platform, unfortunately. Several of us, myself included, had to redesign our website to work with Wordpress.
When you open up your terminal, you are situated on your local computer. If you wish to create a Wordpress server (that also includes email, FTP, DNS), then you will need to rent a VPS (Virtual Private Server) from a respective provider. The one I’m using is Linode.

Also, in course 24, you will find a detailed PDF on how to do that. It’s on the top right of your screen, under Files.

1 Like

Oh yes, yes. Thank you @vasileios I do know all that (clearly I’m learning stuff - amazing)! Transfer was the wrong word. I’m going to redesign it. I even bought a new (better for me) domain from namecheap. I have the VPS from linode done and the SSH. I bought email from Rob Braxman and am using Thunderbird. I even have wordpress installed (I think).

The problem is, when I try to follow along on your tutorial, my terminal has that Vosto thing. I have no idea what that is or how to get out of it! Can you get me from there?

When your Vostro appears, that means you’re on the local system. To head to your VPS, you will need to SSH to it. After you install CyberPanel, however, it will drop a large text with all the credentials and web addresses you will need. Just remember the Admin password you set for it. After that point, everything is controlled via a web interface. :slight_smile:

If you still feel stuck, please let me know which part of the process you’re having trouble with.

@Jen are you using a vostro 7590 computer, by any chance? That looks like my command prompts “dave@TouchScreenNotebook”, I changed the name from hp-xx-17 blah, blah, blah to TouchScreenNotebook. Just my $.02. Cheers!!

@vasileios I assumed I was doing something wrong because the SSH wouldn’t accept my password. I seem to recall following an earlier workshop that maybe had us set it up with no password? But I might be remembering that wrong. I was assuming I was missing a step that I needed before the SSH, but maybe that’s not the problem.

Hi @BigDaveAZ I have no idea! It’s a dell and it used to have windows :woman_shrugging:t4: :laughing:

@Jen I just looked it up your computer is a Dell Vostro 7590. The name was given at setup and was prefilled with the manufacturer’s name for your computer is. to change the computer name open a terminal and run
sudo nano /etc/hostname
enter your sudo password
change the name to whatever you would like it to be, save, and exit
you will be able to see the new computer name at the prompt.
I hope this helps. Cheers!!

Thanks @BigDaveAZ :grin: sounds neat ; I will try that tomorrow! The main problem is the SSH not working from there though.

1 Like

Hey @Jen!
I suppose you have created SSH keys to login to your VPS. If you set a passphrase, then the password you will need is the one you set for your key. Also, login via your non-root user that way. :slight_smile:

1 Like

Hi @vasileios do you happen to remember which workshop was a video by someone else telling us the steps to not have a password for … it was either root or ssh or both. I followed along with that. I’ll try to skim though and see if I can find which one that was. I’m afraid I followed along with something that got rid of a password because none of the ones I have are working for SSH now. They did before.

It was 15! Harden the security of your VPS. I’m going to rewatch this and hopefully this will help!

Ok, new plan @vasileios. I’m going to delete my VSP and start over from the linode part. New stuff, new ssh because I can’t get into my ssh now. As I redo all this, should I redo workshop 15 and make it all no root and no password? Or is it ok to skip that?

Also would have to redownload wordpress? I am vacillating between thinking this is a simple fix and a huge start over!

Here’s the problem @vasileios. I did get a new VPN and all was going great. I’m following workshop 24 and was on Stage 4, Create New User. When I try to log into ssh at that point ‘jen@ipaddress’ it asks for a password to unlock the private key and nothing I enter works. I’ll post a screenshot.

I got it working!! Sorry I am being a pain. I changed the password in Linode and that did the trick! :dancer:t4:

However… at the end of stage 5 (configure ssh), when I type the command “systemctl restart sshd” nothing happens. I’m still at root@localhost:/etc/ssh#. It looks like for you it changes to root@localhost/home/vasileios#

Hey @Jen!
My apologies for the delay. I wish I could clone myself!
First of all, congratulations on getting things done!

On the SSH side, you do not need to worry. There will be nothing visible when you restart the SSH service while you’re connected. The effects come into play once you re-connect.

Also, the passphrase you got asked for is the one you gave your personal SSH key when you first created it. This is very helpful to disallow others - who main gain access to your system - from hijacking your VPS. :slight_smile:

Hi @vasileios, I’m back to being unable to get into SSH at all. I’m trying every password, including the one I’m sure is right and about every other one that comes to mind. I’m still at having finished stage 5 and about to start stage 6. I’ll attach a screenshot

Hey @Jen!
From what I see on your screenshot (thank you!) tells me that you have a different key on your local system and a different key on the server. That’s why it produces a signature error. What I would recommend is the following.

First, clear the key you have on your system, by executing:

rm -Rf ~/.ssh

Then, create a new SSH key, by using:


Choose a passphrase (and jot it down) so that you remember it. :wink:

Then, display your key by entering:

cat ~/.ssh/

Select all the text output (be precise here) and then right-click and select copy.

Go to your Linode account, then select your profile icon on the top right and select the SSH keys. Then add a new SSH key, name it as you like, and then paste the text you copied earlier. Once done, save.

At the very least, this will insure that you won’t have any trouble logging in from your system in the future on other VPS you may create.

You might try to login, but I’m not sure that it will allow you with the new key, since the OS is already deployed on the SSH. You can bypass that by doing the following steps:

When on your Linode control panel, select your server and then go to the top right side and hit the LISH button. It will pop a new window with two tabs: WebLish & GLish. Select the latter. Login as root.

Then edit your SSHD configuration via:

nano /etc/ssh/sshd_config

Look for the line that permits password login (not the root login) and change it from “No” to “Yes”.
Once done, hit CTRL+O and Enter, then CTRL+X to exit. Then execute:

systemctl restart sshd

Now, return to your normal terminal (don’t close the Glish window yet) and type:

ssh-copy-id jen@

It will ask you for your username’s password (the one you created when you made your new user on the VPS). The process should go through without trouble. Once it does, then return to the Glish window on your Linode & edit the SSH configuration again.

nano /etc/ssh/sshd_config

Change the password login line from “Yes” back to “No”. Save (CTRL+O and then Enter) and exit (CTRL+X). Then type:

systemctl restart sshd

At that point, you may close the Linode windows and return to your terminal. You should be able to login via your non-root user without a problem. :slight_smile: