Nostr Web Client

Disappointing. I enabled the autolock feature about a week ago, last night boom! Logged out again. Missed out on zaps for some great notes.

Looking for alternative solutions as this is getting beyond frustrating.

No power outages, no internet interruptions, node online for months, alby hub logs me out atleast once a month, and now its more like once a week 😟

Jon Martins 10mo ago

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 nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 and nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tekd3jks6rev3ehyargv9nk66tnxe6h2dn5w43kuerk0fmnwcm4vfc8z6mgweu8j7fhdfhkjmmrxs6k66mnwg6x2cty9ehku6t0dchsz9mhwden5te0wfjkccte9ehx7um5wghxjmnxduhs5nd6j2, 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.

Reply to this note

Please Login to reply.

Discussion

Roland 10mo ago

Where do you see port 8033? For standard Linux we use 8029 which as far as I know is unassigned, but we did change it from 8080 several months back due to the chance of a conflict. https://github.com/getAlby/hub/blob/master/scripts/linux-x86_64/install.sh#L74

But, Alby Hub would not work at all if the port was already in use, so I doubt this is the issue that cryptowolf is seeing.

Jon Martins 10mo ago

Thank you kindly nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqpqzk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q8tg5jd .

Looked through the commits on Alby's Github, both ARM and X86 scripts and indeed it was from 8080 to 8029. The file I have on my server somewhat shows 8033 with a note warning about it, dated back to September, but I cannot recall why other than a small discussion, my apologies.

So digging around nostr:nprofile1q9z8wue69uhnvmr9dp58jernwf6xsct8d45hxdn4w5m8gatrdej8v7nhxa3h2cnsw94ksanc09unw6n0d9hkxdp4d44hxu35v4skgtn0de5k7m30qy88wumn8ghj7mn0wvhxcmmv9uqzq44xkafh8j8hhy79809wsmv0lw46nu4pkwqjyp20ekml80mytde8phfu08 GitHub files, I noticed they run Albyhub with Docker, which in this case would be my initial suspicion, however further their installation script puts Albyhub listening to only port 8080. Have a look please, line 102:

https://github.com/Start9Labs/albyhub-startos/blob/main/docker_entrypoint.sh

We could be onto something!