No able to connect to aws-vpn from a windows10 VirtualBox in an Ubuntu Host

Question

Hi all,  
  
After discarding the possibility of connecting to AWS-VPN, configured with SAML Authentication  (OKTA), from my Ubuntu Box, my next solution is use a Windows VM (VirtualBox) as a router/bridge.  
  
Not sure if this can be done, but my 1st step, that ism connecting the Window VM to the VPN still not working.  
  
I follow instructions in amazon site:  
  
- Installed amazon vpn-client  
- Disabled windows firewall  
- Allow incoming traffic 1194 and 443 (udp/tcp) in the ubuntu host  
  
So the process starts well,  it shows me the Okta login in the browser,  and then get stuck in  
"Waiting for Identity".  
  
Looking at the log, I see this item repeated and repeated

```
2020-07-10 10:23:36.789 -07:00 [DBG] [TI=9] Process 6472 is owned by SYSTEM
2020-07-10 10:23:37.557 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:37 2020 us=556347 WE_CTL n=0 ev=000000000111D288 rwflags=0x0001 arg=0x0
2020-07-10 10:23:37.559 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:37 2020 us=559262 WE_WAIT enter n=1 to=1000
2020-07-10 10:23:37.559 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:37 2020 us=559262 [0] ev=0000000000000124 rwflags=0x0001 arg=0x0
2020-07-10 10:23:37.791 -07:00 [DBG] [TI=5] IsAlive method called
2020-07-10 10:23:37.834 -07:00 [DBG] [TI=5] Process 6472 is owned by SYSTEM
2020-07-10 10:23:38.568 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:38 2020 us=568870 WE_CTL n=0 ev=000000000111D288 rwflags=0x0001 arg=0x0
2020-07-10 10:23:38.569 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:38 2020 us=569984 WE_WAIT enter n=1 to=1000
2020-07-10 10:23:38.569 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:38 2020 us=569984 [0] ev=0000000000000124 rwflags=0x0001 arg=0x0
2020-07-10 10:23:38.836 -07:00 [DBG] [TI=9] IsAlive method called
2020-07-10 10:23:38.860 -07:00 [DBG] [TI=9] Process 6472 is owned by SYSTEM
2020-07-10 10:23:39.578 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:39 2020 us=578735 WE_CTL n=0 ev=000000000111D288 rwflags=0x0001 arg=0x0
2020-07-10 10:23:39.579 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:39 2020 us=579500 WE_WAIT enter n=1 to=1000
2020-07-10 10:23:39.581 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:39 2020 us=581527 [0] ev=0000000000000124 rwflags=0x0001 arg=0x0
2020-07-10 10:23:39.862 -07:00 [DBG] [TI=5] IsAlive method called
2020-07-10 10:23:39.886 -07:00 [DBG] [TI=5] Process 6472 is owned by SYSTEM
2020-07-10 10:23:40.591 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:40 2020 us=591988 WE_CTL n=0 ev=000000000111D288 rwflags=0x0001 arg=0x0
2020-07-10 10:23:40.591 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:40 2020 us=591988 WE_WAIT enter n=1 to=1000
2020-07-10 10:23:40.591 -07:00 [DBG] [TI=13] [6472] Fri Jul 10 10:23:40 2020 us=591988 [0] ev=0000000000000124 rwflags=0x0001 arg=0x0
2020-07-10 10:23:40.888 -07:00 [DBG] [TI=9] IsAlive method called
```

So not able to understand what the problem is,  
any help will be greatly appreciated.  
  
Thanks  
Tonio

Answer

Problem solved,  
  
File configuration issue, probably something to do with newlines or so, do not figure out what was the reason, but it work smoothly after getting de configuration back from inside windows.  
  
thanks, everyone that looked at this

Answer

I have exactly the same issue, but it intermittent. I was lucky to connect several times, but did not get the sequence what exactly make it works. Most of time it is NOT working.

Answer

