commit 44666a8f263051f27559699e1cc0902c30d7f8a7 Author: Philipp Winter phw@nymity.ch Date: Mon Aug 26 18:02:53 2019 -0700
Link to post-install notes at the end.
Once somebody is done following the instructions, we should explicitly point them to our post-install notes because they are otherwise easy to miss.
Thanks to Roger for pointing this out. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 7 +++++++ .../technical-setup/bridge/debian-ubuntu/contents.lr | 8 ++++++++ .../relay-operations/technical-setup/bridge/docker/contents.lr | 7 ++++++- .../relay-operations/technical-setup/bridge/freebsd/contents.lr | 7 +++++++ .../relay-operations/technical-setup/bridge/openbsd/contents.lr | 8 ++++++++ 5 files changed, 36 insertions(+), 1 deletion(-)
diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index f142d56..5fba1a6 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -92,6 +92,13 @@ To confirm your bridge is running with no issues, you should see something like [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ```
+### 6. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- html: two-columns-page.html --- diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr index 8273f8f..d1eeb17 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -76,6 +76,14 @@ To confirm your bridge is running with no issues, you should see something like [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. ``` + +### 6. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- key: 1 --- diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index ca3d7f7..1c36012 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -14,7 +14,12 @@ Now, it's time to run the container. We maintain a script that automatically de $ bash deploy-container.sh address@email.com ```
-That's it! Your container should now be bootstrapping your new obfs4 Tor bridge. +That's it! Your container should now be bootstrapping your new obfs4 Tor bridge. +Make sure to check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). If +you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). + --- html: two-columns-page.html --- diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 78373df..0741c8c 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -103,6 +103,13 @@ FreeBSDlatest: { } ```
+### 7. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- subtitle: How to deploy an obfs4 bridge on FreeBSD --- diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 0a02f9e..1c95aaa 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -72,6 +72,14 @@ To confirm your bridge is running with no issues, you should see something like [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. ``` + +### 5. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- subtitle: How to deploy an obfs4 bridge on OpenBSD ---