torproject/community
1
0
Fork 0
mirror of https://github.com/torproject/community.git synced 2025-02-17 00:18:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Disabeling of SeLinux to be able to Start the bridge.

Browse Source
This commit is contained in:
qub3 2022-11-23 14:15:01 +00:00 committed by Gus
parent 75a3dc7d79
commit 67e0b91dc7
1 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
content/relay/setup/bridge/fedora/contents.lr
View File

@ -85,13 +85,27 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`,
* Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open both ports. You can use our [reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet.
### 5. Restart Tor
### 5. Disable SeLinux
Check wether SeLinux is set to "Enforcing".
```
# getenforce
```
If set to "Enforcing", change Status to "Permissive".
```
# setenforce 0
```
### 6. Restart Tor
```
# systemctl enable --now tor
```
### 6. Monitor your logs
### 7. Monitor your logs
To confirm your bridge is running with no issues, you should see something like this (usually in `/var/log/tor/log` or `/var/log/syslog`):
```
@ -104,7 +118,7 @@ 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.
```
### 7. Final Notes
### 8. Final Notes
If you are having trouble setting up your bridge, have a look at [our help section](../../../getting-help/).
If your bridge is now running, check out the [post-install notes](../post-install/).