Question about replacing proxies.

[ByQwank]

I often buy 30 day proxies for Earnapp.
Does the program automatically delete/not run the containers if the proxies are not invalid?

After 30 days, is it safe just to remove those 10 from Proxies.txt, then adding another 10. and Start & stopping the script to get those URLS.
-Essentially letting the Earnapp URLS stack up in .txt (Which I dont mind)
But I just want to know best practices, so I dont have containers with invalid proxies for my farm.
Thank you

[ByQwank]

Went to add more proxes I purchased today. Stopped & started the containers again and got this message - Programs been running fine for weeks now.

it downloads about 5-20. then I get this error.

docker: error reponse from daemon: faied to create shim task: OCI runtime create failed: runc create failed: unable to create a new parent process: namespace path: lstat /proc/380309/ns/net: no such file or directory unknown

[engageub]

Went to add more proxes I purchased today. Stopped & started the containers again and got this message - Programs been running fine for weeks now.

it downloads about 5-20. then I get this error.

docker: error reponse from daemon: faied to create shim task: OCI runtime create failed: runc create failed: unable to create a new parent process: namespace path: lstat /proc/380309/ns/net: no such file or directory unknown

Hello,
Could you please let me know the number of containers already running on the host.

Common reason:
If the system has resource constraints (e.g., memory, CPU, or file descriptors), Docker may not be able to create the necessary namespaces. Check your system's resource usage and adjust limits if necessary.

Possible Causes and Solutions

1. Reboot the System

Sometimes, a system reboot can resolve issues where namespaces are not properly cleaned up or are in an invalid state. This can help clear any stale resources or locks.

To reboot your system:

sudo reboot

After rebooting, proceed with the following steps:

2. Check Docker and Kernel Compatibility

This error can happen if there is a mismatch between the Docker version and the kernel version you're using. Ensure that your Docker installation is up to date and is compatible with your system's kernel.

To check your Docker version:

docker --version

To check your kernel version:

uname -r

If you find that either is outdated, update them to the latest stable versions:

• Update Docker:

  sudo apt-get update && sudo apt-get upgrade docker.io
  

• Update your Linux kernel (method depends on your distribution).

3. Check for any Stale Docker Processes

Sometimes, leftover Docker processes can prevent the system from creating new namespaces correctly.

List any Docker-related processes:

ps aux | grep docker

Kill any orphaned Docker processes if needed:

sudo kill -9 <pid>

4. Check Docker's Network Configuration

There could be a problem with Docker's network setup (e.g., conflicting or missing network namespaces). Try restarting Docker's network or removing existing ones:

sudo systemctl restart docker

Or, reset Docker's network configurations (be cautious, this will remove your Docker networks and may disrupt ongoing containers):

sudo docker network prune

5. Reinstall Docker

If the problem persists, you can try uninstalling and reinstalling Docker. This can clear any potential configuration issues or corrupted Docker files.

To uninstall Docker:

sudo apt-get remove --purge docker-ce docker-ce-cli containerd.io docker.io

To reinstall Docker:

sudo apt-get update && sudo apt-get install docker.io

6. Check the System's Resource Limits

If the system has resource constraints (e.g., memory, CPU, or file descriptors), Docker may not be able to create the necessary namespaces. Check your system's resource usage and adjust limits if necessary.

7. Use a Different Runtime

The issue could also be related to the default runtime (runc) used by Docker. You could try switching to an alternative runtime like containerd or crun to see if that resolves the issue. You can configure this in the Docker daemon's settings.

For example, in /etc/docker/daemon.json:

{ "default-runtime": "crun" }

Then restart Docker:

sudo systemctl restart docker

Conclusion

Try these steps and see if the issue resolves.

Thank you

[engageub]

Hello,
The internetIncome script does not detect if the proxies are online or not.
You will have to update the proxies manually in proxies.txt file.
You have the option to delete (using --delete option) all the containers and update proxies and then start (using --start option) them.

However, if you wish to update only few proxies and start the containers, make sure to replace the proxies which are not working and leave the remaining in the same line number where there are.
The run sudo bash updateProxies.sh command to update the proxies.
The devices with same proxies earlier will not be affected but the devices with offline proxies will be updated with new online proxies.

Thank you

[engageub]

If your docker issue is still not resolved, please contact docker support team via the following link.
Please mention your docker forum link here after submitting the request.

https://forums.docker.com/

Thank you

[ByQwank]

Is it safe to leave blanks in Proxies.txt, untill I get proxies to replace those?

[engageub]

No. If you wish to replace proxies and have the same proxy for existing running containers, you should not leave blanks.
Blank lines are deleted and the script will not start as the number of proxies do not match the number of containers previously running.
Either you use sudo bash internetIncome.sh --delete to delete the containers and then start again or replace them with same number of proxies and use updateProxies.sh script.

Thank you

[Jampang99]

You can check the proxy on this site to see if it can be used in the script.

https://app.proxies.fo/

[ByQwank]

^ Tried & Tested Lol.
There are no compatible plans on Proxies.fo that will work & actually be profitable.

[Jampang99]

So from the proxy sites that I mentioned, they are not recommended... what about webshare?