مشکل اتصال در زمان استفاده مرورگر از افزونه های پروکسی

[Tebjox]

Attention | توجه

• [X] I searched and no similar issues were found | جستجو کردم و هیچ گزارش مشابهی پیدا نشد

What Happened? | چه اتفاقی افتاده؟

پس تغییر گزینه پیکربندی شبکه به "None" اگر در مرورگر از Extension هایی که پروکسی مرورگر را تغییر می دهند استفاده بشه وب سایت هایی مثل اینستاگرام، یوتوب، توییتر و ... لود نمی شوند. نمونه Extension : انواع Proxy Switcher و...

این مشکل هم در Chrome و هم در Firefox وجود دارد.

265

Minimal Reproducible Example | چه پروسه‌ای برای مشاهده این مشکل طی کرده‌اید؟

1. Change Network configuration to "None"
2. Click to connect.
3. Use any Proxy switcher Extensions and set Oblivion proxy port into Extensions.

Relevant log output | لاگ برنامه

[2024-06-29 20:04:04.882] [info]  past logs was deleted for new connection.
[2024-06-29 20:04:04.885] [info]  ------------------------MetaData------------------------
[2024-06-29 20:04:04.885] [info]  running on: win32 10.0.22000 x64
[2024-06-29 20:04:04.886] [info]  at od: 0.23.15-beta
[2024-06-29 20:04:04.886] [info]  at wp: v1.2.3
[2024-06-29 20:04:04.887] [info]  ls assets/bin: LICENSE,README.md,vbs,warp-plus.exe
[2024-06-29 20:04:04.887] [info]  method: gool
[2024-06-29 20:04:04.888] [info]  proxyMode: false
[2024-06-29 20:04:04.888] [info]  routingRules: Default
[2024-06-29 20:04:04.889] [info]  endpoint: custom
[2024-06-29 20:04:04.889] [info]  license: false
[2024-06-29 20:04:04.890] [info]  exe: C:\Users\<USERNAME>\AppData\Local\Programs\Oblivion Desktop\Oblivion Desktop.exe
[2024-06-29 20:04:04.890] [info]  userData: C:\Users\<USERNAME>\AppData\Roaming\oblivion-desktop
[2024-06-29 20:04:04.891] [info]  logs: C:\Users\<USERNAME>\AppData\Roaming\oblivion-desktop\logs
[2024-06-29 20:04:04.891] [info]  ------------------------MetaData------------------------
[2024-06-29 20:04:04.900] [info]  starting wp process...
[2024-06-29 20:04:04.901] [info]  C:\Users\<USERNAME>\AppData\Roaming\oblivion-desktop\warp-plus.exe --bind 127.0.0.1:8086 --gool --endpoint 162.159.192.36:908
time=2024-06-29T20:04:04.955+03:30 level=INFO msg="using warp endpoints" endpoints="[162.159.192.36:908 162.159.192.36:908]"
time=2024-06-29T20:04:04.955+03:30 level=INFO msg="running in warp-in-warp (gool) mode"

time=2024-06-29T20:04:04.956+03:30 level=INFO msg="successfully loaded warp identity" subsystem=warp/account

time=2024-06-29T20:04:14.922+03:30 level=INFO msg="connection test successful"

time=2024-06-29T20:04:14.923+03:30 level=INFO msg="successfully loaded warp identity" subsystem=warp/account

time=2024-06-29T20:04:16.268+03:30 level=INFO msg="connection test successful"

time=2024-06-29T20:04:16.268+03:30 level=INFO msg="serving proxy" address=127.0.0.1:8086

time=2024-06-29T20:04:16.342+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:04:16.492+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:04:16.791+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:04:16.791+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:04:31.950+03:30 level=WARN msg="read tcp 172.16.0.2:43250->149.154.167.91:443: i/o timeout" subsystem=vtun

time=2024-06-29T20:04:32.013+03:30 level=WARN msg="read tcp 127.0.0.1:8086->127.0.0.1:4631: i/o timeout" subsystem=vtun

time=2024-06-29T20:04:32.160+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:04:32.161+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:04:34.689+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:04:35.841+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:04:35.843+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:04:35.854+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:04:35.861+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:04:35.896+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:04:36.343+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:04:36.345+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:04:47.408+03:30 level=WARN msg="read tcp 127.0.0.1:8086->127.0.0.1:4645: i/o timeout" subsystem=vtun

time=2024-06-29T20:04:47.551+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:04:47.566+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:05:02.105+03:30 level=WARN msg="read tcp 172.16.0.2:36890->149.154.167.91:443: i/o timeout" subsystem=vtun

time=2024-06-29T20:05:02.775+03:30 level=WARN msg="read tcp 127.0.0.1:8086->127.0.0.1:4666: i/o timeout" subsystem=vtun

time=2024-06-29T20:05:02.903+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:05:02.917+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:05:10.830+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:05:10.832+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:05:13.643+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:14.572+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:14.577+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:14.581+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:14.584+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:14.590+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:14.592+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

time=2024-06-29T20:05:18.130+03:30 level=WARN msg="read tcp 127.0.0.1:8086->127.0.0.1:4672: i/o timeout" subsystem=vtun

time=2024-06-29T20:05:18.301+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:443

time=2024-06-29T20:05:18.316+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=149.154.167.91:80

time=2024-06-29T20:05:18.919+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=216.58.212.3:443

time=2024-06-29T20:05:18.946+03:30 level=INFO msg="handling connection" subsystem=vtun protocol=tcp destination=10.10.34.36:443

[ircfspace]

سلام داخل proxy-switcher با چه تنظیماتی اقدام به اتصال به warp-plus میکنین؟

[Tebjox]

سلام داخل proxy-switcher با چه تنظیماتی اقدام به اتصال به warp-plus میکنین؟

[Tebjox]

تا الان نوع پروکسی رو Socks5 قرار می دادم. ولی وقتی نوع رو HTTP قرار دادم مشکل به طور کامل برطرف شد. #265

لطفا به صورت Hint یا یک راهنما این مورد رو تو همون قسمت انتخاب Port ذکر کنید که پروکسی باید از نوع HTTP باشه که سایر افراد این اشتباه رو نکنند. متشکرم.

[ircfspace]

در رابطه با سایفون باید روی socks5 تنظیم بشه