Generally, if a VPS is cheap it probably means that they don’t have much
bandwidth. What you might want to consider doing is contacting the VPS provider
(sending an email to their support email address, or contacting them via their
contact tab on their website, and asking them how much bandwidth
On 06/25/2018 08:01 PM, Keifer Bly wrote:
> Ok. It could be possible your tor installation was somehow corrupted. Try
> completely uninstalling tor with this command
>
> As root: apt-get remove tor
>
> This should completely uninstall tor
>
> I am saying this as it could be that somehow one of
Thank you.There do seem to be a few faults and missing bits in the help stuff.As nothing has worked I'll reinstall Deb9 and start again.I wonder whether cheap VPS operators might have something to do with the problems. Rob
___
tor-relays mailing
Hi Rob,
The default log location on Debian changed some time ago to be your syslog
instead of a file in /var/log/tor.
If you would like to have tor log to a specific file, please add the following
to your torrc and restart tor:
Log notice file /var/log/tor/log
I will get this page updated ri
Ok. It could be possible your tor installation was somehow corrupted. Try
completely uninstalling tor with this command
As root: apt-get remove tor
This should completely uninstall tor
I am saying this as it could be that somehow one of your tor files was
accidentally deted or moved. Doing thi
Keifer,That was from root.That is what is odd as I only install things from root and use them as a user.Rob
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Try signing into the root account on your Linux. This should these issues. Let
me know.
From: I
Sent: Monday, June 25, 2018 5:37 PM
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] bridge installation help please
Keifer, thanks,
Try navigating to /var/log/tor/. This is where tor wi
Keifer, thanks, Try navigating to /var/log/tor/. This is where tor will normally save the log files to. See if there is a tor log text file there. If you have not started your relay, tor might not have created the log file yet. Try starting the tor software then see if the file appears after
Is the tor software successfully launched? Try simply launching the tor
software just by opening a terminal window and typing “tor” in the Debian
command line. This will start the tor software. If the bridge becomes
successfully useable, you will see a message which will read “Self testing
indi
Keifer, thanks for the swift answer,! shift workI followed https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxyon a vps with Debian 9the torrc readsRunAsDaemon 1ORPort 9001BridgeRelay 1ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxyExtORPort autoDataDirectory
This is Debian Linux your doing this on correct? I am assuming this as most
relays are run on Linux.
Here are the steps I’d use to install tor on Linux:
1. Open the Linux terminal
2. Sign into the Linux root account by typing su, then press enter. Liux will
then ask you for a password; type th
Would someone know what the problem is, please.I can't see how the bridge is running nor what is wrong but have followed the torproject.org guide. tail -F /var/log/tor/logtail: cannot open '/var/log/tor/log' for reading: No such file or directoryRunAsDaemon 1ORPort 9001BridgeRelay 1ExtORPort au
On Tue, Jun 26, 2018 at 04:31:55AM +1000, teor wrote:
>
> On 26 Jun 2018, at 02:40, nusenu wrote:
>
> >> It would also be nice if the relay, itself, performed self-checks of
> >> this connectivity and printed a warning log if some failure-threshold is
> >> reached (and possibly disabling the IPv
On Mon, Jun 25, 2018 at 04:40:00PM +, nusenu wrote:
> > Considering there are potential critical failures when the IPv6 ORPort
> > is configured, should the relay guide suggest the operator confirm they
> > have IPv6 connectivity to all of the IPv6-enabled directory
> > authorities[2] before en
On 26 Jun 2018, at 02:40, nusenu wrote:
>> It would also be nice if the relay, itself, performed self-checks of
>> this connectivity and printed a warning log if some failure-threshold is
>> reached (and possibly disabling the IPv6 ORPort). But, in reality, this
>> is a hack
>
> I wouldn't cal
nusenu:
>> Considering there are potential critical failures when the IPv6 ORPort
>> is configured, should the relay guide suggest the operator confirm they
>> have IPv6 connectivity to all of the IPv6-enabled directory
>> authorities[2] before enabling it ("Please ping6/telnet/nc to these
>> hos
> Considering there are potential critical failures when the IPv6 ORPort
> is configured, should the relay guide suggest the operator confirm they
> have IPv6 connectivity to all of the IPv6-enabled directory
> authorities[2] before enabling it ("Please ping6/telnet/nc to these
> hosts before enabl
Over the last few days I've started thinking more about IPv6 and,
inevitably, I started thinking about how we can improve support within
the Tor network.
Within the last few months, there were a few instances of relay
operators seeking answers for why their relay did not have the running
flag in t
18 matches
Mail list logo
