pull down to refresh

4 replies \ @supratic OP 23 Sep \ on: Install, Run, Publish & Connect 𝚙𝚑𝚘𝚎𝚗𝚒𝚡𝚍 to SEND/RECEIVE sats to/from SN meta
@ek, I know you have some experience in networking stuff, how you'd face the port forwarding issue on step 2.0 to make the locally installed phoenixd publicly available on the internet?
write
preview
63 sats \ 3 replies \ @ek 23 Sep
Few options:
  1. use (free) dynamic DNS services like https://www.duckdns.org/ to get a domain that always points to your router even if your IP address changes and then use port forwarding on router
  2. use VPN tunnel to a server you own
  3. or just deploy phoenixd on that server
  4. wrap phoenixd with NWC and use NWC instead (not sure if this exists yet)
I am using the third option right now.
reply
0 sats \ 2 replies \ @supratic OP 23 Sep
That's great to know you are using phoenixd, and thanks for sharing all these options. I think this step of port-forwarding/tunneling is a major blocker for people aiming to run a node. I know for example that Start9 is working on it, finding a way to automate the process somehow. I did not have checked lately, maybe someone else can confirm.
reply
0 sats \ 1 reply \ @ek 23 Sep
NWC is the solution imo
Or I might look into if I want to maintain a service like ngrok for stackers only
reply
0 sats \ 0 replies \ @supratic OP 23 Sep
That's sound exiting! running ngrok on a private SN instance?
reply