Problème sur mac

Bonjour,

Je n'arrive pas à mconnecter en utilisant Frozenway sur mon Mac OS. Par contre, ça marche bien dans le système Windows de mon Mac.

Ça affiche: Impossible de se connecter au serveur. Veuillez essayer un autre serveur ou un autre protocole.

Comment je peux régler ce problème? Dans mon mac j'ai déjà utilisé un proxy automatique de type url qui est fourni par l'université. Sans cela, je ne peux pas connecter au fronzenway.

Merci

FrozenWay version 1.6.6
----------------------------------
Server: premium-01-fr-01
Protocol: OpenVPN
----------------------------------
Tue Sep 26 13:11:50 2017 OpenVPN 2.2.1 i386-apple-darwin10.8.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Aug 10 2012

Tue Sep 26 13:11:50 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

Tue Sep 26 13:11:50 2017 WARNING: file '/Applications/FrozenWay.app/Contents/MacOS/../Resources/auth.key' is group or others accessible

Tue Sep 26 13:11:50 2017 Control Channel Authentication: using '/Applications/FrozenWay.app/Contents/MacOS/../Resources/auth.key' as a OpenVPN static key file
Tue Sep 26 13:11:50 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Sep 26 13:11:50 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Sep 26 13:11:50 2017 LZO compression initialized
Tue Sep 26 13:11:50 2017 Control Channel MTU parms [ L:1544 D:168 EF:68 EB:0 ET:0 EL:0 ]

Tue Sep 26 13:11:50 2017 Socket Buffers: R=[131072->65536] S=[131072->65536]
Tue Sep 26 13:11:50 2017 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]

Tue Sep 26 13:11:50 2017 Local Options hash (VER=V4): '863ad621'
Tue Sep 26 13:11:50 2017 Expected Remote Options hash (VER=V4): '64e96fc1'
Tue Sep 26 13:11:50 2017 Attempting to establish TCP connection with 217.182.34.220:443 [nonblock]

Tue Sep 26 13:11:51 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:11:53 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:11:55 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:11:57 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:11:59 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:01 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:03 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:05 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:12 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:14 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:16 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:18 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:20 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:22 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:24 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:26 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:28 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:30 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:32 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:34 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:36 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:38 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:40 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:42 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:44 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:46 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:48 2017 TCP: connect to 217.182.34.220:443 failed, will try again in 1 seconds: Connection refused

Tue Sep 26 13:12:50 2017 TCP/UDP: Closing socket
Tue Sep 26 13:12:50 2017 SIGTERM[hard,init_instance] received, process exiting

Réponses

  • Salut,

    Connecte-toi depuis Windows, tu verras une ligne "Proxy" apparaître en haut du journal de connexion. Copie l'adresse IP/nom de domaine et le port et entre les dans les options de connexion de FrozenWay sur mac, dans proxy HTTP manuel.
  • Salut,

    J'ai essayé, malheureusement, ça ne marche pas.
  • septembre 2017 modifié
    Donne le journal de connexion à FrozenWay du mac avec le proxy configuré manuellement stp.
Connectez-vous ou Inscrivez-vous pour répondre.