Ebesucher

[mrjkjxyz]

After running the Ebesucher container, can it only be accessed via http://127.0.0.1:3000/? How can I access it using the public IP of my VPS?

[engageub]

Hello,
Could you please follow this FAQ on how to access the URLs outside the VPS.

https://github.com/engageub/InternetIncome/wiki/Frequently-Asked-Questions#-how-to-access-127001-urls-if-gui-is-not-available-in-linux-

Thank you

[engageub]

Hello,
These are common log messages. You will need to access the 127.0.0.1 URLs using the mentioned methods to see if the surfbar is working fine or you can login to your ebesucher dashboard and check your earnings.

Thank you

[mrjkjxyz]

Is the following VPS configuration acceptable?
top - 05:57:01 up 1 day, 15:50, 7 users, load average: 0.08, 0.14, 0.56
Tasks: 133 total, 2 running, 131 sleeping, 0 stopped, 0 zombie
%Cpu(s): 36.1 us, 9.4 sy, 0.0 ni, 53.8 id, 0.0 wa, 0.0 hi, 0.3 si, 0.3 st
MiB Mem : 981.2 total, 71.7 free, 396.1 used, 513.4 buff/cache
MiB Swap: 4608.0 total, 4568.5 free, 39.5 used. 432.1 avail Mem

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND  

104686 911 20 0 1160.2g 206996 146740 S 27.8 20.6 0:38.89 chromium
104611 911 20 0 33.0g 172384 115792 S 6.3 17.2 0:14.32 chromium
104666 911 20 0 32.8g 92900 62260 S 4.0 9.2 0:18.37 chromium
104668 911 20 0 32.6g 88316 70840 S 3.3 8.8 0:03.98 chromium
104118 root 20 0 1234772 8368 3980 S 1.7 0.8 0:03.22 tun2soc+
104211 root 20 0 1238244 10432 7076 S 0.7 1.0 0:00.95 contain+
105214 root 20 0 12240 4056 3336 R 0.7 0.4 0:00.70 top
10 root 20 0 0 0 0 R 0.3 0.0 0:38.72 rcu_sch+
8468 root 20 0 1875276 16312 5004 S 0.3 1.6 3:49.32 contain+
90167 root 20 0 0 0 0 I 0.3 0.0 0:02.40 kworker+
104511 911 20 0 334888 37152 17796 S 0.3 3.7 0:02.57 Xvnc
104755 911 20 0 1160.1g 107300 84384 S 0.3 10.7 0:00.63 chromium
105061 root 20 0 0 0 0 I 0.3 0.0 0:00.50 kworker+
1 root 20 0 168292 5152 2336 S 0.0 0.5 0:28.49 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.03 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par+

[mrjkjxyz]

xjasonlyu/tun2socks:v2.5.2 logs

time="2025-02-08T06:00:10Z" level=debug msg="[UDP] copy data for remote->origin: read udp [::]:56335: use of closed network connection"
time="2025-02-08T06:00:10Z" level=debug msg="[UDP] copy data for remote->origin: read udp [::]:47516: use of closed network connection"
time="2025-02-08T06:00:10Z" level=debug msg="[UDP] copy data for remote->origin: read udp [::]:52438: use of closed network connection"
time="2025-02-08T06:00:20Z" level=warning msg="[UDP] dial 142.251.163.99:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:00:20Z" level=warning msg="[UDP] dial 142.251.163.99:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:00:22Z" level=warning msg="[UDP] dial 142.251.163.99:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:00:24Z" level=warning msg="[UDP] dial 142.251.163.99:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:00:57Z" level=warning msg="[TCP] dial 67.207.73.141:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:00:57Z" level=warning msg="[TCP] dial 67.207.73.141:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:01:15Z" level=warning msg="[TCP] dial 67.207.73.141:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection refused"
time="2025-02-08T06:01:15Z" level=warning msg="[TCP] dial 67.207.73.141:443: connect to 109.121.37.234:10589: dial tcp 109.121.37.234:10589: connect: connection ref

[engageub]

Hello,

Based on the logs, it appears that UDP connections are being initiated through the container, but your proxy does not support UDP. To isolate the issue, please try establishing a direct connection first and then use the proxy to confirm whether the problem is related to the proxy configuration.

Additionally, your host has 1 GB of RAM with approximately 4 GB of swap space. Such a configuration may result in slow performance. Please note that containers running browsers typically consume significantly more CPU and memory compared to other applications.

From my experience, running a browser inside a container on a VPS with a 1 vCPU and 1 GB RAM configuration, such as Oracle VPS, results in severe performance issues, including frequent browser freezes. Therefore, it is advisable to avoid running browsers in such environments.

For reference, applications like AdNade and eBesucher tend to consume more system resources compared to other bandwidth-sharing applications. You may consider running other applications on your VPS while avoiding containers that require browsers.

To monitor CPU and memory usage for all Docker containers, you can use the following command:

sudo docker stats

For detailed resource consumption per container, replace <container_name> with the actual container name and run:

sudo docker stats <container_name>

Based on the resource usage results, you can determine the most suitable applications to run on your VPS.

Thank you

[mrjkjxyz]

Got it, thank you very much.