Appears to be censored in Russia: 4.99.17, Android

Geph tech support / 迷雾通技术支持
1

Later edit: all of the below is, so far, incorrect again. Apparently they completed another round of tests.

Starting midnight today, 2+ hours ago. The connection gets established, but then it interrupts, reestablishes, and so on, in an endless loop. Here, an excerpt from the log. All gates are affected, including premium ones, except somehow Zurich. The resulting quality is abysmal: no pages open at all, and Chrome constantly reacts with a 'network change' error.

Coincides with other network problems which spiked in my region at the same time, so likely another round of DPI censorship. For example they also hurt legit Telegram traffic which works poorly even without VPN.

2024-11-13T23:14:30 [DEBG]: requiring full authentication server="15.235.15.156:21157"
2024-11-13T23:14:35 [DEBG]: authentication done, starting mux system elapsed=6.448647693s
2024-11-13T23:14:35 [INFO]: proxy_loop; instance=10 server=15.235.15.156:21157
2024-11-13T23:14:35 [DEBG]: opening tunnel remote_addr=tcp$149.154.167.51:443
2024-11-13T23:14:36 [WARN]: individual client thread failed err=inner connection to 15.235.15.156:21157 failed Caused by: ping-pong timed out
2024-11-13T23:14:36 [DEBG]: authentication done, starting mux system elapsed=6.638996923s
2024-11-13T23:14:36 [INFO]: proxy_loop; instance=11 server=15.235.15.156:21157
2024-11-13T23:14:37 [DEBG]: dial completed elapsed=341.966384ms protocol="tcp"

1 个赞
2

Can confirm, impossible to connect to any of the free servers in Europe, CA / Montreal still works.
Hard to tell if it's just the Russian 'sovereign internet' problem though, since network load is also all on that Canadian server at 90%, with Euro ones only having 20-30% each.

3

不就是用户自身人为选择的结果？

4

不就是用户自身人为选择的结果？

Well yes, it's just that usually the EU servers for free accounts were always at around 80% capacity during their day time, but for a few weeks now are all at the same 20-30% capacity no matter the time I check them, and Canada is overloaded at 90%. Hence why I'm guessing it's not specifically a Russian region problem.

5

image
image
image
image
image

image
image398×829 42.9 KB

image

6

Thanks for checking, on my end Poland server have started to work again (most of the time), but Amsterdam and Paris still get these messages repeating in the log while trying to re-authenticate:

2024-11-21T17:xx:xx [DEBG]: calling broker through http method="get_free_exits"
2024-11-21T17:xx:xx [DEBG]: deprioritizing route addr=51.158.203.70:20195
2024-11-21T17:xx:xx [WARN]: individual client thread failed err=overall dial/mux/auth timeout
7

敝人并非码农。。。
试试：
1、在程序设置的“排除应用程序”下，尽可能将非明确需要代理的程序全部勾选上。
2、记住迷雾通账户与密码，关闭程序，清空该程序的缓存或数据后再次启动。
I am not a coder. . .
Try:

  1. Under "Exclude Applications" in the program settings, check all programs that do not explicitly require agents as much as possible.
  2. Remember the Miwutong account and password, close the program, clear the cache or data of the program and start it again.
  3. Routing Mode: Bridges
9

Try setting the routing mode to bridges in settings!

Geph has two routing modes: directly connect to exits (like other vpns) or connect to exits through an extra hop, called a bridge. Bridges are constantly switched out to prevent getting blocked. In countries with heavy censorship, Geph should always automatically choose to use bridges. Currently if a user is in China or Iran (sophisticated censorship) Geph automatically forces using bridges.

However sometimes when a censor in another country doesn't blacklist exits but instead dynamically detects whether a connection is a VPN connection and cuts it off after a few seconds, Geph can have this bug: a direct connection (not using bridges) gets established, and Geph chooses to use this connection, but then the ISP interrupts the connection and Geph gets stuck. This is a bug.

If turning on force bridges fixes the issue, we're gonna add Russia to the list of countries where Geph always forces bridges

1 个赞
10

如果 Routing Mode: Auto
可能 Protocal: client-exit

11

Try setting the routing mode to bridges in settings!

Changing routing to Bridges worked! I looked at that setting before but only having "Auto" and "Bridges" as options for some reason made me think that the latter is the only option and so I didn't touch it, haha

12