Nouveau DNS jeedom

totovaauski · Message par **totovaauski** » 17 janv. 2016, 18:50

Oui, car pour l instant, c est du beta public, tout sera "carré" en V2

Envoyer avec mon pouce ...

gpqpptdp · Message par **gpqpptdp** » 17 janv. 2016, 19:31

Merci , c'est deja une bonne chose car je ne suis tjs pas connecté.

J'ai toujours le meme log meme apres avoir refait les dépendances du plugin, supprimer du market l'ancien DNS , attendu le nouveau afin d'avoir un nouveau mot de passe ..

Code : Tout sélectionner

Sun Jan 17 19:30:11 2016 OpenVPN 2.3.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Dec  1 2014
Sun Jan 17 19:30:11 2016 library versions: OpenSSL 1.0.1k 8 Jan 2015, LZO 2.08
Sun Jan 17 19:30:11 2016 WARNING: file '/tmp/openvpn_auth_D4GtHD4UXnAwV3EFPK41Jan0m3AfUR.conf' is group or others accessible
Sun Jan 17 19:30:11 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Sun Jan 17 19:30:11 2016 UDPv4 link local: [undef]
Sun Jan 17 19:30:11 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Sun Jan 17 19:30:11 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun Jan 17 19:30:11 2016 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 Jan 17 19:30:11 2016 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 Jan 17 19:30:11 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jan 17 19:30:11 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 17 19:30:11 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jan 17 19:30:11 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jan 17 19:30:11 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sun Jan 17 19:30:11 2016 [server] Peer Connection Initiated with [AF_INET]195.28.207.16:1194
Sun Jan 17 19:30:14 2016 AUTH: Received control message: AUTH_FAILED
Sun Jan 17 19:30:14 2016 SIGTERM[soft,auth-failure] received, process exiting

Je vais continuer à chercher pourquoi je n'arrive pas à etre authentifié.

Message par **loic** » 17 janv. 2016, 19:43

De ce que je vois ton jeedom a été créé le 2016-01-17 18:44:20 soit aujourd'hui il faut donc que tu attendes demain pour qu'il soit dans le DNS

Gorgluk · Message par **Gorgluk** » 17 janv. 2016, 19:48

Bonjour,
Je n’arrive toujours pas à me connecter

Message par **loic** » 17 janv. 2016, 19:53

Bonjour,
Je viens de vérifier au niveau du DNS, il n'y a pas de soucis de ce coté tu es bien sur le serveur 2 et tu as bien un compte dessus pour ton jeedom qui est actif

Gorgluk · Message par **Gorgluk** » 17 janv. 2016, 19:57

J'ai le DNS actif et démarré mais toujours pas d'adresse ip

Message par **loic** » 17 janv. 2016, 19:59

Si tu as toujours la meme log tu as soit un soucis sur le mot de passe soit un soucis sur le nom d'utilisateur

kouaw · Message par **kouaw** » 17 janv. 2016, 20:01

attention que on ne peut utiliser un pseudo du market comme nom

Envoyé de mon GT-I9300 en utilisant Tapatalk

Gorgluk · Message par **Gorgluk** » 17 janv. 2016, 20:03

J'ai rempli comme ça
Utilisateur : Configuration puis "Clef hardware"
MDP : sur le market "Mes jeedoms" puis mot de passe
J'ai sauvegardé et ensuite j'ai envoyé le certificat et j'ai resauvegardé
Peux-tu voir si j'ai les bons identifiants ?

Message par **loic** » 17 janv. 2016, 20:03

Non je vois pas tout ca, mais ouvre un ticket et je m'en occupe dessuite

gpqpptdp · Message par **gpqpptdp** » 17 janv. 2016, 20:24

loic a écrit :De ce que je vois ton jeedom a été créé le 2016-01-17 18:44:20 soit aujourd'hui il faut donc que tu attendes demain pour qu'il soit dans le DNS

Merci de cette précision , je vais attendre demain soir.

pir2d2 · Message par **pir2d2** » 18 janv. 2016, 17:14

salut,
j'ai l'impression d'être neuneu

. Je ne vois pas où mettre à jour les dépendances.
Dans les logs, ça me met "sudo: openvpn: command not found"
Merci.

Message par **loic** » 18 janv. 2016, 17:39

A oui du a ma mise a jour pour la v2 ca passe en auto mais sur les v1.... en ssh il faut faire :
sudo apt-get install -y openvpn

