jonmartins on Nostr: Interesting. Are all of you running Albyhub on a StartOS node? Lots of people using ...
Interesting.
Are all of you running Albyhub on a StartOS node?
Lots of people using Albyhub experience no issues. Six months of uninterrupted service for me on an ARM server with vanilla Ubuntu, only running Haven Nostr Relay adjacent to it.
However, on my installation I changed the ports from 8033 to 8029, because 8033 is officially registered on IANA to MindPrint, whatever that might be.
So my hypothesis:
1. Something from StartOS distro is conflicting with port 8033, hence it would be prudent for StartOS to ship it with an unregistered port.
2. And/or upstream, Albyhub could "officially" ship it with some other port. 8029 is not registered.
Please Alby (nprofile…qss4) and Start9 (nprofile…d6j2), weigh in on this.
It could be such a minor detail keeping people from "technically" installing it on the background and "forgetting it".
Otherwise, we might have bigger problems due to running BTC Core along side these apps. Back around v18 and v19, I would often experience complete hogging of TCP connections, crippling every other address on the network the node was connected to.
Are all of you running Albyhub on a StartOS node?
Lots of people using Albyhub experience no issues. Six months of uninterrupted service for me on an ARM server with vanilla Ubuntu, only running Haven Nostr Relay adjacent to it.
However, on my installation I changed the ports from 8033 to 8029, because 8033 is officially registered on IANA to MindPrint, whatever that might be.
So my hypothesis:
1. Something from StartOS distro is conflicting with port 8033, hence it would be prudent for StartOS to ship it with an unregistered port.
2. And/or upstream, Albyhub could "officially" ship it with some other port. 8029 is not registered.
Please Alby (nprofile…qss4) and Start9 (nprofile…d6j2), weigh in on this.
It could be such a minor detail keeping people from "technically" installing it on the background and "forgetting it".
Otherwise, we might have bigger problems due to running BTC Core along side these apps. Back around v18 and v19, I would often experience complete hogging of TCP connections, crippling every other address on the network the node was connected to.