-
Notifications
You must be signed in to change notification settings - Fork 83
Open
Description
Not an issue, but who knows, it could be. Is it okay to run nucypher behind load balancer? When you load balance real client IPs are hidden and keep receive balancer's IP. Has been running it for a day and getting:
number of connected peers: [138]
2024-04-06T19:32:39.662Z INFO keep-libp2p libp2p/libp2p.go:547 established connection to [/ip4/172.18.0.1/tcp/40356/ipfs/16Uiu2HAmNUTrhsXTgrFCEJwngrwhDSf3AZLqMUFbfj7yTaQqG2BT]
2024-04-06T19:32:39.662Z INFO keep-libp2p libp2p/libp2p.go:569 starting ping test for [/ip4/172.18.0.1/tcp/40356/ipfs/16Uiu2HAmNUTrhsXTgrFCEJwngrwhDSf3AZLqMUFbfj7yTaQqG2BT]
2024-04-06T19:32:40.093Z INFO keep-libp2p libp2p/libp2p.go:593 ping test for [/ip4/172.18.0.1/tcp/40356/ipfs/16Uiu2HAmNUTrhsXTgrFCEJwngrwhDSf3AZLqMUFbfj7yTaQqG2BT] completed with success (RTT [143.628337ms])
So everything seems fine (given that 172.18.0.1 is a load balancer IP which is a tcp proxy)a nd I can see my node among other peers in their /diagnostics.
Asking to make sure that it is not a problem to run in behind a proxy.
Metadata
Metadata
Assignees
Labels
No labels