pir2d2 · Message par **pir2d2** » 18 janv. 2016, 17:42

OK dak. Je suis rassuré.
Je suis à distance. Je ferai ça quand je serai en local.
Merci. tchô.

billou02 · Message par **billou02** » 19 janv. 2016, 00:59

Bonjour a tous

Perso je n'y arrive pas.
Je suis en service pack Power et sur le serveur DNS 2. Debian sur machine dédiée Jeedom en 1.212.0.8

voici mes logs

Code : Tout sélectionner

19-01-2016 00:43:48 | info | Lancement openvpn : sudo openvpn --config /tmp/openvpn_125.ovpn >> /usr/share/nginx/www/jeedom/core/class/../../log/openvpn_DNS_Jeedom  2>&1 &
Tue Jan 19 00:43:48 2016 OpenVPN 2.3.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Dec  1 2014
Tue Jan 19 00:43:48 2016 library versions: OpenSSL 1.0.1k 8 Jan 2015, LZO 2.08
Tue Jan 19 00:43:48 2016 WARNING: file '/tmp/openvpn_auth_1THIpsOyPFuRDrFgJeH6ZUlXuGlR8t.conf' is group or others accessible
Tue Jan 19 00:43:48 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:43:48 2016 UDPv4 link local: [undef]
Tue Jan 19 00:43:48 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194
Tue Jan 19 00:44:48 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 00:44:48 2016 TLS Error: TLS handshake failed
Tue Jan 19 00:44:49 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 00:44:51 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:44:51 2016 UDPv4 link local: [undef]
Tue Jan 19 00:44:51 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194
Tue Jan 19 00:45:50 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 00:45:50 2016 TLS Error: TLS handshake failed
Tue Jan 19 00:45:50 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 00:45:52 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:45:52 2016 UDPv4 link local: [undef]
Tue Jan 19 00:45:52 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194
Tue Jan 19 00:46:53 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 00:46:53 2016 TLS Error: TLS handshake failed
Tue Jan 19 00:46:53 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 00:46:55 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:46:55 2016 UDPv4 link local: [undef]
Tue Jan 19 00:46:55 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194
Tue Jan 19 00:47:55 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 00:47:55 2016 TLS Error: TLS handshake failed
Tue Jan 19 00:47:55 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 00:47:57 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:47:57 2016 UDPv4 link local: [undef]
Tue Jan 19 00:47:57 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194
Tue Jan 19 00:48:57 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 00:48:57 2016 TLS Error: TLS handshake failed
Tue Jan 19 00:48:57 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 00:48:59 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:48:59 2016 UDPv4 link local: [undef]
Tue Jan 19 00:48:59 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194
Tue Jan 19 00:49:59 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 00:49:59 2016 TLS Error: TLS handshake failed
Tue Jan 19 00:49:59 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 00:50:01 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:50:01 2016 UDPv4 link local: [undef]
Tue Jan 19 00:50:01 2016 UDPv4 link remote: [AF_INET]195.28.207.18:1194

J'ai bien configuré Openvpn comme cité plus haut (login clef hard du jeedom a contrôler et mdp, celui sur le market, sur la ligne du jeedom en question).

Au grès de quelques lectures, j'ai trouvé un certif nommé ca-vpn.crt.
(D'ailleur, il serait bien de documenter ou se trouve le certif. aux dernières news sur ce post, il est censé être Ici mais je ne l'ai pas vu...)

Le mien viens d'ici

J'ai créé mon dns jeedom sous le plugin openvpn et sauvegardé puis uploadé le certif. par contre, je ne sais pas si ca a fonctionné.
Les logs me font penser que non...

Qu'en dites vous ?

EDIT 19/01/2016 : Tout est ok. encore un coup du /mode boulet.....
J'avais mis vpn2.jeedom.FR au lieu de vpn2.jeedom.COM

pir2d2 · Message par **pir2d2** » 19 janv. 2016, 09:24

