Skip to content

Troubleshooting Manual

Michael-X-Net edited this page Feb 3, 2023 · 7 revisions

This page collects and organizes common fault "phenomena" and corresponding analysis and solutions.
You can search or search for the problems you encounter (Ctrl+F) on this page, and view the corresponding solutions.
Everyone is welcome to add their own problems and solutions.
Questions, bug reports, and suggestions about XX-Net can be posted in the issue area.

Indicator description

Note: This chapter lists the common "good indicators" and "bad indicators". Please check them against each other. When you issue an issue, you can explain which good indicators you have seen and which bad indicators. This helps developers and other users determine the cause of the problem.
These indicators involve status page and log page.
When posting an issue, it would be even better if you could attach complete status information and relevant log information.

Indicators representing "good news"

  • Able to circumvent the wall (although there are some problems), check the IP through the proxy and display it as a foreign address
  • Although there is a problem, the error message is different from before overcoming the wall (indicating that XX-Net has brought some changes, please find the specific error message in this article)
  • block stat in GAEProxy Status Information is displayed as OK (indicating that the network is unblocked)
  • The connect link in the GAEProxy status information is not 0,0 (indicating that it is already connected to the GAE server)
  • When you open a website outside the wall, you can see the words of the relevant URL in the log. (It means that XX-Net has received the proxy request from the browser)
  • The words "[DEBUG] create_ssl update [IP address] time:[time]" can be seen in the log (indicating that this IP is available)

Indicator representing "bad news"

  • Slow or unstable internet
  • The browser displays an error message (please find the specific error message title in this article)
  • GAEProxy Status Information shows the block stat as connect block (meaning there is a problem with the network)
  • The connect link in the GAEProxy status information is displayed as 0,0 (indicating that the GAE server has not been connected yet)
  • There are many words such as "[DEBUG] create_ssl [IP address] fail:timed out" in the log (indicating that this IP is unavailable)
  • There are many words like "[DEBUG] report_connect_fail network fail" in the log (indicating that there is a problem with the network)
  • "ssl handshake failure" appears in the log (probably certificate error)

Download, install, and deploy issues

Deployment failure

APPID in use

When deploying GAE, the appid is in use, causing the deployment to fail. Please refer to Deploy-fail-when-appid-in-useEN.

Enable weak security applications

When deployment fails, please check if you Lesssecure apps enabled.

password issue

When deploying, it prompts that the password is wrong, or other password-related issues. Please refer to Deploy password problemEn.
If you have enabled 2-step login authentication, you will need to set up app passwords.

Reauthorization

Please refer to reauthorization

Other deployment issues

You can also review and supplement other deployment issues at here.

Windows issues:

Linux and Mac system problems

Cannot run normally under Linux

XX-Net cannot run under Linux system, and the log shows:
"_start module gae_proxy fail: libssl.so.1.0.0: cannot open shared object file: No such file or directory _"
(See: issue #779 for an example)

This is because the OpenSSL that comes with XX-Net cannot work under some Linux. Execute the following command to install the system library:

  • Fedora
    sudo dnf install pyOpenSSL.noarch
  • CentOS
    sudo yum install pyOpenSSL

Missing module named pygtk

It may be that some systems do not come with this module. Such as Ubuntu, it can be solved by running the following command
sudo apt-get install -y python-gtk2
(See: issue #1381 for an example)

Run in pure terminal mode under Linux and report an error

For examples and solutions see: issue #715

[Problems during use](#Problems during use)

Network connection problem

Can bypass the firewall through the GAE module, but it displays "Please check the browser proxy settings"

https://zh.wikipedia.org/wiki/Help:Bypass browser cache

Intermittent, sometimes it can be turned over, sometimes the connection times out

The network speed is slow or unstable, sometimes it can be turned over, and sometimes it displays "Connection timed out, please take a break".
There are many words such as "create_ssl [IP address] fail:timed out" in the log.

It may be that you currently only have a few available IPs. Due to the influence of the "Google IP usage frequency limit" option, you will switch between IPs. When switching to an invalid IP, it cannot connect.

Please refer to: "Google IP usage frequency limit" option

XX-Net is running normally but cannot bypass the wall

When you open the blocked website, the browser displays "The page cannot be opened", which is the same as before breaking the wall. I can't find any records in the XX-Net logs related to the URL you opened, but there are other signs that XX-Net is running normally (see above: [Indicators for "good news"](https://github.com/XX-net/XX-Net/wiki/Troubleshooting Manual#Indicators representing "good news")).
(For an example, see: issue #749)

It's probably because you don't have a good proxy setup. See the article Setting Proxy.

Frequent encounters with man-machine verification (verification code)

If you frequently encounter verification codes while using Google, you can configure direct connection rules to improve. (Note: Configuring direct connection rules is not a perfect solution, and may cause other problems) The method is: Add in data/gae_proxy/manual.ini (if there is no such file, create a new one):

[hosts] .google.com = direct

Then restart GAE_proxy.

can't watch youtube

Add in data/gae_proxy/manual.ini (if there is no such file, create a new one):

[hosts] .youtube.com = gae

Garbled characters

IE/Safari and other browsers access youtube with garbled characters, because the website uses the Brotli compression algorithm.
This can be resolved by using a suitable browser http://caniuse.com/#feat=brotli.
A simple test browser is available

Unable to use google search

1

After the browser sets the proxy, install the ncr plugin

After closing XX-Net, the browser cannot access the Internet

After closing XX-Net, the browser shows that it cannot connect to the proxy server and cannot access the Internet. (See: issue #785 for an example)

Usually this problem comes from the browser's proxy settings. When the browser's proxy settings point to a certain address (such as XX-Net's 127.0.0.1:8087), but you close the software that provides the corresponding proxy, then it will fail to connect to the proxy server. The solution is to adjust the browser's proxy settings.

Reference: Install and use SwichySharpEN, Tray right-click menu, How to set proxy.

After opening XX-NET, the domestic website (directly connected) cannot be opened

Phenomenon:

  1. After opening XX-NET, after a while, the directly connected website (domestic website) cannot be accessed, while the website accessed through the proxy Station (foreign website), you can visit. If you let the domestic website also go through the proxy (that is, the global proxy), you can also access it.

  2. Other devices connected to the same router cannot access the network.

Method: The performance of the router is not good, try reducing the number of scanning threads (such as reducing to 5).

Source #1431

Stuck (sluggish computer response)

It may be caused by the high number of threads scanning IP in the background. Try setting the scanning thread to 1, click "Update".

[Certificate Questions] (#Certificate Questions)

When the browser opens the https:// link, an error is reported

The browser blocks access to the URL, displaying a warning text. To the effect that the identity of the website owner cannot be verified, server certificates cannot be trusted, security credentials are not reliable, etc.
The title of the error message is similar to:
"SSL error"
"Your link is not private"
"The site's security certificate is not trusted"
"This link is not trusted"
"There is a problem with this website's security certificate"
...

Please refer to:
Certificate Error

SSL handshake failed

"ssl handshake failure" appears in the log

Clone this wiki locally