Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tun error #173

Closed
drdre-lab opened this issue Nov 30, 2024 · 7 comments
Closed

Tun error #173

drdre-lab opened this issue Nov 30, 2024 · 7 comments

Comments

@drdre-lab
Copy link

drdre-lab commented Nov 30, 2024

Please help me. I'm trying to launch Honeygain using Test script with proxy. But the container with Tun2socks cannot start. Errors in the screenshot.
level=fatal msg="[ENGINE] failed to start: create tun: operation not permitted"

Скриншот 30 11 24_16 52 50

I'm trying it on a freshly installed Ubuntu. I tried using the root user and the sudo user. I tried it on another clean VPS. I tried Tun2proxy instead of Tu2socks. A similar error remains.
Скриншот 30 11 24_16 32 52

I tried using http proxy instead of socks. I tried disabling dns in the settings. I think I've already tried everything.

@engageub
Copy link
Owner

engageub commented Nov 30, 2024

Hello,
It looks like /dev/net/tun does not have required permissions on your VPS.
Please see xjasonlyu/tun2socks#125 for more details.
You may change the permissions as mentioned and try to start.

Thank you

@engageub
Copy link
Owner

Adding to the previous comment, please note that if the problem is not resolved, please comment on the issue mentioned above.
The script is working as expected.

@drdre-lab
Copy link
Author

drdre-lab commented Dec 1, 2024

I leave a comment on my problem. I suffered for a couple of days, but decided. The problem was in the newest version of the Docker. I installed clean Ubuntu 22 and installed the latest Docker from Docker repositories (29). But apparently in the latest version there is a conflict with Ubuntu 22 - containers Tun2socks could not launch tun. Although I performed and run all the actions on behalf of root. Then I installed Docker with sudo apt-get -y install docker.io. The old version from Ubuntu repositories has been installed (24). And this is the working system.
01 12 24_19 08 01
The problem is gone, everything works like clockwork. Thank you for the script.

@engageub
Copy link
Owner

engageub commented Dec 1, 2024

Thank you for the update. So you have installed docker separately and not by using the command mentioned which caused this issue?
The steps mentioned in the Readme are for the new Ubuntu VPS after getting it from the provider.
It updates the OS and then installs docker.
If you get a new VPS, just follow the commands mentioned in ReadMe file.
Even if you don't install the docker, the script detects and provides command lines on how to install.

Thank you

@drdre-lab
Copy link
Author

drdre-lab commented Dec 2, 2024

So you have installed docker separately and not by using the command mentioned which caused this issue?

Yes, initially I installed Docker of newest version separately on the new VPS. And that was my fatal mistake. The installed newest Docker and Ubuntu 22 did not allow Tun2socks to start.

@theo-bnts
Copy link

Thanks to the owner for this work!
I had the same problem with an old Docker installation but I couldn't reinstall Docker.
Here's the solution I found: Replace -v '/dev/net/tun:/dev/net/tun' with --device /dev/net/tun.

@engageub
Copy link
Owner

engageub commented Dec 14, 2024

@theo-bnts ,
Thank you for the update. Other users in the issues mentioned were having the same problem.
Some users had to use --privileged flag along with the mentioned command to use device.
However if you wish to install docker, you can simply use the built-in command in the script.
sudo bash internetIncome.sh --install .
This command worked for another user in the recent issue #177

Similar Issues from other docker users below:
haugene/docker-transmission-openvpn#2900
qdm12/gluetun#2606
haugene/docker-transmission-openvpn#2883

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants