How To: Restart TeamViewer From The Terminal

In a previous article, I wrote about TeamViewer, and this article will teach you how to restart TeamViewer from the terminal. The reality is, I like TeamViewer quite a bit but it has a nasty habit of failing during the authentication step.

The only way to make it work, without visiting the device in person, is to restart it. I actually do this with SSH, but it’ll work in the terminal. So, you’re doing it from the terminal – you’re just doing it remotely and using SSH to do that.

Well, no… I have no idea how you’ll be doing it. After all, you might choose to do it locally – where this will also work. So, is it really from the terminal? Yes. It just depends on which terminal, I suppose!

Anyhow, this is just a short article. If you’re physically at the computer, why are you using TeamViewer?!? If you’re physically at the computer, you can just restart it with the GUI – or you can use the terminal. 

Restart TeamViewer From The Terminal:

So, if you’re at the device, just open the terminal. If you’re not at the device and TeamViewer isn’t authenticating, just connect to it with SSH. We’ll assume you’ve already set up SSH and know how to connect. If you don’t, then go back and read the SSH link in the 2nd paragraph. You need to use the following commands. 

To stop the TeamViewer service, run:

To restart the TeamViewer service, run:

If you want to just run one command, you can do that too! Just run:

The latter command is probably the easiest, and TeamViewer fails often enough for me to have taken the time to alias the restart command. As far as I can tell, there’s no rhyme or reason for it to no longer authenticate, but that’s what happens.


As I use it often enough, I figure this is worth sharing with the world. It’s not a very long article, but it is indeed an article. Hopefully this helps someone who’s having similar authentication errors. As near as I can tell, just restarting the service fixes it and I’d say that the authentication fails every other day, sometimes more and sometimes less. Thanks for reading!

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

TeamViewer; My Most-Recent Favorite Alternative To VNC.

Today’s article is going to be about my latest favorite VNC alternative, TeamViewer. It’s a surprisingly handy application that just works. Read on to learn more about it!

I’m a pretty big fan of VNC (Virtual Network Computing, from RealVNC). Actually, it’d be a bit more accurate to say that I’m a pretty big fan of remotely managing devices. Among the ways I do this, VNC is a nice way to do so graphically.

Basically, remote administration software such as this forwards the remote desktop to a window on my local desktop and allows me the control as though I was physically seated at the device. I have quite a few devices, and remotely manage the majority of them. I have computers in my house that I seldom physically use, I manage them all remotely. 

SSH is often adequate for anything I want to do, but not always. I can even forward SSH but not all applications work well with that. Sometimes I just want a GUI, as some things are best done in a GUI.

Besides, TeamViewer is free for personal use, and I like TeamViewer because it just works, even over the world wide web without knowing an IP address. I can use it to help friends and relatives by just talking to them long enough to get started.

Frankly, VNC can be a pain in the butt to configure and my favorite VNC client (RealVNC) is proprietary. So, using the proprietary TeamViewer doesn’t bother me. 

If you insist on opensource, this isn’t the tool for you. If you want something that is easy and just works, read on:

Getting and Using TeamViewer:

I’ll explain how to install it with Debian/Ubuntu/etc, but you can easily install TeamViewer for other Linux package management systems. Start by opening your terminal by pressing CTRL + ALT + T.

Once open, let’s grab the latest .deb with wget and install it. If you don’t have wget installed, you can do that with sudo apt install wget and then proceed with:

Copy and paste all three of those lines individually, of course. Press ENTER after each one. The last command should complete the process and would normally be the last step but this is proprietary software so you’ll need to run TeamViewer at least once in order to accept the license agreement. You can just do that in the terminal with:

That should pop up a window where can accept the license and keep on trucking.

Now, you’ll have to install TeamViewer on each device you want to manage and it’ll need to be installed on any device you wish to use to control the rest. Just be careful and read the prompts. It installs and works like a champ.

You’ll need to configure it on each device as well, allowing remote connections and setting up passwords as needed. It can check a centralized server, so the host doesn’t need to know things like ports and passwords.

It’s easily configured the first time, and once you’re done it a remote connection will hopefully look a bit like this:

TeamViewer in action.
This is what a connection might look like. It’s what mine looks like at this minute in time.

You can use this as a single instance or you can configure an account online with the management console to keep track of all your connections from a single point. You’ll spend a confusing amount of time making your browsers and devices ‘trusted’ status. All of this, of course, has obvious privacy implications.

Privacy & Security Concerns:

Again, they’re absolutely going to track your usage. They’ll know your IP addresses and the names of the devices you’re connecting to. They will know when you connect, how long you stay connected, and more. On top of that, they’ll know your email address, if you give it to them.

Having used them for a while, I see no spam from them and they’ve been nothing but acceptably and professionally behaved from my perspective. I don’t even get any regular newsletter emails from them. I think it’s safe to assume they’re currently not doing so. They do a whole lot of email verification steps if you want to trust devices.

Being proprietary, we have no idea what the source code looks like. We have no way to be sure that they’re not being malicious. They’re a business and they’d do poorly if it turned out they were malicious and using this information for spying or anything of that nature. 

If you’re running from an oppressive government, I’d probably not use them. They’re a business and that means they’re likely to respond to lawful requests – and laws around the globe can be pretty terrible.

In fact, if you’re doing anything that’s even remotely secure, I’d suggest not doing so over TeamViewer. Sure, when the application is terminated you can verify that it’s down, but at the same time don’t connect to your remote device to do your banking. That’d just be silly regardless.

As I stated above, I’m quite okay with the potential privacy and security implications. I don’t use Linux because of any philosophical reasons, I use Linux because it just works. If you’re different and object in some way, you should probably just move on and use alternative software to remotely manage your devices.


And there you have it! It’s yet another article in the books, another article in the records. Traffic has been high lately, and that’s great. Things are growing in a linear feature and I’m okay with that. Even my Reddit sub is growing – at 50 viewers, up from just a few when I first took the sub over. So, things are going great.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Subscribe To Our Newsletter
Get notified when new articles are published! It's free and I won't send you any spam.
Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.