The issue was caused by problems with ovpn configuration file, after getting a fresh version everything worked smoothly.

Answer

After a few more intents, and not sure exactly what was changed,  I finally  
got an AUTH_FAILED message from the okta site, see below the log.  
  
So the question now should be, why does Authentication Fail, if I can log to Okta  
from my Ubuntu host without any trouble ?  
  
Again, any help we'll be greatly welcome  
Thanks, tonio  
  
**UPDATE (jul-26):**  Just discovered I mispelled 1194 (wrote 1193) in port-forwarding configuration in Wifi-Router configuration, correct it and still getting se same error, hope this gives a clue on what is happening.

```
2020-07-22 07:12:03.799 -07:00 [DBG] [TI=11] [3872] Wed Jul 22 07:12:03 2020 us=795025 ACK reliable_send_timeout 604800 [5]
2020-07-22 07:12:03.799 -07:00 [DBG] [TI=11] [3872] Wed Jul 22 07:12:03 2020 us=795025 TLS: tls_process: timeout set to 57
2020-07-22 07:12:03.799 -07:00 [DBG] [TI=11] [3872] Wed Jul 22 07:12:03 2020 us=795025 TLS: tls_multi_process: i=1 state=S_INITIAL, mysid=ef105247 19cc985e, stored-sid=00000000 00000000, stored-ip=[AF_UNSPEC]
2020-07-22 07:12:03.799 -07:00 [DBG] [TI=11] [3872] Wed Jul 22 07:12:03 2020 us=795025 TLS: tls_multi_process: i=2 state=S_UNDEF, mysid=00000000 00000000, stored-sid=00000000 00000000, stored-ip=[AF_UNSPEC]
2020-07-22 07:12:03.799 -07:00 [DBG] [TI=11] [3872] Wed Jul 22 07:12:03 2020 us=795025 AUTH: Received control message: AUTH_FAILED,CRV1:R:instance-1/6852307300868160118/05882bae-333f-4013-830d-ca02de3020d9:b'Ti9B':https://vlocity.okta.com/app/aws_clientvpn/exk44adt6rxKtluq8357/sso/saml?SAMLRequest=fVPRbtowFH3vV0R5hziBktUCpAw0Da3bELA%2B7KVynMtq1bFT3xug%2B%2FrZgbZU6kgeIl3fc%2B45xzdjFLVueNHSg1nBUwtIV1F0qLVB3h1N4tYZbgUq5EbUgJwkXxffb3nWZ7xxlqy0On4HuowRiOBIWRNAi%2Fkkvpc5ZIwNtwDV8AZGg5JtIRNlPoJRNahu0jIVab7NRgFwBw49dhJ7qo4AsYWFQRKGfJFlrMfyXpZt0iFPM86y36Fr7n0pI6hDPhA1yJNkp61U9Ny3jyT60taJaJpE7PFeagWGdo1J4PA4HIqKRu7wjXT79GlwnSeINgk2A%2FHyFMBnZSpl%2Flx2Xh6bkH%2FdbJa95c%2F1JlAUL3nMrMG2BrcGt1MSfq1uj1q91DTL%2B8y%2FKR9cM5bGU4%2BLonFQwbsE3DQMFrX4aw3fQ4lHDuSvXsbJefcbvuE%2FvNDFfGm1ks9dPTxfrKsF%2Fd9P6rWEiqp6266VQy2ULqrKAWL8ylNobfczB4JgEpNrIY6Sd9NPWwdVt4M%2BA4IDRTNbN8IpDPcFByHpZPnN9nn7TPulWsF2enHvpA8jLB%2Fypf%2FsravC7YH0szdOGGyso1NKH5IfVScXZE%2BvXo7Pf6jpPw%3D%3D
20
```

Edited by: tjc on Jul 26, 2020 10:42 AM

No able to connect to aws-vpn from a windows10 VirtualBox in an Ubuntu Host

Relevant content