-
Notifications
You must be signed in to change notification settings - Fork 27
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
TorBox does not work after restart #228
Comments
I guess
If this doesn't work, try the following (replacing
If this doesn't work, try the following (adding
I would appreciate your feedback which of these three solutions worked for you so I can take it into account for the upcoming release. |
Thanks for the fast response! I tried the 3 options: to summarize: Option 2 enables torbox to get an IP after boot. That is good. Internet access is still not working and the web interface is broken (don’t know when the web interface broke, maybe it already broke during option 1) |
So I tried a bunch of stuff and I found the following thing quite interesting: Internet access starts working. I will add this to rc.local, but I feel like this is a bug or something Edit: It’s already in the rc.local. I tried adding a sleep 10 before and after the command, I also tried exit 0 right after the command. Nothing seems to help. Edit2: |
Thank you for your detailed information. You are on the right track: the problem lies in the Dealing with With option 2 it was possible to isolate the problem. However, the Old: Old: Old: Also, If this will not fix the issue, try to execute the command |
I’ve gone the way of running sudo /etc/rc.local First to see any error. Haven’t thought about that earlier. I commented bash /home/torbox/torbox/bin/regset out by placing a # before the line and executed the rc file again. Now without any errors! Then I fixed the if statements and installed ipset. Rebooted aaaaaaand, let’s see… Restarting tor doesn’t lead to 100% bootstrapped. It’s stuck on 0%. The pi has a valid IP on eth0 and is able to access the internet though. Running rc.local manually again. No errors. No behavior change. Running the menu again, choosing 5 to set eth0 as source. Menu didn’t show the arrow on the side of the option. Internet access still doesn’t work. |
Ok, that's a setback. :-( The flash is based on the following check: You don't have a valid route if the router doesn't give you an IP (via DHCP). Because these IPs have time to live (TTL) settings in the DHCP server, it is possible that you have manually to release the old IP ( Sometimes, when I do tests with a TorBox on my Internet router and have to restart TorBox several times, the router fails to give me a new IP which results in waiting until the TTL is over or restarting the router. |
I’ve checked that the TorBox has a valid IP. It can reach 8.8.8.8 when I am using the local console on it. That does not seem to be the problem. Unfortunately. |
What is the output of |
Let me give you the current status: Starting Pi
Accessing the menu again
Rebooting
|
No arrow will be shown if the Let's summarize my thoughts:
At this point, I don't know how to help you further to get your default gateway from your router. |
The missing default route is not a problem on other devices that are running windows, Ubuntu and even MacOS. Since the route was there in the beginning (otherwise I couldn’t have installed ipset), I assume it has been destroyed by our troubleshooting and tempering. Since we found a lot of bugs and you could implement those fixes, when would 0.5.3 be available? I could then reflash and see where we go from there. Maybe that version will work out of the box. |
I'm still fixing some bugs that pop up during the test phase. If all works according to my plans, the image should be out this weekend, latest coming Monday. If you want to try it before, you can install it from the Github repository using this manual: https://www.torbox.ch/?page_id=1168#script The recommended command for the script is the following (as long as the branche |
Sitting tight until a new image has been released and looking forward to test it! Will report back after that. |
News to report! As I mentioned before: Sometimes, when I do tests with a TorBox on my Internet router and have to restart TorBox several times, the router fails to give me a new IP (or default route, as I have discovered today). Because, during today's test, I was confronted with the same problem you have to deal with, I took the opportunity to investigate a possible fix in more depth. I couldn't find why TorBox sometimes doesn't get the default route, but it also happens on other Linux systems. Research on the internet brought up several different explanations and solutions, which are also different on various distributions. Usually, that's a sign that affected people also struggle to pinpoint the source of the problem. I guess the problem has something to do with
See also here. |
Well that sounds great! Can’t wait to try the new image once it has been released |
The new image is online: https://www.torbox.ch/data/torbox-20230709-v053.gz |
New image works like a charm! Great success! Thanks a lot |
Thank you for your feedback and support! |
First of all thanks for this cool project. There’s something going on however, because whenever I restart the Pi, the following happens:
Things I did:
Is this by design? If so, can I change it? If not( what’s wrong?
The text was updated successfully, but these errors were encountered: