VMware Workspace ONE Community
cyphil
Enthusiast
Enthusiast

Per app VPN

Hi,


Any expert here can advise how can I troubleshoot per-app VPN not connecting?


 


*Cloud AW


*AW tunnel (Server A) on-premise, proxy on port 2020, per app vpn on 443, internal web site port 80 (Server B)


*Telnet from device to (Server A) port 443: OK


*vpnd (listening 443) and proxy (listening 2020) services up


*Telnet from (Server A) to (Server B) 80: OK Device can connect to (Server B) internal site port 80 through VMware Browser: OK


*Device, Tunnel App installed, VPN profile installed, when per-app VPN get connected, 3 green ' ticks' .


*Device, can access to internal (Server B) through Safari domain, [VPN] sign on iOS turned on: OK


*Device per-app VPN to (Server B) internal site port 80 e.g. through telnet client failed, [VPN] sign on iOS turned on: NOT OK


*No hint from tunnel.log


 


Thx.


Philip

Labels (1)
Reply
0 Kudos
3 Replies
JimMalandruccol
Contributor
Contributor

Do you have debug on for vpnd logs?
For Linux Tunnel, edit the server.conf file in /opt/VMware/tunnel/vpnd. Change log_level to 4, restart vpnd service and recreate problem. Tunnel.log should then have more detailed information.
Reply
0 Kudos
LukeDC
Expert
Expert

If you're on 9.2 or later you can up your debugging from the console. editing the server.conf file doesn't work well as the airwatch service will revert it back after a period of time.  Logging can be changed here ' System > Enterprise Integration > VMware Tunnel'  and the per-app VPN settings are on the bottom of the page.
Reply
0 Kudos
cyphil
Enthusiast
Enthusiast

Thx guys.
It's cloud AW, 9.4.
I can see a lot of DEBUG log in tunnel.log, I supposed it is already in debug log level. However, couldn't find something vivid. I can see some ' regular'  ERROR log ' UDID mismatched' , but I think it may not be the root cause.
Anyway, will check if it's log_level 4 tmr when I can access to tunnel console.
Reply
0 Kudos