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:password@12.4.5.2:7874
http://username:password@1.23.5.2:7878
socks5://15.4.5.2:7875
http://13.23.5.2:7872
ss://Y2hhY2hhMjAtaWV0Zi1wb2@15.4.5.2:19609

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.

This feature has been implemented in the test branch. To enable it, set the AUTO_UPDATE_CONTAINERS property to true in the properties.conf file. Once enabled, the system will automatically update all bandwidth-sharing container Docker images that use the latest tag. If you are using the main branch and wish to enable automatic updates for all containers on the host, run the following command:

sudo docker run -d --name watchtower --restart always --mount type=bind,source=/var/run/docker.sock,target=/var/run/docker.sock -e WATCHTOWER_CLEANUP=true --no-healthcheck ghcr.io/nicholas-fedor/watchtower:nightly

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

Please following command to install Docker or update the existing Docker version on the host:

sudo bash internetIncome.sh --install

Different applications rely on specific proxy intelligence services to determine IP details. Because these services may not always be synchronized or updated, the information shown can sometimes be inaccurate. You can verify the current classification of your IP using a tool such as:

https://check-host.net/ip-info?host=95.135.139.48

If the displayed information is incorrect, please contact the corresponding proxy service so they can update their records. Additionally, contact the support team for the application you are using and ask which proxy intelligence service they rely on for IP classification. Once confirmed, you can reach out to that service to have the details updated. If the application uses MaxMind, you can submit an IP correction using the following link:

https://www.maxmind.com/en/geoip-location-correction

To successfully run over 1,000 proxies (Docker containers or processes), your Linux system needs proper tuning for high concurrency, file descriptors, and network performance. Please follow the guide mentioned below:

🔗 Running 1000+ Proxies on Linux: Advanced Kernel Tuning Guide

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.

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 most likely reason is that you can only run one node per public IP address. When you try running multiple nodes on the same IP, only one gets accepted by the network while the others show as offline or monitoring failed. "Monitoring failed" status indicates network connection issues with your nodes. This could be related to NAT configuration, DNS issues, or firewall problems. To run multiple nodes successfully, each one needs its own unique public IP - either through separate routers with different IPs, different locations, or cloud providers.

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.

For Mysterium Nodes setup and initial payment, refer to: Accessing Mysterium Nodes for Initial Payment.

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

Please find the alternatives below if the above command does not work.

ssh -R 80:127.0.0.1:2000 nokey@localhost.run

ssh -p 443 -R0:127.0.0.1:2000 free.pinggy.io

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.

This feature is currently available only in the test branch with DNS_OVER_HTTPS enabled. 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

This feature is currently available only in the test branch. To start new applications after the script has already been launched, use the --startOnly parameter. This does not require adding configuration entries to the properties.conf file. Instead, the configuration must be passed via the command line. For example, if you want to start Bitping, retrieve the required configuration variable names from the properties.conf file. Make sure to use single quotes for the values, as shown below:

sudo bash internetIncome.sh --startOnly -e BITPING_EMAIL='your_email' -e BITPING_PASSWORD='your_password'

The limitation is that containers requiring exposed ports may not be accessible via IP:PORT, because those ports must be opened when the proxy container starts.

To determine whether a SOCKS5 proxy supports UDP, please refer to the following script repository and its accompanying README file. The repository includes the udpchk.py script along with usage instructions and example commands.

https://github.com/semigodking/socks5chk

For advanced users seeking to utilize multiple IPs or VPNs, please refer to the test branch. For detailed instructions on configuring VPNs, consult the Multi VPN Setup guide on the wiki.

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.