only for curiosity, do you have pihole instaled?.
I suspect that Teamviewer need some ping or response from internet and my pihole block it and that is the reason, but I can't be sure.
only for curiosity, do you have pihole instaled?.
I suspect that Teamviewer need some ping or response from internet and my pihole block it and that is the reason, but I can't be sure.
No, I dononly for curiosity, do you have pihole instaled?.
I suspect that Teamviewer need some ping or response from internet and my pihole block it and that is the reason, but I can't be sure.
No I don't.
I have installed the Teamviewer plugin on a fresh install of OMV 4.0.17-1 and it works on the go, getting a correct ID from the web panel and accepting incoming connections from my Teamviewer client on Windows.
So it seems to be some sort of incompatibility with other plugins/services. The problem is that I have so many plugins installed and running on my main OMV build that it will be hard to determine which one interferes with it.
Plugins
openmediavault 4.0.17-1 all openmediavault - The open network attached storage solution
openmediavault-anacron 3 all anacron plugin for OpenMediaVault.
openmediavault-apttool 3.4 all apt tool plugin for OpenMediaVault.
openmediavault-autoshutdown 4.0.2 all OpenMediaVault AutoShutdown Plugin
openmediavault-backup 3.9 all backup plugin for OpenMediaVault.
openmediavault-clamav 4.1.4-1 all OpenMediaVault ClamAV plugin
openmediavault-cups 3.1.2 all OpenMediaVault CUPS (network printer server) plugin.
openmediavault-diskstats 4 all OpenMediaVault disk monitoring plugin
openmediavault-docker-gui 4.0.1 all OpenMediaVault plugin for Docker
openmediavault-flashmemory 4.1 all folder2ram plugin for OpenMediaVault
openmediavault-keyring 1 all GnuPG archive keys of the OpenMediaVault archive
openmediavault-letsencrypt 3.4.5 all Generate free and valid SSL certificates for OMV
openmediavault-locate 3.4 all locate plugin for OpenMediaVault.
openmediavault-luksencryption 3.0.2 all OpenMediaVault LUKS encryption plugin
openmediavault-nut 4.0.9-1 all OpenMediaVault Network UPS Tools (NUT) plugin
openmediavault-omvextrasorg 4.1.2 all <a href="http://OMV-Extras.org">OMV-Extras.org</a> Package Repositories for OpenMediaVault
openmediavault-remotemount 4 all Remote mount plugin for OpenMediaVault.
openmediavault-resetperms 3.3 all Reset Permissions
openmediavault-route 4.0.3-1 all OpenMediaVault IP routing table plugin
openmediavault-sftp 3.1.6 all sftp server
openmediavault-snmp 4.0.3-1 all OpenMediaVault SNMP (Simple Network Management Protocol) plugin
openmediavault-symlinks 3.1.3 all OpenMediaVault symlinks plugin
openmediavault-teamviewerhost 3 all Teamviewer Host plugin for OpenMediaVault.
openmediavault-tftp 4.0.3-1 all OpenMediaVault TFTP-Server plugin
openmediavault-unionfilesystems 4 all Union filesystems plugin for OpenMediaVault.
openmediavault-virtualbox 4 all VirtualBox plugin for OpenMediaVault.
openmediavault-wakealarm 3.3 all wakealarm plugin for OpenMediaVault.
openmediavault-webdav 4 all OpenMediaVault WebDAV plugin.
Alles anzeigen
Containers
CONTAINER ID IMAGE NAMES COMMAND
139ec443ad89 linuxserver/plex:latest plex "/init"
74c4294e12c4 coppit/filebot:latest filebot "/sbin/my_init"
d404cc1b43b0 linuxserver/znc:latest znc "/init"
f41b0fcef151 linuxserver/tvheadend:latest tvheadend "/init"
12045d6570e7 linuxserver/tt-rss:latest tt-rss "/init"
6d033d11f1c0 linuxserver/smokeping:latest smokeping "/init"
864fe129fb44 linuxserver/plexpy:latest plexpy "/init"
03fca572cec3 linuxserver/kodi-headless:latest kodi-headless "/init"
d766eec1a582 linuxserver/piwigo:latest piwigo "/init"
5af78e18b3da linuxserver/openvpn-as:latest openvpn-as "/init"
2ced1d9f352f linuxserver/ombi:latest ombi "/init"
ffc8d0f7c830 linuxserver/nzbget:latest nzbget "/init"
b58435255e19 linuxserver/nginx:latest nginx "/init"
8c65058795fe linuxserver/muximux:latest muximux "/init"
c5b764728236 linuxserver/mariadb:latest mariadb "/init"
b1b11c2c5176 linuxserver/duckdns:latest duckdns "/init"
dc6ae68a4ad8 linuxserver/domoticz:latest domoticz "/init"
1d1ad71ac20e linuxserver/deluge:latest deluge "/init"
317264a84c9b linuxserver/booksonic:latest booksonic "/init"
324db7c0e205 linuxserver/airsonic:latest airsonic "/init"
55fd28fd72d6 linuxserver/ubooquity:latest ubooquity "/init"
cb7143fb9479 linuxserver/oscam:latest oscam "/init"
0af8830b83db linuxserver/zoneminder:latest zoneminder "/init"
fb6052f094dd linuxserver/syncthing:latest syncthing "/init"
4d8ec1ba4665 linuxserver/calibre-web:latest calibre-web "/init"
9b5c07edf606 magnaz/traccar:latest traccar "java -Djava.net.pre…"
56aba4d76d01 linuxserver/gsm-ts3:latest teamspeak "/init"
93b2a4e6d50e linuxserver/nextcloud:latest nextcloud "/init"
Alles anzeigen
my plugins are:
I have a virtual (test) enviroment to test your aproach, so my next probe can be install teamviewer alone and check if works
PD: in my test enviroment , teamviewer actually do not work, but I install first the 6 plugings that have in my primary NAS, and never check to install teamviewer the first, so this night i have a response for you.
I do a new fresh install and then update it, next I install Omv-extras, and activate teamviewer repro, install teamviewer and still no work, so it's not a conflict with plugins, at leats on my side / test enviroment.
PD: because my test enviroment use DHCP for images, the test image use pihole as default DNS server, so the only test that this night I can do is to change image config to use fixed IP and fixed DNS= 8.8.8.8 to test again.
new test, same that previous, but use 8.8.8.8 as DNS, still no luck, so in my side is not pihole or some plugings the cause.
Do you do some test in your side?.
Hi!
I have installed the Teamviewer plugin and it doesn't work also.
Actually the teamviewerd is running:
root@droid:~# teamviewer daemon status
systemctl status teamviewerd.service
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled)
Active: active (running) since Tue 2018-03-06 11:40:32 EET; 34min ago
Process: 5505 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 5507 (teamviewerd)
CGroup: /system.slice/teamviewerd.service
└─5507 /opt/teamviewer/tv_bin/teamviewerd -d
Mar 06 11:40:32 droid systemd[1]: Started TeamViewer remote control daemon.
Alles anzeigen
But I can't connect remotely - Teamviewer client says that Teamviewer isn't active on the remote computer.
I joined my OMV NAS to teamviwer account (using teamviewer setup via SSH), but it stays offline in teamviewer client.
Than I trying to do teamviewer setup again, I've got message that my system is already registered. And it becomes online on the Teamviewer client list at that moment, but it's impossible to connect anyway.
It looks that teamviewerd doesn't connect to teamviewers' servers:
root@droid:~# netstat -ntap | grep teamviewer
tcp 0 0 127.0.0.1:5943 0.0.0.0:* LISTEN 5507/teamviewerd
No idea what to dig next.
raulfg3
I do have read this topic, and I spent few days searching the solution. But not successfully also.
But I guess I found the possible core of that problem, because the netstat output on the system with operational teamviewer looks like this:
user@home_machine:~$ sudo netstat -ntap | grep teamviewer
tcp 0 0 127.0.0.1:5941 0.0.0.0:* LISTEN 20351/teamviewerd
tcp 0 0 192.168.1.100:49333 176.223.198.114:5938 ESTABLISHED 20351/teamviewerd
In my case I found there is no connection teamviewerd to Teamviewers servers:
root@droid:~# netstat -ntap | grep teamviewer
tcp 0 0 127.0.0.1:5943 0.0.0.0:* LISTEN 5507/teamviewerd
Now I'm trying to find the reason of connection absence.
May be somebody here has ideas about...
good to know i do some test too and post my result here.
sorry no netstat on my system:
Linux PDNS 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Mar 1 15:30:50 2018 from 192.168.1.100
root@PDNS:~# netstat -ntap | grep teamviewer
-bash: netstat: no se encontró la orden
root@PDNS:~# sudo netstat -ntap | grep teamviewer
sudo: netstat: command not found
root@PDNS:~# apt-get install netstat
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
E: No se ha podido localizar el paquete netstat
root@PDNS:~# ^C
root@PDNS:~#
Alles anzeigen
sorry no netstat on my system:
netstat is old but apt-get install net-tools will install it.
$ sudo netstat -tupln | grep team
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 14099/teamviewerd
Use ss which should already be installed on your system:
$ sudo ss -tulpn | grep team
tcp LISTEN 0 128 127.0.0.1:5939 *:* users:(("teamviewerd",pid=14099,fd=14))
Now I'm trying to find the reason of connection absence.
May be somebody here has ideas about...
Your system is listening. This would be a good question for the teamviewer people. I saw your github issue but there is nothing I can do to fix the plugin if the service is listening.
ok, net-tools installed:
root@RDNS:~# netstat -ntap | grep teamviewer
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 16170/teamviewerd
root@RDNS:~#
root@RDNS:~# netstat -tupln | grep team
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 16170/teamviewerd
root@RDNS:~#
root@RDNS:~# ss -tulpn | grep team
tcp LISTEN 0 128 127.0.0.1:5939 *:* users:(("teamviewerd",pid=16170,fd=15))
root@RDNS:~#
Alles anzeigen
my install:
root@RDNS:~# teamviewer daemon status
systemctl status teamviewerd.service
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2018-03-06 21:37:37 CET; 2min 53s ago
Main PID: 15217 (code=exited, status=0/SUCCESS)
CPU: 236ms
mar 06 21:37:34 RDNS systemd[1]: Starting TeamViewer remote control daemon...
mar 06 21:37:34 RDNS systemd[1]: teamviewerd.service: PID file /var/run/teamviewerd.pid not readable (yet?) after start: No such file or directory
mar 06 21:37:34 RDNS systemd[1]: Started TeamViewer remote control daemon.
mar 06 21:37:37 RDNS systemd[1]: Stopping TeamViewer remote control daemon...
mar 06 21:37:37 RDNS systemd[1]: Stopped TeamViewer remote control daemon.
fail
root@RDNS:~#
Alles anzeigen
My hardware is HP510 on signature.
ok, net-tools installed:
You didn't need to install net-tools. Your system is listening on the right port. Not sure what else to say other than ask on the teamviewer forum.
ryecoaaron
At my view, Teamviewer daemon have to initiate connection to Teamviewers servers (something like server19408.teamviewer.com) for handshake, ID assignment, tunnel establishment, etc., before teamviewer client will get possibility to connect to target system.
Otherwise it will be impossible to connect remote system via internet thru NAT, routers, etc...
On this netstat output:
root@RDNS:~# netstat -ntap | grep teamviewer
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 16170/teamviewerd
we have only localhost listening for loopback purposes only.
There is no any other connection necessary for tunnelling between remote an local systems via Teamviewers servers.
That is the problem I guess.
Other thing, I cannot connect my remote system directly in the same local network, but teamviewer software allowed direct connection in the same local network, for Windows version at list.
I didn't check that you are the author of openmediavault-teamviewerhost plugin, I'm sorry for any possible inconvenience for you in case my issue opening on Github.
And you are right - that's the question for teamviewer support mostly.
we have only localhost listening for loopback purposes only.
There is no any other connection necessary for tunnelling between remote an local systems via Teamviewers servers.
That is the problem I guess.
My test system is working with only localhost listening. Below is the output with and without being connected to a teamviewer client from the internet.
# dpkg -l | grep team
ii openmediavault-teamviewerhost 3.0 all Teamviewer Host plugin for OpenMediaVault.
ii teamviewer-host 13.0.5641 amd64 Remote control solution.
# netstat -tulpn | grep team
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 14099/teamviewerd
# netstat -tulpn | grep team
tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 14099/teamviewerd
udp 0 0 0.0.0.0:60671 0.0.0.0:* 14099/teamviewerd
Alles anzeigen
My test system is working with only localhost listening.
No idea how it can be working without established connections.
Perhaps it happened because you cut off other connections from netstat output by using -l parameter.
Now I'm digging teamviewers community for useful topics.
This one looks interesting:
community.teamviewer.com/t5/Linux/No-connection-to-server-on-TeamViewer-12
No idea how it can be working without established connections.
Perhaps it happened because you cut off other connections from netstat output by using -l parameter.
It is connected.
tcp 0 0 192.168.1.18:53690 162.250.3.6:5938 ESTABLISHED 14099/teamviewerd
It is connected.
tcp 0 0 192.168.1.18:53690 162.250.3.6:5938 ESTABLISHED 14099/teamviewerd
Here it is!
Mine isn't...
display manager are mentioned here: https://community.teamviewer.c…able-9-2-no-GUI/m-p/24817
raulfg3
Teamviewer team declaring about headless instalation mode
Installation via ssh (headless mode)
After installing the package via ssh, on a machine with no monitor attached and no X server running, you have to find a way to connect.
You could set a password and get your TeamViewer ID via command line, but the recommended way is to assign the device to your account. To do this, run setup.
How-to-install-TeamViewer-Host-for-Linux
And System requirements nothing says about X server.
But anything can happen...
still no luck, I connect a keyboard and a monitor to my headless HP510, and still no luck same error.
NO ID.
PD: If I run setup from shell:
root@RDNS:~# teamviewer setup
El demonio de TeamViewer no está en ejecución; la instalación no puede continuar. Active el demonio
de TeamViewer antes de invocar la instalación.
root@RDNS:~#
and teamviewer info:
root@RDNS:~# teamviewer info
TeamViewer 13.0.5641 (DEB)
TeamViewer ID:
Try restarting the TeamViewer daemon (e.g. teamviewer --daemon restart)
teamviewerd status n/a (error)
root@RDNS:~#
Alles anzeigen
and if I restart daemon, still no ID:
systemctl restart teamviewerd.service
root@RDNS:~# teamviewer info
TeamViewer 13.0.5641 (DEB)
TeamViewer ID:
Try restarting the TeamViewer daemon (e.g. teamviewer --daemon restart)
teamviewerd status ● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-03-08 07:58:59 CET; 5s ago
Process: 6361 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 6363 (teamviewerd)
Tasks: 15 (limit: 4915)
Memory: 5.9M
CPU: 95ms
CGroup: /system.slice/teamviewerd.service
└─6363 /opt/teamviewer/tv_bin/teamviewerd -d
mar 08 07:58:59 RDNS systemd[1]: Starting TeamViewer remote control daemon...
mar 08 07:58:59 RDNS systemd[1]: teamviewerd.service: PID file /var/run/teamviewerd.pid not readable (yet?) after start: No such file or directory
mar 08 07:58:59 RDNS systemd[1]: Started TeamViewer remote control daemon.
root@RDNS:~#
Alles anzeigen
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!