Ce Forum passera en lecture seule en janvier 2020
Image
Merci de vous rendre sur https://community.jeedom.com maintenant pour vos prochains postes ;)

probleme acces externe dns jeedom

De l'installation à l'utilisation venez discuter de JEEDOM au quotidien
bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

probleme acces externe dns jeedom

Message par bornich » 30 mars 2019, 18:12

Bonjour,

j'ai fais la dernière mise a jour de jeedom ce matin et je m’aperçois que l’accès externe est NOK alors que j'ai un service pack.

je me sers principalement de cet accès pour contrôler des éclairages avec la google home mini. En voyant que ca ne marchait plus, je suis allé voir dans santé et là : accès externe NOK. Tout a l'air ok sur mon market .....

une idée ?

Bosquetia
Actif
Messages : 6783
Inscription : 10 mai 2016, 07:54

Re: probleme acces externe dns jeedom

Message par Bosquetia » 30 mars 2019, 18:22

Hello,

Oui vérifier la config réseau, gérée par jeedom ou pas et sinon donner des logs
Sans autres infos techniques que ca marche pas, aucun diagnostic ne peut être établi.

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 30 mars 2019, 21:09

ben ... c'est reparti ..... pfff ... dsl

pb serveurs jeedom ?

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 15 avr. 2019, 18:49

bonsoir,

j'ai dans "santé" : Configuration réseau externe NOK Allez sur Administration -> Configuration -> Réseaux, puis configurez correctement la partie réseau

ca arrive régulièrement, ca revient .... pas facile

que puis je faire pour fiabiliser ? quand a donner des logs ...... euh, je fais comment ?

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 15 avr. 2019, 20:00

j'ai bien trouvé le menu logs mais je n'arrive pas a trouver de choses correspondantes a cet accès externe

pour info : depuis mon dernier message, il est passé a ok 2 fois et autant en nok......

peut il y avoir un rapport avec mon joueur invétéré de gamin en vacances, sachant que lui et le rpi sont branchés directs a la box (baie de brassage mais pas de switch) et que je surfe en même temps mais que je ne sens pas de ralentissement comme ça peut arriver

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 15 avr. 2019, 20:38

