Roland's avatar
Roland rolznz@getalby.com 9 months 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.
GitHub
hub/scripts/linux-x86_64/install.sh at master · getAlby/hub
Alby Hub - Your own Bitcoin Lightning node: easy, connectable, feature-rich ✨ Run anywhere. Become self-sovereign. - getAlby/hub
 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.
↑ Parent

Replies (1)

Jon Martins's avatar
Jon Martins _@jonmartins.com 9 months ago
Thank you kindly @Roland . 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 @Start9 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:
GitHub
albyhub-startos/docker_entrypoint.sh at main · Start9Labs/albyhub-startos
This repository creates the s9pk package that is installed to run Alby Hub - Start9Labs/albyhub-startos
 We could be onto something!
↑