It doesn’t make sense to me that you are fine with (probably) less than 75% uptime without even investigating. This much downtime is not expected from onion services.
1 Like
It doesn’t make sense to me that you are fine with (probably) less
than 75% uptime without even investigating. This much downtime is not
expected from onion services.
+1. I see this also in the downtime the whonix onion apt repo gets.
See my thread on this:
Whonix maintainers should, or can do, a better job at keeping their
onion services online.
1 Like
Investigation has been completed.
It’s not DOS related. I can rule that out, because I have other other onions with non-pubic onion domain names. (Such as for fetching e-mail over onion.)
The only way to fix a broken onion is the following cumbersome procedure.
Tor / Tor network issues / bugs.
-
stop tor@name.service on the server
-
manually delete Tor consensus and state files on the server
/var/lib/tor-instances/name/cached-certs
/var/lib/tor-instances/name/cached-microdesc-consensus
/var/lib/tor-instances/name/cached-microdescs.new
/var/lib/tor-instances/name/state
(Not all files may need deletion. Perhaps “only” deleting the state file would be sufficient.)
-
restart tor@name.service on the server
-
restart tor@default on local system
These were the only steps requires to temporarily “fix” this. (I wouldn’t call this a “fix”, not even a workaround.)
This is not a safe procedure and should not be required. Not something a “real” onion host requiring location privacy can afford. (Not a safe procedure because it replaces Tor entry guards.)
It’s also not a server configuration issue, because I have multiple servers with identical configuration except for the onion service domain names and private keys. So no other action was required to fix this other than the cumber some procedure.
2 Likes
I have had many problems with the forum .onion in the past. But it is working perfectly for me today.
3 Likes
Unreachable: deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/
E: Failed to fetch tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/dists/trixie/InRelease Connection failed [IP: 127.0.0.1 8082]E: Some index files failed to download. They have been ignored, or old ones used instead.
1 Like
After 12 hours, still unreachable:
E: Failed to fetch tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/dists/trixie/InRelease Connection failed [IP: 127.0.0.1 8082]E: Some index files failed to download. They have been ignored, or old ones used instead.
cc: @Patrick @arraybolt3
1 Like
1 Like
Same issue as:
https://forums.whonix.org/t/forum-onion-unable-to-connect/23107/14
No need to duplicate this.
1 Like
then clear and concisely tell your users whattf they are they supposed to do if the deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion is down and they cannot get updates to their whonix package repos, due to a problem that seems to repeat every two/three weeks.
Whonix project’s onion websites and repos are unreachable. Are you trying to tell your users that tor network is incapable of delivering reliably?
1 Like
OK, so, what’s this? What do I do now to reach whonix project’s onion hidden servers so that I can complete my whonix template updates quickly instead of wasting hours’ of time on this as I am forced to keep trying with different tor circuits, etc.etc.
1 Like
I really don’t get this way of communicating with your users. Are you trying to say
- that it is vain for your users to keep trying to reach the onion hidden services of whonix project?
- that it is vain for your users to use the onion hidden service of whonix project for the whonixOS package updates?
1 Like
Yes. Highly unstable.
Yes.
Debian and Qubes onion also unstable as reported here:
1 Like
I use both, and both of them are more stable than whonix’s one.
1 Like
I don’t have a better answer.
1 Like
This forum topic is about forum onion.
Off-topic.
Packages already replied here:
1 Like
Maybe just restart the tor.service on your VPS?
1 Like
Also, what it is to do, then? Just wait for a while and wish the problem away??? Like, the https://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ is still unreachable.
1 Like
Forum onion UNREACHABLE RIGHT NOW:
1 Like
OK, so you refuse to do the only not- “fix”, not- workaround that may fix the current issue. What’s the other option you are relying on then? Simply refuse to act, and let the problem solve itself, and in the meanwhile let the onion URLs to public whonix services (like forum onion, deb onion, etc.) stay not-working?
1 Like