Hi,
i wanted to run my bridge on 443 too but i had the same problem on Raspbian Buster with Tor 0.4.0.5 I asked Google but choosing a port above 1024 was the only thing that made it working for me.
Am Fr., 19. Juli 2019 um 11:52 Uhr schrieb dmz21@ziggo.nl:
On July 19, 2019 at 6:36 AM Ben Riley blades1000@gmail.com wrote:
Hi,
Thanks for the reply. Yes, I ran that command way back at the start. I'm assuming I don't have to run it every time the machine reboots or
updates?
I ran it again this morning and it made no difference.
Ah logs, you say that like I know where those are :P When I run sudo tail /var/log/tor/log - I get nothing. I found the Logs app and run that to get all the system logs - way too
much
stuff and I couldn't move it to here, so I found this command (Google)
cat
/var/log/syslog | grep tor -i and got the following (I think I've
included
2 set of attempts to boot up):
Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Starting with guard context
"default" Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Signaled readiness to
systemd
Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bootstrapped 5% (conn): Connecting to a relay Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Server managed proxy encountered a method error. (obfs4 listen tcp 0.0.0.0:443: bind: permission denied)
I ran (and keep running) into the same problem (but on Debian), even after the fix suggested below. Could you please try an unused port above 1024, like 8531? That resolved this issue for me.
hope this helps and kind regards.
Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Managed proxy at '/usr/bin/obfs4proxy' failed the configuration protocol and will be destroyed. Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: tor_assertion_failed_():
Bug:
../src/feature/client/transports.c:1836: managed_proxy_stdout_callback: Assertion mp->conf_state == PT_PROTO_COMPLETED failed; aborting. (on
Tor
0.4.0.5 ) Jul 19 14:32:23 ben-OptiPlex-755 Tor[28002]: Bug: Assertion
mp->conf_state
== PT_PROTO_COMPLETED failed in managed_proxy_stdout_callback at ../src/feature/client/transports.c:1836. Stack trace: (on Tor 0.4.0.5 )
(removed rest of log)
On Fri, Jul 19, 2019 at 1:12 AM Philipp Winter phw@torproject.org
wrote:
On Thu, Jul 18, 2019 at 12:50:34PM +1000, Ben Riley wrote:
Then I saw the above email about being a bridge and thought, fine,
I'll
configure it to be a bridge and help out someone. Tried to do it via the docker/script method, but soon realised that
was
outside my skill level (hey stop laughing! :P)
Did you run into any specific issues? If you had troubles following
the
guide, I'm gonna blame the guide.
Setting ORPort to 443 as suggested. I forwarded that port on the router and then tested it, but it said it was closed. So I thought my router was playing up. I checked a few other ports using online
tools
and a few of them were closed. I forwarded a new another port to
some
other software on another machine and that worked?! So I realised
the
ports are open on the router but closed on the ubuntu machine. I've played around with all the settings, changed by torrc file to a
really
basic one of:
To run obfs4 on port 443, you will have to run the following command,
to
allow obfs4proxy to bind to port 443:
sudo setcap cap_net_bind_service=+ep /usr/bin/obfs4proxy
If you did that already, it would be helpful to see your logs.
Cheers, Philipp _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays