🛡️ VPN OpenVPN SSL for PC/Android (Pwedeng All Network)

Status
Not open for further replies.
586825
586827
586828


thanks ts working sa android 5.0 marshmallow galaxy note 3
586829
 
good day sir
sir bakit ayaw oi sa cp ku lumabas sinunod ku nman ung instruction eh and then nalito po ako s
question no.3. Import niyo yung ovpn config na pang android sa attachments sa OpenVPN. May lalabas na login credentials diyan, you can find them in this thread.
salamat po
 
good day sir
sir bakit ayaw oi sa cp ku lumabas sinunod ku nman ung instruction eh and then nalito po ako s
question no.3. Import niyo yung ovpn config na pang android sa attachments sa OpenVPN. May lalabas na login credentials diyan, you can find them in this thread.
salamat po
Dpende nalang sa payload na ginamit mo sir at sa signal nng area maging working yung no load. Working po sigurado yan pg nakaregister ka sa kahit anong promo. Import mo nlng yung config na pang ovpn for android tas gamitin mo account na binigay ni ts. ☺️
 
2019-04-04 12:43:53 official build 0.7.8 running on Xiaomi Redmi 5 (msm8953), Android 7.1.2 (N2G47H) API 25, ABI arm64-v8a, (Xiaomi/rosy/rosy:7.1.2/N2G47H/V9.2.3.0.NDAMIEK:user/release-keys)
2019-04-04 12:43:53 Building configuration…
2019-04-04 12:43:53 Network Status: CONNECTED LTE to MOBILE http.globe.com.ph
2019-04-04 12:43:53 OpenVPN core 3.2 (qa:d87f5bbc04)(icsopenvpn/v0.7.8-0-ga8d2d82c) android arm64 64-bit built on Feb 22 2019 13:59:24
2019-04-04 12:43:53 Copyright (C) 2012-2017 OpenVPN Inc. All rights reserved.
2019-04-04 12:43:53 Debug state info: CONNECTED LTE to MOBILE http.globe.com.ph, pause: userPause, shouldbeconnected: true, network: SHOULDBECONNECTED
2019-04-04 12:43:53 Debug state info: CONNECTED LTE to MOBILE http.globe.com.ph, pause: userPause, shouldbeconnected: true, network: SHOULDBECONNECTED
2019-04-04 12:43:53 Frame=512/2048/512 mssfix-ctrl=1250
2019-04-04 12:43:53 UNUSED OPTIONS
1 [verb] [4]
2 [connect-retry] [2] [300]
3 [resolv-retry] [60]
10 [nobind]
12 [persist-tun]
13 [preresolve]
14 [mute-replay-warnings]
16 [mute] [2]
17 [resolv-retry] [infinite]
2019-04-04 12:43:53 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:43:53 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:43:53 TCP recv error: Connection reset by peer
2019-04-04 12:43:53 Transport Error: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:43:53 EVENT(Error): TRANSPORT_ERROR: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:43:53 Client terminated, restarting in 5000 ms...
2019-04-04 12:43:58 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:43:58 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:43:58 TCP recv error: Connection reset by peer
2019-04-04 12:43:58 Transport Error: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:43:58 EVENT(Error): TRANSPORT_ERROR: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:43:58 Client terminated, restarting in 5000 ms...
2019-04-04 12:44:03 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:44:03 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:44:03 TCP recv error: Connection reset by peer
2019-04-04 12:44:03 Transport Error: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:03 EVENT(Error): TRANSPORT_ERROR: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:03 Client terminated, restarting in 5000 ms...
2019-04-04 12:44:08 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:44:08 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:44:08 TCP recv error: Connection reset by peer
2019-04-04 12:44:08 Transport Error: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:08 EVENT(Error): TRANSPORT_ERROR: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:08 Client terminated, restarting in 5000 ms...
2019-04-04 12:44:13 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:44:13 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:44:13 TCP recv error: Connection reset by peer
2019-04-04 12:44:13 Transport Error: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:13 EVENT(Error): TRANSPORT_ERROR: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:13 Client terminated, restarting in 5000 ms...
2019-04-04 12:44:18 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:44:18 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:44:18 TCP recv error: Connection reset by peer
2019-04-04 12:44:18 Transport Error: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:18 EVENT(Error): TRANSPORT_ERROR: Transport error on '127.0.0.1: NETWORK_RECV_ERROR
2019-04-04 12:44:18 Client terminated, restarting in 5000 ms...
2019-04-04 12:44:23 Contacting 127.0.0.1:8888 via TCPv4
2019-04-04 12:44:23 Connecting to [127.0.0.1]:8888 (127.0.0.1) via TCPv4
2019-04-04 12:44:23 TCP recv error: Connection reset by peer
2019-04-04 12:44:23 Transport Error: Transport erro
 
Status
Not open for further replies.

About this Thread

  • 539
    Replies
  • 27K
    Views
  • 283
    Participants
Last reply from:
Alice Schuberg

Online now

Members online
1,051
Guests online
1,140
Total visitors
2,191

Forum statistics

Threads
2,272,256
Posts
28,941,466
Members
1,237,118
Latest member
memalang
Back
Top