pull down to refresh
33 sats \ 1 reply \ @NabismoPrime 11 Aug \ on: How to run a Nostr relay? nostr
This is a relay project that I run and is under active development. I tried to make the setup as simple as possible, automating most of the process and including a setup video:
https://github.com/UTXOnly/nostpy-relay/tree/main
I also just rolled out a relay admin graphical user interface so you can manage your relay's allowlist remotely without having to SSH into the server.
https://github.com/UTXOnly/nostpy-gui
If you did end up trying to set these up, I would be happy to support if you have any questions! Feel free to shoot me a DM: npub1g5pm4gf8hh7skp2rsnw9h2pvkr32sdnuhkcx9yte7qxmrg6v4txqqudjqv
Definitely submitting a proposal! Trying to get some clarity on the requirements though as I had a few ideas that don't quite fit the mold like a multi region containerized relay.
Nice just followed the repo!
This is much faster than the serverless relay PoC I made with Python and Lambda functions, less expensive as well!
Not a stupid question at all!
There are a few reasons I suggest running this as a separate server is assuming you are running a Tor node at home and/or hosted only on Tor.
The first being that this ultimately a web server that is meant to listen on a public IP address. You could be hosting your node from a public IP at home (using portforwarding on a NAT router) but I wouldn't advise running a publicly reachable webserver from your home network as you could inadvertently let bad actors into your home network. I would rather spend $5 a month on a VPS than worry about bad actors getting onto my home network, with the current design this just makes API calls over Tor to your node and then serves the invoices to nostr clients.
The second issue is that this script automates the deployment of an nginx server and requesting a TLS certificate (for ease of setup). If you have anything (other services) in the
etc/nginx/sites-available/default
file, it will be overwritten and replaced with the new nginx proxy.The third issue is potential port conflicts, certain nodes may be hosting a webserver on port 443 for an admin UI or something similar.
However this was just quickly thrown together on a Saturday, I'll continue to work on this and will likely release a docker container at some point and with some careful planning could possibly run this on a node as well.
This same thing has happened to me multiple times with several banks. I used to do a lot of P2P trading on Paxful, it was a great extra source of income for a while until I started getting charge backs and otherwise flagging fraud detection algorithms due to very frequent trades.
Glad to hear you ended up coming out of this with your account balance intact. But definitely can relate to what you went through, I was pulling out my hair for over 3 months as well and now have multiple checking accounts to hopefully prevent myself from ending up in that situation again ( I no longer P2P trade as well).