Impossible de se connecter au serveur - Mac, Ubuntu mais pas Windows
Bonjour,
J'ai un problème assez particulier je pense. Je suis obligé dans ma résidence de souscrire à un abonnement internet qui passe par un roxy. Ce proxy bloque les protocoles imap, pop, smtp et ssh (ce qui est trèèèèès embêtant pour moi, particulièrement le dernier).
Je possède un mac et un ordinateur fixe avec deux systèmes d'exploitations (Winddows 10 et Ubuntu). FrozenWay focntionne très bien pour Windows mais pas pour le mac ni Ubuntu. J'ai soit une latence supérieure à une seconde, soit une erreur du type : Impossible de se connecter au serveur. Veuillez essayer un autre serveur ou un autre protocole.
J'ai essayé de comparer au maximum les différentes configurations proxy entre le windows, ubuntu et le mac mais je ne vois pas de différence qui pourrait causer un tel problème.
Des idées ?
Merci d'avance,
Antonin.
Voici le journal de connexion pour le mac :
FrozenWay version 1.6.6
----------------------------------
Server: public-01-fr-01
Protocol: OpenVPN
----------------------------------
Sun Jun 17 01:15:03 2018 OpenVPN 2.2.1 i386-apple-darwin10.8.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Aug 10 2012
Sun Jun 17 01:15:03 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sun Jun 17 01:15:03 2018 WARNING: file '/Applications/FrozenWay.app/Contents/MacOS/../Resources/auth.key' is group or others accessible
Sun Jun 17 01:15:03 2018 Control Channel Authentication: using '/Applications/FrozenWay.app/Contents/MacOS/../Resources/auth.key' as a OpenVPN static key file
Sun Jun 17 01:15:03 2018 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jun 17 01:15:03 2018 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jun 17 01:15:03 2018 LZO compression initialized
Sun Jun 17 01:15:03 2018 Control Channel MTU parms [ L:1544 D:168 EF:68 EB:0 ET:0 EL:0 ]
Sun Jun 17 01:15:03 2018 Socket Buffers: R=[131072->65536] S=[131072->65536]
Sun Jun 17 01:15:03 2018 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Jun 17 01:15:03 2018 Local Options hash (VER=V4): '863ad621'
Sun Jun 17 01:15:03 2018 Expected Remote Options hash (VER=V4): '64e96fc1'
Sun Jun 17 01:15:03 2018 Attempting to establish TCP connection with 87.98.166.29:443 [nonblock]
Sun Jun 17 01:15:06 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:08 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:10 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:12 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:14 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:16 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:18 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:20 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:22 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:26 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:28 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:30 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:32 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:34 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:36 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:38 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:40 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:42 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:44 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:46 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:48 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:50 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:52 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:55 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:57 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:59 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:01 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:03 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:05 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:05 2018 SIGTERM[hard,init_instance] received, process exiting
J'ai un problème assez particulier je pense. Je suis obligé dans ma résidence de souscrire à un abonnement internet qui passe par un roxy. Ce proxy bloque les protocoles imap, pop, smtp et ssh (ce qui est trèèèèès embêtant pour moi, particulièrement le dernier).
Je possède un mac et un ordinateur fixe avec deux systèmes d'exploitations (Winddows 10 et Ubuntu). FrozenWay focntionne très bien pour Windows mais pas pour le mac ni Ubuntu. J'ai soit une latence supérieure à une seconde, soit une erreur du type : Impossible de se connecter au serveur. Veuillez essayer un autre serveur ou un autre protocole.
J'ai essayé de comparer au maximum les différentes configurations proxy entre le windows, ubuntu et le mac mais je ne vois pas de différence qui pourrait causer un tel problème.
Des idées ?
Merci d'avance,
Antonin.
Voici le journal de connexion pour le mac :
FrozenWay version 1.6.6
----------------------------------
Server: public-01-fr-01
Protocol: OpenVPN
----------------------------------
Sun Jun 17 01:15:03 2018 OpenVPN 2.2.1 i386-apple-darwin10.8.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Aug 10 2012
Sun Jun 17 01:15:03 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sun Jun 17 01:15:03 2018 WARNING: file '/Applications/FrozenWay.app/Contents/MacOS/../Resources/auth.key' is group or others accessible
Sun Jun 17 01:15:03 2018 Control Channel Authentication: using '/Applications/FrozenWay.app/Contents/MacOS/../Resources/auth.key' as a OpenVPN static key file
Sun Jun 17 01:15:03 2018 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jun 17 01:15:03 2018 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jun 17 01:15:03 2018 LZO compression initialized
Sun Jun 17 01:15:03 2018 Control Channel MTU parms [ L:1544 D:168 EF:68 EB:0 ET:0 EL:0 ]
Sun Jun 17 01:15:03 2018 Socket Buffers: R=[131072->65536] S=[131072->65536]
Sun Jun 17 01:15:03 2018 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Jun 17 01:15:03 2018 Local Options hash (VER=V4): '863ad621'
Sun Jun 17 01:15:03 2018 Expected Remote Options hash (VER=V4): '64e96fc1'
Sun Jun 17 01:15:03 2018 Attempting to establish TCP connection with 87.98.166.29:443 [nonblock]
Sun Jun 17 01:15:06 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:08 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:10 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:12 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:14 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:16 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:18 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:20 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:22 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:26 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:28 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:30 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:32 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:34 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:36 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:38 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:40 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:42 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:44 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:46 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:48 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:50 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:52 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:55 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:57 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:15:59 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:01 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:03 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:05 2018 TCP: connect to 87.98.166.29:443 failed, will try again in 1 seconds: Connection refused
Sun Jun 17 01:16:05 2018 SIGTERM[hard,init_instance] received, process exiting
Connectez-vous ou Inscrivez-vous pour répondre.
Réponses
Il y a un problème de configuration du proxy sous mac et linux. Ce sera mis à jour dans la prochaine version qui arrive bientôt. Désolé pour la gêne occasionnée.