Sounds like the same issue I had… workaround is to update the host name in the config file from Null to “”I don’t think the latest Datum version with the fix has made it to StartOS yet
Discussion
that was fixed on latest
I don’t recall seeing an update come through on StartOS (and I’ve just been running with the manual fix). I see v2.2 is running and that is latest on GitHub (Jan 13). I thought I had my issue after that
The "" fixed it for me too! So I am running 0.2.2 according to nostr:nprofile1qqs9df4h2deu3aae83fmet5xmrlm4w5l9gdnsy3q2n7dklem7ezmwfcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tekd3jks6rev3ehyargv9nk66tnxe6h2dn5w43kuerk0fmnwcm4vfc8z6mgweu8j7fhdfhkjmmrxs6k66mnwg6x2cty9ehku6t0dchsz9mhwden5te0wfjkccte9ehx7um5wghxjmnxduhs5nd6j2. As I see on GitHub that should be the latest version but maybe Start9 are doing something else to it? I edited the config through the StartOS interface and not through the terminal.
Oh there it is! Hmm it hasn't come through to StartOS yet though... I will try to sideload it to try it out 😉
Thanks nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr … I see I was not looking at the startOS Datum repository on GitHub. Do you know how long it should take for new versions to show up in StartOS marketplace?