salut,
Tu retrouve le certificat est sur le premier post. Tout y est expliqué et bien mis à jour (sauf l'install de openvpn en ligne de commande : sudo apt-get install -y openvpn)

Pour moi, donc, ça fonctionne bien maintenant. Je m'étais emmellé les pincettes entre vpn1.jeedom.com à mettre dans la config et moncodedns.dns1.jeedom.com

Merci Loïc.

gpqpptdp · Message par **gpqpptdp** » 19 janv. 2016, 10:11

Bonjour ,

J'ai eu une évolution dans mes logs

Code : Tout sélectionner


    Accueil
    Analyse
    Général
    Plugins

    10:08:24



Mon Jan 18 22:50:23 2016 OpenVPN 2.3.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Dec  1 2014
Mon Jan 18 22:50:23 2016 library versions: OpenSSL 1.0.1k 8 Jan 2015, LZO 2.08
Mon Jan 18 22:50:23 2016 WARNING: file '/tmp/openvpn_auth_D4GtHD4UXnAwV3EFPK41Jan0m3AfUR.conf' is group or others accessible
Mon Jan 18 22:50:23 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Mon Jan 18 22:50:23 2016 UDPv4 link local: [undef]
Mon Jan 18 22:50:23 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Mon Jan 18 22:50:23 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Jan 18 22:50:24 2016 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 Jan 18 22:50:24 2016 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 Jan 18 22:50:24 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jan 18 22:50:24 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jan 18 22:50:24 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jan 18 22:50:24 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jan 18 22:50:24 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Mon Jan 18 22:50:24 2016 [server] Peer Connection Initiated with [AF_INET]195.28.207.16:1194
Mon Jan 18 22:50:26 2016 TUN/TAP device tun0 opened
Mon Jan 18 22:50:26 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Mon Jan 18 22:50:26 2016 /sbin/ip link set dev tun0 up mtu 1500
Mon Jan 18 22:50:26 2016 /sbin/ip addr add dev tun0 local 10.9.3.245 peer 10.9.3.246
Mon Jan 18 22:50:26 2016 Initialization Sequence Completed
Mon Jan 18 23:50:24 2016 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 Jan 18 23:50:24 2016 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 Jan 18 23:50:24 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jan 18 23:50:24 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jan 18 23:50:24 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Jan 18 23:50:24 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Jan 18 23:50:24 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 00:03:44 2016 [server] Inactivity timeout (--ping-restart), restarting
Tue Jan 19 00:03:44 2016 SIGUSR1[soft,ping-restart] received, process restarting
Tue Jan 19 00:03:46 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 00:03:46 2016 UDPv4 link local: [undef]
Tue Jan 19 00:03:46 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 00:03:47 2016 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
Tue Jan 19 00:03:47 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 00:03:47 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 00:03:47 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 00:03:47 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 00:03:47 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 00:03:47 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 00:03:47 2016 [server] Peer Connection Initiated with [AF_INET]195.28.207.16:1194
Tue Jan 19 00:03:49 2016 Preserving previous TUN/TAP instance: tun0
Tue Jan 19 00:03:49 2016 NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device.
Tue Jan 19 00:03:49 2016 Closing TUN/TAP interface
Tue Jan 19 00:03:49 2016 /sbin/ip addr del dev tun0 local 10.9.3.245 peer 10.9.3.246
Tue Jan 19 00:03:50 2016 TUN/TAP device tun0 opened
Tue Jan 19 00:03:50 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Jan 19 00:03:50 2016 /sbin/ip link set dev tun0 up mtu 1500
Tue Jan 19 00:03:50 2016 /sbin/ip addr add dev tun0 local 10.9.3.239 peer 10.9.3.240
Tue Jan 19 00:03:50 2016 Initialization Sequence Completed
Tue Jan 19 01:03:48 2016 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
Tue Jan 19 01:03:48 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 01:03:48 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 01:03:48 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 01:03:48 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 01:03:48 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 01:03:48 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 02:03:48 2016 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
Tue Jan 19 02:03:48 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 02:03:49 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 02:03:49 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 02:03:49 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 02:03:49 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 02:03:49 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 03:03:49 2016 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
Tue Jan 19 03:03:49 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 03:03:49 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 03:03:49 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 03:03:49 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 03:03:49 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 03:03:49 2016 NOTE: --mute triggered...
Tue Jan 19 04:50:30 2016 8 variation(s) on previous 20 message(s) suppressed by --mute
Tue Jan 19 04:50:30 2016 [server] Inactivity timeout (--ping-restart), restarting
Tue Jan 19 04:50:30 2016 SIGUSR1[soft,ping-restart] received, process restarting
Tue Jan 19 04:50:32 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 04:50:52 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:51:12 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:51:37 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:52:02 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:52:27 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:52:52 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:53:17 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:53:42 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:54:07 2016 RESOLVE: Cannot resolve host address: vpn1.jeedom.com: No address associated with hostname
Tue Jan 19 04:54:22 2016 UDPv4 link local: [undef]
Tue Jan 19 04:54:22 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 04:54:22 2016 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
Tue Jan 19 04:54:22 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 04:54:22 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 04:54:22 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 04:54:22 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 04:54:22 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 04:54:22 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 04:54:22 2016 [server] Peer Connection Initiated with [AF_INET]195.28.207.16:1194
Tue Jan 19 04:54:25 2016 Preserving previous TUN/TAP instance: tun0
Tue Jan 19 04:54:25 2016 Initialization Sequence Completed
Tue Jan 19 05:04:25 2016 [server] Inactivity timeout (--ping-restart), restarting
Tue Jan 19 05:04:25 2016 SIGUSR1[soft,ping-restart] received, process restarting
Tue Jan 19 05:04:27 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 05:04:27 2016 UDPv4 link local: [undef]
Tue Jan 19 05:04:27 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 05:05:27 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 05:05:27 2016 TLS Error: TLS handshake failed
Tue Jan 19 05:05:27 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 05:05:29 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 05:05:29 2016 UDPv4 link local: [undef]
Tue Jan 19 05:05:29 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 05:06:29 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 05:06:29 2016 TLS Error: TLS handshake failed
Tue Jan 19 05:06:29 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 05:06:31 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 05:06:31 2016 UDPv4 link local: [undef]
Tue Jan 19 05:06:31 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 05:07:31 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 05:07:31 2016 TLS Error: TLS handshake failed
Tue Jan 19 05:07:31 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 05:07:33 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 05:07:33 2016 UDPv4 link local: [undef]
Tue Jan 19 05:07:33 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 05:08:33 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Tue Jan 19 05:08:33 2016 TLS Error: TLS handshake failed
Tue Jan 19 05:08:33 2016 SIGUSR1[soft,tls-error] received, process restarting
Tue Jan 19 05:08:35 2016 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 19 05:08:35 2016 UDPv4 link local: [undef]
Tue Jan 19 05:08:35 2016 UDPv4 link remote: [AF_INET]195.28.207.16:1194
Tue Jan 19 05:08:35 2016 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
Tue Jan 19 05:08:35 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 05:08:36 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 05:08:36 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 05:08:36 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 05:08:36 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 05:08:36 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 05:08:36 2016 [server] Peer Connection Initiated with [AF_INET]195.28.207.16:1194
Tue Jan 19 05:08:38 2016 Preserving previous TUN/TAP instance: tun0
Tue Jan 19 05:08:38 2016 Initialization Sequence Completed
Tue Jan 19 06:08:35 2016 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
Tue Jan 19 06:08:35 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 06:08:36 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 06:08:36 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 06:08:36 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 06:08:36 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 06:08:36 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 07:08:35 2016 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
Tue Jan 19 07:08:35 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 07:08:36 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 07:08:36 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 07:08:36 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 07:08:36 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 07:08:36 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 19 08:08:35 2016 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
Tue Jan 19 08:08:35 2016 VERIFY OK: depth=0, C=FR, ST=IDF, L=Paris, O=jeedom.com, OU=jeedom.com, CN=server, name=jeedom, emailAddress=postmaster@jeedom.com
Tue Jan 19 08:08:35 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 08:08:35 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 08:08:35 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 19 08:08:35 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 19 08:08:35 2016 NOTE: --mute triggered...

J'essaye de me connecter avec le lien obtenu depuis le market et que ce soit avec
https://xxxxxxxxx.dns.jeedom.com/
https://xxxxxxxxx.dns.jeedom.com/jeedom
J'obtiens " Tunnel xxxxxxxxx.dns.jeedom.com not found"

kouaw · Message par **kouaw** » 19 janv. 2016, 10:14

normal il faut passer par l'adresse https://nomvoulu.dnsX.jeedom.com ou X = le serveur DNS qui ta etait atribuer et non pas par les adresse que tu as test

gpqpptdp · Message par **gpqpptdp** » 19 janv. 2016, 10:46

Merci Kouaw , j'ai rajouté le 1 sur
https://xxxxxxxxx.dns.jeedom.com/jeedom et cela a fonctionné .

kouaw · Message par **kouaw** » 23 janv. 2016, 21:37

petit up pour les gens qui cherche un accès extérieur sécurisé !

Envoyé de mon GT-I9300 en utilisant Tapatalk

Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Re: Nouveau DNS jeedom

Qui est en ligne ?