trouvé les logs !!
Mon Apr 15 16:31:50 2019 WARNING: file '/tmp/jeedom/openvpn/openvpn_auth_xj8ih5jvNlk2vqJNNh56Ok2jqaPOdx.conf' is group or others accessible
Mon Apr 15 16:31:50 2019 OpenVPN 2.4.0 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 14 2018
Mon Apr 15 16:31:50 2019 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08
Mon Apr 15 16:31:50 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 16:32:30 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:33:10 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:33:10 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 16:33:10 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 16:33:15 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 16:33:55 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:34:35 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:34:35 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 16:34:35 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 16:34:40 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 16:35:20 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:36:00 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:36:00 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 16:36:00 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 16:36:05 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 16:36:45 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:37:25 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:37:25 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 16:37:25 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 16:37:30 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 16:38:10 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:38:50 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 16:38:50 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 16:38:50 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 16:39:00 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 16:39:10 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]195.154.38.163:1196
Mon Apr 15 16:39:10 2019 UDP link local: (not bound)
Mon Apr 15 16:39:10 2019 UDP link remote: [AF_INET]195.154.38.163:1196
Mon Apr 15 16:39:10 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Apr 15 16:39:10 2019 VERIFY OK: depth=1, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=jeedom.com CA, name=jeedom, emailAddress=postmaster@jeedom.com
Mon Apr 15 16:39:10 2019 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Mon Apr 15 16:39:10 2019 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Mon Apr 15 16:39:10 2019 [server] Peer Connection Initiated with [AF_INET]195.154.38.163:1196
Mon Apr 15 16:39:12 2019 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Apr 15 16:39:12 2019 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Apr 15 16:39:12 2019 TUN/TAP device tun0 opened
Mon Apr 15 16:39:12 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Apr 15 16:39:12 2019 /sbin/ip link set dev tun0 up mtu 1500
Mon Apr 15 16:39:12 2019 /sbin/ip addr add dev tun0 local 10.11.1.209 peer 10.11.1.210
Mon Apr 15 16:39:12 2019 Initialization Sequence Completed
Mon Apr 15 17:39:10 2019 VERIFY OK: depth=1, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=jeedom.com CA, name=jeedom, emailAddress=postmaster@jeedom.com
Mon Apr 15 17:39:10 2019 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Mon Apr 15 17:39:10 2019 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Apr 15 17:39:10 2019 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Apr 15 17:39:10 2019 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Mon Apr 15 17:50:17 2019 AEAD Decrypt error: cipher final failed
Mon Apr 15 17:50:28 2019 AEAD Decrypt error: cipher final failed
Mon Apr 15 17:50:38 2019 AEAD Decrypt error: cipher final failed
Mon Apr 15 17:50:48 2019 AEAD Decrypt error: cipher final failed
Mon Apr 15 17:50:58 2019 AEAD Decrypt error: cipher final failed
Mon Apr 15 17:51:08 2019 AEAD Decrypt error: cipher final failed
Mon Apr 15 17:51:50 2019 [server] Inactivity timeout (--ping-restart), restarting
Mon Apr 15 17:51:50 2019 SIGUSR1[soft,ping-restart] received, process restarting
Mon Apr 15 17:51:55 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 17:51:55 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]195.154.38.163:1196
Mon Apr 15 17:51:55 2019 UDP link local: (not bound)
Mon Apr 15 17:51:55 2019 UDP link remote: [AF_INET]195.154.38.163:1196
Mon Apr 15 17:52:55 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Mon Apr 15 17:52:55 2019 TLS Error: TLS handshake failed
Mon Apr 15 17:52:55 2019 SIGUSR1[soft,tls-error] received, process restarting
Mon Apr 15 17:53:00 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 17:53:40 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:54:20 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:54:20 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 17:54:20 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 17:54:25 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 17:55:05 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:55:45 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:55:45 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 17:55:45 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 17:55:50 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 17:56:30 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:57:10 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:57:10 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 17:57:10 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 17:57:15 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 17:57:55 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:58:35 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 17:58:35 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 17:58:35 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 17:58:40 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 17:59:20 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:00:00 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:00:00 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:00:00 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:00:10 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:00:50 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:01:31 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:01:31 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:01:31 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:01:51 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:02:31 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:03:11 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:03:11 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:03:11 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:03:51 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:04:31 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:05:11 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:05:11 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:05:11 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:06:31 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:07:11 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:07:51 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:07:51 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:07:51 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:10:31 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:11:11 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:11:51 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:11:51 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:11:51 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:16:51 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:17:31 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:18:11 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:18:11 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:18:11 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:23:11 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:23:51 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:24:31 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:24:31 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:24:31 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:29:31 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Apr 15 18:30:11 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:30:51 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Mon Apr 15 18:30:51 2019 Could not determine IPv4/IPv6 protocol
Mon Apr 15 18:30:51 2019 SIGUSR1[soft,init_instance] received, process restarting
Mon Apr 15 18:35:51 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

Avatar de l’utilisateur
Patdec
Actif
Messages : 771
Inscription : 21 janv. 2015, 15:49
Localisation : Tournai

Re: probleme acces externe dns jeedom

Message par Patdec » 15 avr. 2019, 21:12

bornich a écrit :
15 avr. 2019, 20:38

Mon Apr 15 16:31:50 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

En rouge ça te dit quelque chose ?

Quand on regarde le lien; il y a une tartine à se farcir pour paramétrer.
Il doit y avoir plus simple.

Après on voit bien qu'il tourne en boucle. C'est toujours la même erreur.
Débutant Jeedom.
VirtualBox 6.0.10 sur Tablette I Works 12 sous Win 10 - Debian 9.9
Jeedom 3.3.36 - Contrôleur Aeotec ZW 090 C
Modules Fibaro FGR-222

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 16 avr. 2019, 18:31

ben non, ca ne me dit rien mais vu mes connaissances en réseau, c est pas surprenant. Le genre de trucs que je ne vais pas toucher sans procédure claire...

j'ai pris le DNS jeedom (pack power à 50€ je crois) pour ne pas avoir a m'en occuper ..... la dernière fois que j'ai eu le pb, j'ai voulu ouvrir un ticket en même temps que je posais la question ici : je n'ai jamais eu de réponse ......

ca m'ennuie sérieusement

pff, je viens de faire la dernière mise a jour et ca remarche, mais pour combien de temps ?

