From 2ccce0043661d797045b9a0e6745d58461ba4246 Mon Sep 17 00:00:00 2001 From: brettmollin Date: Sun, 6 Oct 2024 21:12:26 -0400 Subject: [PATCH] Update configure-a-private-server.md remove alloy server reference --- .../configuration/peering/configure-a-private-server.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/infrastructure/configuration/peering/configure-a-private-server.md b/docs/infrastructure/configuration/peering/configure-a-private-server.md index 0cbf0a0b65..23d530c005 100644 --- a/docs/infrastructure/configuration/peering/configure-a-private-server.md +++ b/docs/infrastructure/configuration/peering/configure-a-private-server.md @@ -50,7 +50,6 @@ To set up a specific server as a private peer, complete the following steps: ``` [ips_fixed] r.ripple.com 51235 - zaphod.alloy.ee 51235 ``` If your server connects using **proxies**, the IP addresses and ports should match the configurations of the `rippled` servers you are using as proxies. For each of those servers, the port number should match the `protocol = peer` port in that server's config file (usually 51235). For example, your configuration might look like this: