Unverified Commit 3cb1c181 authored Aug 07, 2019 by Philipp Winter

Use port 3818 instead of 9001 in our example log.

Port 9001 should not be used for a bridge.

parent fbb69822

content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr

+1 −1

Original line number	Diff line number	Diff line
		@@ -89,7 +89,7 @@ To confirm your bridge is running with no issues, you should see something like
		[notice] Registered server transport 'obfs4' at '[::]:46396'
		[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
		[notice] Bootstrapped 100%: Done
		[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
		```

content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr

+1 −1

Original line number	Diff line number	Diff line
		@@ -75,7 +75,7 @@ To confirm your bridge is running with no issues, you should see something like
		[notice] Registered server transport 'obfs4' at '[::]:46396'
		[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
		[notice] Bootstrapped 100%: Done
		[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
		```
		---

content/relay-operations/technical-setup/bridge/freebsd/contents.lr

+1 −1

Original line number	Diff line number	Diff line
		@@ -75,7 +75,7 @@ To confirm your bridge is running with no issues, you should see something like
		[notice] Registered server transport 'obfs4' at '[::]:46396'
		[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
		[notice] Bootstrapped 100%: Done
		[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
		```

content/relay-operations/technical-setup/bridge/openbsd/contents.lr

+1 −1

Original line number	Diff line number	Diff line
		@@ -70,7 +70,7 @@ To confirm your bridge is running with no issues, you should see something like
		[notice] Registered server transport 'obfs4' at '[::]:46396'
		[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
		[notice] Bootstrapped 100%: Done
		[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
		[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
		```
		---