Avatar de l’utilisateur
Patdec
Actif
Messages : 771
Inscription : 21 janv. 2015, 15:49
Localisation : Tournai

Re: probleme acces externe dns jeedom

Message par Patdec » 16 avr. 2019, 21:43

bornich a écrit :
16 avr. 2019, 18:31
ben non, ca ne me dit rien mais vu mes connaissances en réseau, c est pas surprenant. Le genre de trucs que je ne vais pas toucher sans procédure claire...

j'ai pris le DNS jeedom (pack power à 50€ je crois) pour ne pas avoir a m'en occuper ..... la dernière fois que j'ai eu le pb, j'ai voulu ouvrir un ticket en même temps que je posais la question ici : je n'ai jamais eu de réponse ......

ca m'ennuie sérieusement

pff, je viens de faire la dernière mise a jour et ca remarche, mais pour combien de temps ?

Je suis pas plus calé que toi en réseau, je serai même plutôt " recalé " :lol:
Je voulais juste souligner que tu avais un problème de certificat.

A savoir si la mise à jour du core en 3.3.20 règle le problème définitivement.
Débutant Jeedom.
VirtualBox 6.0.10 sur Tablette I Works 12 sous Win 10 - Debian 9.9
Jeedom 3.3.36 - Contrôleur Aeotec ZW 090 C
Modules Fibaro FGR-222

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 17 avr. 2019, 19:02

ben rebelote a cette heure ci : ci dessous les logs jeedom ...

