-
Notifications
You must be signed in to change notification settings - Fork 49
Frequently Asked Questions
If you wish to use proxies, you need to set the value of variable USE_PROXIES to true in properties.conf file.
Then, create a file name proxies.txt in the same folder you have internetIncome.sh file.
Add your proxies in each line in the format protocol://user:pass@ip:port or protocol://ip:port
Example proxies.txt file below.
socks5://username:[email protected]:7874
http://username:[email protected]:7878
socks5://15.4.5.2:7875
http://13.23.5.2:7872
For any other proxy format, please click here to format proxies.
Yes❗ You can use the script with a direct internet connection by setting the variable USE_PROXIES to false in properties.conf file. This is the default configuration when you download the script from the main branch.
If you are using test branch, you will have to set USE_DIRECT_CONNECTION to true in properties.conf file.
For multiple users to use the same host, simply create different folders, download the script in each folder, and set the configuration. It is recommended not to create multiple accounts for yourself.
To auto-update all containers on the host, run the following command.
sudo docker run --detach --name watchtower --restart always --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower
Please run the following command to delete all the running and stale containers on your host. The commands also delete stale docker images.
sudo docker container ls -a | awk '{print $1}' | xargs sudo docker rm -f
sudo docker system prune -f -a
🤔 Why is my IP address classified as non-residential by the application, despite it being a residential IP❓
Each application queries various services to determine whether an IP address is residential. However, these services may not always be aligned with the most current data. As a result, an IP address may occasionally be misclassified as non-residential.
If your proxies are working properly, ensure that your CPU usage remains below 80% and that you have enough available RAM. Otherwise, high CPU usage or insufficient RAM could cause the issue you are experiencing. In addition to this, the application website may also be throttling the requests either due to multiple authentication requests in a short period or the request may be timing out, etc.
Your DNS requests may also be throttled on the host. Set the value of USE_DNS_OVER_HTTPS to true in properties.conf to see if this resolves the issue. If you are using socks5 proxies that support DNS requests, set the value of USE_SOCKS5_DNS to true. To confirm if the issue is related to DNS queries, please run the following command to get the recent logs.
sudo journalctl -u docker.service --no-pager | tail -n 100
To view the docker service logs, please run the following command.
sudo journalctl -u docker.service --no-pager | less
If the issue is related to DNS queries and you are using proxies, then please use the test branch with DNS over HTTPS enabled.
If you are using a proxy instead of a direct connection, you may see the node online but no earnings. There is an ongoing issue here https://github.com/xjasonlyu/tun2socks/issues/262. However, note that Mysterium works with VPN and IP. Please use the test branch if you would like to use multiple VPNs or IPs. It is crucial to understand that the Mysterium node operates differently from other applications, as it necessitates the enabling of UDP (User Datagram Protocol). This protocol is essential for the proper functioning of the Mysterium node. In the case of utilizing SOCKS5 proxies, it is imperative to confirm with your provider whether UDP is enabled for your specific SOCKS5 proxy. When utilizing a direct internet connection, it is imperative to ensure that your firewall is configured to allow UDP traffic.
The data of your Mysterium keys is stored in the designated mysterium-data folder, located in the same directory as the script. It is crucial to note that the script does not remove or delete this folder, as it contains your private keys. Losing these keys would necessitate the payment for a new Mysterium node.
Therefore, it is imperative to exercise caution and ensure the safety and security of the mysterium-data folder, as it contains sensitive and valuable information. By taking appropriate measures to preserve and back up this data, you can mitigate the risk of potential loss and subsequent financial implications.
If your VPS does not have port restrictions to access your VPS IP globally, you can access your localhost URLs by replacing them with your VPS IP address. For example, if your VPS IP address is 2.4.75.2 and you wish to access your localhost URL http://127.0.0.1:2000, then replace the IP with your VPS IP to access it elsewhere. The URL to access directly using VPS IP would be http://2.4.75.2:2000.
If your VPS IP is not accessible globally, please run the following command to get the corresponding URL.
ssh -R 80:127.0.0.1:2000 serveo.net
An alternative is localhost.run, use this if serveo.net is busy.
ssh -R 80:127.0.0.1:2000 [email protected]
In the above command, 2000 represents the port number of your localhost or 127.0.0.1. For each browser instance, there is a separate port number. Please change the port number accordingly. You will receive a URL after running the above command which can be accessed globally.
The UUID or node IDs are required to identify your unique nodes in the Earnapp dashboard. These nodes are stored in the earnapp.txt file and are not deleted. The same node IDs will be used when you start the application again. You do not need to delete existing nodes in the dashboard and add them again when you use the --delete option. If you already have an existing node and would like to use it via the script you may add it in the earnapp.txt file in the same format as the existing file.
If you wish to use change proxies for already running containers due to bad proxies or proxies being offline, update them in proxies.txt and remove your old proxies. Make sure you have the same number of proxies as you had earlier in the proxies.txt file. Then run the following command.
sudo bash updateProxies.sh
For advanced users who wish to use multiple IPs or multiple VPNs, please use the test branch.
To utilize applications that involve installing browser extensions, use the test branch and set the CUSTOM_CHROME property to true in the properties.conf file.
This configuration will launch a browser with a new profile, allowing you to install extensions just as you would in a standard browser. You can also create multiple instances of the Chrome browser, each with different proxies. However, please note that managing credentials and installing extensions must be done manually.