Hey nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpzemhxue69uhkummnw3ezu6m0wdkk7uewdaexwqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qzxnhwden5te0dehhxarj9ehhyctwvajhq6tvdshxgetkvjvusy nostr:nprofile1qqsq2gwmj5csjm0lwqxu7sgtq8d502m9nr08uhhjck3t6ls3vqc4haspz4mhxue69uhk2er9dchxummnw3ezumrpdejqzyrhwden5te0dehhxarj9emkjmn9qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsxdd778 ,
To install Alby Hub on my Proxmox I've changed the Linux distribution for the Virtual Machine from debian 12.8 to the most recent Ubuntu LTS. 

And guess what, now I can successfully connect my Alby account. ✅
As it's the same Alby account, the bug, which was reproducable for me on a second fresh VM, could be connected to debian.


nostr:nevent1qqsrvh6gz97gj68wee60sx3f8l0nzady9rwtd5ktsy3p64r5xmyexyspz3mhxue69uhkummnw3exjcfwwdcxzcm99upzq6ln8mdmlc6gc8cymxms3l23ldsqgjzcz2k6kj036u9dpdnd03c4qvzqqqqqqy5leyud