What's new

ovpn FAST AND LOWPING SINGAPORE SERVER FOR GIGASTORIES, GIGAGAMES/ML10/GAMETIME, GTM PROMO, GIGAVIDEO AND COD & WILDRIFT PROMO

The Zohan said:
Salamat lods 💜may unli stories ka na config po?
Click to expand...
Pakitry nalang po yan sa unlistories po

bLueLite said:
thanks po lods
Click to expand...
Welcome po

H3nt41 said:
Thanks po
Click to expand...
Welcome

Ryster said:
Gigastories not connecting
Click to expand...
Patingin nga po ng log

errot13 said:
salamat
Click to expand...
Welcome po

rendezvous17 said:
many thanks po sa share boss
Click to expand...
Feedback po

Zhenxs said:
salamat po
pero yung gigastories kumakain ng shareable🥺
Click to expand...
Wehhh?? Sige po maghunt lang ako new payload
 
RaizerRTX said:
Pakitry nalang po yan sa unlistories po


Welcome po


Welcome


Patingin nga po ng log


Welcome po


Feedback po


Wehhh?? Sige po maghunt lang ako new payload
Click to expand...
Ito po

22:40:30.497 -- ----- OpenVPN Start -----

22:40:30.498 -- EVENT: CORE_THREAD_ACTIVE

22:40:30.502 -- OpenVPN core 3.git::662eae9a:Release android arm64 64-bit PT_PROXY

22:40:30.506 -- Frame=512/2048/512 mssfix-ctrl=1250

22:40:30.517 -- UNUSED OPTIONS
2 [persist-tun]
6 [persist-remote-ip]
7 [resolv-retry] [infinite]
8 [connect-retry] [0] [1]
10 [nobind]
12 [keysize] [0]
13 [rcvbuf] [0]
14 [sndbuf] [0]
15 [verb] [2]
18 [auth-nocache]

22:40:30.517 -- EVENT: RESOLVE

22:40:30.521 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:30.522 -- EVENT: WAIT_PROXY

22:40:31.528 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:31.530 -- Client terminated, restarting in 2000 ms...

22:40:33.529 -- EVENT: RECONNECTING

22:40:33.538 -- EVENT: RESOLVE

22:40:33.543 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:33.545 -- EVENT: WAIT_PROXY

22:40:34.561 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:34.562 -- Client terminated, restarting in 2000 ms...

22:40:36.561 -- EVENT: RECONNECTING

22:40:36.577 -- EVENT: RESOLVE

22:40:36.586 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:36.588 -- EVENT: WAIT_PROXY

22:40:37.597 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:37.600 -- Client terminated, restarting in 2000 ms...

22:40:39.597 -- EVENT: RECONNECTING

22:40:39.602 -- EVENT: RESOLVE

22:40:39.607 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:39.609 -- EVENT: WAIT_PROXY

22:40:40.605 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:40.606 -- Client terminated, restarting in 2000 ms...

22:40:42.605 -- EVENT: RECONNECTING

22:40:42.611 -- EVENT: RESOLVE

22:40:42.615 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:42.617 -- EVENT: WAIT_PROXY

22:40:43.613 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:43.614 -- Client terminated, restarting in 2000 ms...

22:40:45.613 -- EVENT: RECONNECTING

22:40:45.620 -- EVENT: RESOLVE

22:40:45.630 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:45.631 -- EVENT: WAIT_PROXY

22:40:46.639 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:46.642 -- Client terminated, restarting in 2000 ms...

22:40:48.640 -- EVENT: RECONNECTING

22:40:48.644 -- EVENT: RESOLVE

22:40:48.649 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:48.650 -- EVENT: WAIT_PROXY

22:40:49.645 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:49.647 -- Client terminated, restarting in 2000 ms...

22:40:51.646 -- EVENT: RECONNECTING

22:40:51.661 -- EVENT: RESOLVE

22:40:51.667 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:51.669 -- EVENT: WAIT_PROXY

22:40:52.665 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:52.666 -- Client terminated, restarting in 2000 ms...

22:40:54.665 -- EVENT: RECONNECTING

22:40:54.674 -- EVENT: RESOLVE

22:40:54.689 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:54.691 -- EVENT: WAIT_PROXY

22:40:55.689 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:55.690 -- Client terminated, restarting in 2000 ms...

