Changes the onion hidden service port to match the clearnet API port

Turns out both the clearnet API and the Tor hidden service can be run on the same port.
talaia-labs · Nov 10, 2022 · f5dccf4 · f5dccf4
1 parent 6f10736
commit f5dccf4
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/teos/src/conf_template.toml b/teos/src/conf_template.toml
@@ -2,7 +2,7 @@
 api_bind = "127.0.0.1"
 api_port = 9814
 tor_control_port = 9051
-onion_hidden_service_port = 2121
+onion_hidden_service_port = 9814
 tor_support = false
 
 # RPC

diff --git a/teos/src/config.rs b/teos/src/config.rs
@@ -106,7 +106,7 @@ pub struct Opt {
     #[structopt(long)]
     pub tor_control_port: Option<u16>,
 
-    /// Port for the onion hidden service to listen on [default: 2121]
+    /// Port for the onion hidden service to listen on [default: 9814]
     #[structopt(long)]
     pub onion_hidden_service_port: Option<u16>,
 }
@@ -257,7 +257,7 @@ impl Default for Config {
             api_port: 9814,
             tor_support: false,
             tor_control_port: 9051,
-            onion_hidden_service_port: 2121,
+            onion_hidden_service_port: 9814,
             rpc_bind: "127.0.0.1".into(),
             rpc_port: 8814,
             btc_network: "mainnet".into(),