-
@ Jon Martins
2025-03-05 18:52:02
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!