22:40:57.690 -- EVENT: RECONNECTING

22:40:57.694 -- EVENT: RESOLVE

22:40:57.700 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:40:57.702 -- EVENT: WAIT_PROXY

22:40:58.697 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:40:58.698 -- Client terminated, restarting in 2000 ms...

22:41:00.696 -- EVENT: RECONNECTING

22:41:00.699 -- EVENT: RESOLVE

22:41:00.713 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:00.715 -- EVENT: WAIT_PROXY

22:41:01.709 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:01.711 -- Client terminated, restarting in 2000 ms...

22:41:03.713 -- EVENT: RECONNECTING

22:41:03.720 -- EVENT: RESOLVE

22:41:03.729 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:03.730 -- EVENT: WAIT_PROXY

22:41:04.729 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:04.730 -- Client terminated, restarting in 2000 ms...

22:41:06.729 -- EVENT: RECONNECTING

22:41:06.734 -- EVENT: RESOLVE

22:41:06.739 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:06.740 -- EVENT: WAIT_PROXY

22:41:07.742 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:07.745 -- Client terminated, restarting in 2000 ms...

22:41:09.741 -- EVENT: RECONNECTING

22:41:09.753 -- EVENT: RESOLVE

22:41:09.757 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:09.758 -- EVENT: WAIT_PROXY

22:41:10.753 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:10.754 -- Client terminated, restarting in 2000 ms...

22:41:12.753 -- EVENT: RECONNECTING

22:41:12.757 -- EVENT: RESOLVE

22:41:12.761 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:12.762 -- EVENT: WAIT_PROXY

22:41:13.765 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:13.767 -- Client terminated, restarting in 2000 ms...

22:41:15.765 -- EVENT: RECONNECTING

22:41:15.773 -- EVENT: RESOLVE

22:41:15.780 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:15.781 -- EVENT: WAIT_PROXY

22:41:16.781 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:16.783 -- Client terminated, restarting in 2000 ms...

22:41:18.781 -- EVENT: RECONNECTING

22:41:18.788 -- EVENT: RESOLVE

22:41:18.793 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:18.795 -- EVENT: WAIT_PROXY

22:41:19.797 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:19.798 -- Client terminated, restarting in 2000 ms...

22:41:21.797 -- EVENT: RECONNECTING

22:41:21.802 -- EVENT: RESOLVE

22:41:21.811 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:21.813 -- EVENT: WAIT_PROXY

22:41:22.821 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:22.822 -- Client terminated, restarting in 2000 ms...

22:41:24.821 -- EVENT: RECONNECTING

22:41:24.829 -- EVENT: RESOLVE

22:41:24.838 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:24.839 -- EVENT: WAIT_PROXY

22:41:25.837 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:25.839 -- Client terminated, restarting in 2000 ms...

22:41:27.836 -- EVENT: RECONNECTING

22:41:27.841 -- EVENT: RESOLVE

22:41:27.845 -- Contacting 128.199.150.166:8000 via HTTP Proxy

22:41:27.846 -- EVENT: WAIT_PROXY

22:41:28.861 -- Transport Error: TCP connect error on '128.199.150.166:8000' (128.199.150.166:8000) for TCP-via-HTTP-proxy session: Connection refused

22:41:28.863 -- Client terminated, restarting in 2000 ms...

22:41:30.520 -- EVENT: CONNECTION_TIMEOUT

22:41:30.527 -- EVENT: DISCONNECTED

22:41:30.528 -- Tunnel bytes per CPU second: 0

22:41:30.529 -- ----- OpenVPN Stop -----
 

Similar threads

Popular Tags

android cloudfront custom data ehi fast freenet giga games giga stories gigastories hpi http http custom http injector injector ktr load ml10 modem no block no blocking no load noload open tunnel ovpn payload ph server promo proxy server sg server smart smart & tnt sim sts sts no load sts noload sun sun & smart sun ehi surfsaya talk 'n text talkntext tiktok tnt unli unli data unli tiktok unlidata update vpn

About this Thread

  • 106
    Replies
  • 2K
    Views
  • 74
    Participants
Last reply from:
L A G

New Topics

Popular On This Forum

Online statistics

Members online
1,144
Guests online
5,890
Total visitors
7,034
Back
Top