Hello,
When I try to access published ports via IP:PORT in tun2socks, it is not accessible where as using 127.0.0.1:PORT and 0.0.0.0:PORT are working fine. net.ipv4.ip_forward is also set 1 in the container.

If I use published ports on direct docker image instead of tun2socks, it is accessible via IP:PORT. So, the only issue is accessing via IP:PORT on tun2socks container.

To Test this, you can use InternetIncome test branch.
Set the following in properties.conf file for directly accessing the container without tun2socks

 Set CUSTOM_CHROME to true 
 Set USE_DIRECT_CONNECTION to true

After starting the container, you can try accessing via IP:PORT. It works fine.

Now, to access via tun2socks proxy.
Set the following in properties.conf

 Set CUSTOM_CHROME to true 
 Set USE_DIRECT_CONNECTION to false
 Set USE_PROXIES to true

Set a proxy inside proxies.txt file.
After starting the container, you will notice that it is accessible via 127.0.0.1:IP and 0.0.0.0:IP but not IP:PORT of VPS.

Could you please suggest what configuration has to be enabled to access via IP:PORT through tun2socks container.

Thank you