[2019-04-15 21:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-15 22:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-15 23:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 00:00:33][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 01:00:33][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 02:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 03:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 04:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 05:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 06:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 07:00:33][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 08:00:33][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 09:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 10:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 11:00:33][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 12:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 13:00:33][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 14:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-16 15:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-17 18:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com
[2019-04-17 19:00:32][ERROR] : Erreur curl sur : https://www.jeedom.com/market/core/api/api.php. Détail :Could not resolve host: www.jeedom.com

Julien30
Timide
Messages : 100
Inscription : 17 déc. 2015, 08:41

Re: probleme acces externe dns jeedom

Message par Julien30 » 21 avr. 2019, 09:31

Salut,
Moi aussi depuis quelques jours !
Même problème !
Je précise que ça marche depuis des mois.
Sun Apr 21 07:30:31 2019 RESOLVE: Cannot resolve host address: vpn.dns1.jeedom.com: Temporary failure in name resolution
Merci pour votre aide

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 21 avr. 2019, 16:45

comme quoi .......... il n'y a pas que moi
d’après le support (un certain Loic), ça vient de ma box et il ne peut rien faire ........ euh ..... pour 50€, je continue de harceler.
d’après lui, jeedom essaie de se connecter mais ma box lui dit qu'il n'y a pas d'internet...... il n'a pas l'air de vouloir aller plus loin, ça me choque pour un produit non gratuit
techniquement, je suis complètement dépassé, là

je suppose que ta box n'a pas changé non plus

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 21 avr. 2019, 16:49

@Bosquetia ? tu pourrais nous en dire plus avec les logs publiés ?

Avatar de l’utilisateur
Patdec
Actif
Messages : 771
Inscription : 21 janv. 2015, 15:49
Localisation : Tournai

Re: probleme acces externe dns jeedom

Message par Patdec » 21 avr. 2019, 18:41

bornich a écrit :
21 avr. 2019, 16:45
comme quoi .......... il n'y a pas que moi
d’après le support (un certain Loic), ça vient de ma box et il ne peut rien faire ........ euh ..... pour 50€, je continue de harceler.
d’après lui, jeedom essaie de se connecter mais ma box lui dit qu'il n'y a pas d'internet...... il n'a pas l'air de vouloir aller plus loin, ça me choque pour un produit non gratuit
techniquement, je suis complètement dépassé, là

je suppose que ta box n'a pas changé non plus

En y réfléchissant un peu, tu crois pas que tu as un problème configuration ou matériel chez toi ?
S'il y avait des problèmes liés aux DNS Jeedom, tu crois pas qu'il y aurait une quantité de posts signalant un problème récurrent
Le problème est certainement plus de ton côté.

Tu as acheté pour 50€ d'eau pour ta piscine, mais elle a peut être une fuite et je te parle même pas de l'évaporation :lol: . Pourquoi rendre Véolia responsable ? :shock:
Débutant Jeedom.
VirtualBox 6.0.10 sur Tablette I Works 12 sous Win 10 - Debian 9.9
Jeedom 3.3.36 - Contrôleur Aeotec ZW 090 C
Modules Fibaro FGR-222

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 21 avr. 2019, 18:57

justement, Véolia, Saur, etc ont des services qui t'aident a résoudre ce genre de problèmes ...... si, si, j'ai eu le cas au boulot

peut être que c'est chez moi mais sans rien avoir changé, donc je ne vois pas. qui plus est, je ne sais même pas de quel coté chercher ..... mon rpi est branché sur une box sfr tout ce qu'il y a de plus con.....

Avatar de l’utilisateur
Patdec
Actif
Messages : 771
Inscription : 21 janv. 2015, 15:49
Localisation : Tournai

Re: probleme acces externe dns jeedom

Message par Patdec » 21 avr. 2019, 19:04

bornich a écrit :
21 avr. 2019, 18:57
justement, Véolia, Saur, etc ont des services qui t'aident a résoudre ce genre de problèmes ...... si, si, j'ai eu le cas au boulot

peut être que c'est chez moi mais sans rien avoir changé, donc je ne vois pas. qui plus est, je ne sais même pas de quel coté chercher ..... mon rpi est branché sur une box sfr tout ce qu'il y a de plus con.....
@Bosquetia t'as demandé les logs. Tu veux pas les donner, pourquoi ?
Débutant Jeedom.
VirtualBox 6.0.10 sur Tablette I Works 12 sous Win 10 - Debian 9.9
Jeedom 3.3.36 - Contrôleur Aeotec ZW 090 C
Modules Fibaro FGR-222

Avatar de l’utilisateur
Poumi
Actif
Messages : 660
Inscription : 21 mars 2019, 22:41

Re: probleme acces externe dns jeedom

Message par Poumi » 21 avr. 2019, 19:06

Tu as essayé de te connecter en ssh sur ton rpi et de faire un Ping de www.google.com par exemple?

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 21 avr. 2019, 19:18

lorsque Bosquetia me les a demandé, je ne savais ni les trouver ni lesquels ils voulait .......
maintenant, je pense savoir les trouver et le sav m'a demandé ceux de openvpn que je mets de suite ici

Rechercher
Sun Apr 21 15:54:56 2019 WARNING: file '/tmp/jeedom/openvpn/openvpn_auth_xj8ih5jvNlk2vqJNNh56Ok2jqaPOdx.conf' is group or others accessible
Sun Apr 21 15:54:56 2019 OpenVPN 2.4.0 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 14 2018
Sun Apr 21 15:54:56 2019 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08
Sun Apr 21 15:54:56 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 15:55:36 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 15:56:16 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 15:56:16 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 15:56:16 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 15:56:21 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 15:57:01 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 15:57:41 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 15:57:41 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 15:57:41 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 15:57:46 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 15:58:26 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 15:59:06 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 15:59:06 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 15:59:06 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 15:59:11 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 15:59:51 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:00:31 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:00:31 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:00:31 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:00:36 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:01:16 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:01:56 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:01:56 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:01:56 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:02:06 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:02:46 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:03:26 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:03:26 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:03:26 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:03:46 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:04:26 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:05:06 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:05:06 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:05:06 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:05:46 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:06:26 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:07:06 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:07:06 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:07:06 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:08:26 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:08:31 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]195.154.38.163:1196
Sun Apr 21 16:08:31 2019 UDP link local: (not bound)
Sun Apr 21 16:08:31 2019 UDP link remote: [AF_INET]195.154.38.163:1196
Sun Apr 21 16:08:31 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun Apr 21 16:08:31 2019 VERIFY OK: depth=1, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=jeedom.com CA, name=jeedom, emailAddress=postmaster@jeedom.com
Sun Apr 21 16:08:31 2019 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Sun Apr 21 16:08:31 2019 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Sun Apr 21 16:08:31 2019 [server] Peer Connection Initiated with [AF_INET]195.154.38.163:1196
Sun Apr 21 16:08:48 2019 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sun Apr 21 16:08:48 2019 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sun Apr 21 16:08:48 2019 TUN/TAP device tun0 opened
Sun Apr 21 16:08:48 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sun Apr 21 16:08:48 2019 /sbin/ip link set dev tun0 up mtu 1500
Sun Apr 21 16:08:48 2019 /sbin/ip addr add dev tun0 local 10.11.1.209 peer 10.11.1.210
Sun Apr 21 16:08:48 2019 Initialization Sequence Completed
Sun Apr 21 16:19:18 2019 [server] Inactivity timeout (--ping-restart), restarting
Sun Apr 21 16:19:18 2019 SIGUSR1[soft,ping-restart] received, process restarting
Sun Apr 21 16:19:23 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:19:23 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]195.154.38.163:1196
Sun Apr 21 16:19:23 2019 UDP link local: (not bound)
Sun Apr 21 16:19:23 2019 UDP link remote: [AF_INET]195.154.38.163:1196
Sun Apr 21 16:20:23 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Apr 21 16:20:23 2019 TLS Error: TLS handshake failed
Sun Apr 21 16:20:23 2019 SIGUSR1[soft,tls-error] received, process restarting
Sun Apr 21 16:20:28 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:21:08 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:21:48 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:21:48 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:21:48 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:21:53 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:22:33 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:23:13 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:23:13 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:23:13 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:23:18 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:23:58 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:24:38 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:24:38 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:24:38 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:24:43 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:25:23 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:26:03 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:26:03 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:26:03 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:26:08 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:26:48 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:27:28 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:27:28 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:27:28 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:27:38 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:28:18 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:28:58 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:28:58 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:28:58 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:29:18 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:29:58 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:30:38 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:30:38 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:30:38 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:31:18 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:31:58 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:32:38 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:32:38 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:32:38 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:33:58 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:34:38 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:35:18 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:35:18 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:35:18 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:37:58 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:38:38 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:39:19 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:39:19 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:39:19 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:44:19 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:44:59 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:45:39 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:45:39 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:45:39 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:50:39 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:51:19 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:51:59 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:51:59 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:51:59 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 16:56:59 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 16:57:39 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:58:19 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 16:58:19 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 16:58:19 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 17:03:19 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 17:03:59 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 17:04:39 2019 RESOLVE: Cannot resolve host address: vpn.dns3.jeedom.com:1196 (Temporary failure in name resolution)
Sun Apr 21 17:04:39 2019 Could not determine IPv4/IPv6 protocol
Sun Apr 21 17:04:39 2019 SIGUSR1[soft,init_instance] received, process restarting
Sun Apr 21 17:09:39 2019 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sun Apr 21 17:09:39 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]195.154.38.163:1196
Sun Apr 21 17:09:39 2019 UDP link local: (not bound)
Sun Apr 21 17:09:39 2019 UDP link remote: [AF_INET]195.154.38.163:1196
Sun Apr 21 17:09:39 2019 VERIFY OK: depth=1, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=jeedom.com CA, name=jeedom, emailAddress=postmaster@jeedom.com
Sun Apr 21 17:09:39 2019 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Sun Apr 21 17:09:39 2019 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Sun Apr 21 17:09:39 2019 [server] Peer Connection Initiated with [AF_INET]195.154.38.163:1196
Sun Apr 21 17:09:40 2019 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sun Apr 21 17:09:40 2019 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sun Apr 21 17:09:40 2019 Preserving previous TUN/TAP instance: tun0
Sun Apr 21 17:09:40 2019 Initialization Sequence Completed

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 21 avr. 2019, 19:22

merci de remarquer que le dernier date de 17:09, j'ai validé le post après le collé à 19:19, je ne sais pas si ça donne des indices.

le ping de google en ssh donc depuis le rpi je pense donne ca :
--- www.google.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12018ms
rtt min/avg/max/mdev = 21.768/22.592/28.298/1.668 ms

merci de vous interesser !!

bornich
Timide
Messages : 273
Inscription : 29 juil. 2017, 18:05

Re: probleme acces externe dns jeedom

Message par bornich » 21 avr. 2019, 19:25

j'ajoute, qu'a 19:15, la config reseau externe est marqué ok dans santé et que tout marche, on verra ce que disent les logs

Répondre

Revenir vers « Utilisation »

Qui est en ligne ?

Utilisateurs parcourant ce forum : Aucun utilisateur inscrit et 2 invités