\n\nDoesn't happen if I install directly from [elk.zone](https://elk.zone). ",[3198,3199],{"name":3152,"color":3153},{"name":3155,"color":3156},3343,"Icon of Microsoft Store version has white background","2025-08-03T02:09:25Z","https://github.com/elk-zone/elk/issues/3343",0.7498257,{"description":3206,"labels":3207,"number":3210,"owner":3158,"repository":3159,"state":3160,"title":3211,"updated_at":3212,"url":3213,"score":3214},"When trying to load elk.zone or main.elk.zone on Safari on iOS 14.5.1, I get the following errors in the console:\r\n\u003Cimg width=\"763\" alt=\"image\" src=\"https://user-images.githubusercontent.com/57513430/214772552-fedda5d7-6591-4aa1-89e8-51f42e04517b.png\">\r\n\r\nThe effect of this is that the page doesn't show any content.\r\n\r\n\r\n\r\n(Yes, it's jailbroken, but I'm confident it's not an issue with that as I rebooted to stock iOS and the error persisted)\r\n\r\nI know this is an obscure target, but I'd like to at least try Elk on a mobile device, as many iOS clients don't support a version this low (argh!), and this seems like potentially one of the only solutions to push notifications on it. Thank you for your time!",[3208,3209],{"name":3152,"color":3153},{"name":3155,"color":3156},1464,"Not loading on iOS 14.5.1","2023-01-31T01:04:33Z","https://github.com/elk-zone/elk/issues/1464",0.7539474,{"description":3216,"labels":3217,"number":3220,"owner":3158,"repository":3159,"state":3160,"title":3221,"updated_at":3222,"url":3223,"score":3224},"With my GtS account, feeds are getting updates on elk.zone, but not on canary versions.\n\nI looked through the commits between masto 6.10.1 (used in stable release) and 6.10.4 (currently in Elk's package.json) and found the cause: commit https://github.com/neet/masto.js/commit/7f01cb3f9c2c9f53f7bdbb9ad1d95fc4b4e9bab5, PR https://github.com/neet/masto.js/pull/1255\n\nThe client no more sends an access token via Sec-WebSocket-Protocol header, but neither sends Authorization header for some reason.",[3218,3219],{"name":3152,"color":3153},{"name":3155,"color":3156},3356,"masto.js 6.10.2 broke streaming API","2025-08-21T15:38:18Z","https://github.com/elk-zone/elk/issues/3356",0.75562406,{"description":3226,"labels":3227,"number":3230,"owner":3158,"repository":3159,"state":3160,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Pre-Checks\n\n- [X] Check that there isn't [already an issue](https://github.com/elk-zone/elk/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/elk-zone/elk/discussions) or join our [Discord Chat Server](https://chat.elk.zone).\n- [X] Providing a screenshot or video to reproduce the issue or show visually what was meant.\n- [ ] I am willing to provide a PR.\n\n### Describe the bug\n\nI'm running elk locally on a machine on my home network to debug/develop a separate issue. At home I just used a private ipv4 address (192.168.x.x) to reach it, and it was fine. When I left home and wanted to work on the bug, when I tried to reach the private ipv6 address (which I'm tunneled to using yggdrasil), I get a backtrace and all kinds of errors when I connect to it. See the screenshot below and additional context.\n\n### Reproduction video or screenshot\n\n\r\n\n\n### Additional Context\n\nI start the server:\r\n\r\n```\r\n(elk-git)elk-git@hm90:/elk$ HOST='200:6873:2359:a0d1:ef41:f25d:c973:dc04' pnpm dev\r\n 21:19:03\r\nNuxi 3.0.0 21:19:03\r\nNuxt 3.0.0 with Nitro 1.0.0 21:19:03\r\n 21:19:04\r\n > Listening: http://200:6873:2359:a0d1:ef41:f25d:c973:dc04:5314/ \r\n > Vue Inspector: Press Meta+Shift in App to toggle the Inspector 21:19:06\r\n\r\n WARN [@vue/reactivity-transform] Reactivity transform is an experimental feature. 21:19:07\r\nExperimental features may change behavior between patch versions.\r\nIt is recommended to pin your vue dependencies to exact versions to avoid breakage.\r\nYou can follow the proposal's status at https://github.com/vuejs/rfcs/discussions/369.\r\n\r\n 21:19:03\r\nℹ Vite client warmed up in 5901ms 21:19:12\r\n✔ Nitro built in 696 ms nitro 21:19:13\r\n```\r\n\r\n\r\nThen, I try to load the site (http://[200:6873:2359:a0d1:ef41:f25d:c973:dc04]:5314/) in my browser; I get the above screenshot in my browser, and the following backtrace on the console:\r\n\r\n```\r\n[nuxt] [request error] [unhandled] [500] Failed to parse URL from http://200:6873:2359:a0d1:ef41:f25d:c973:dc04:5314/__nuxt_vite_node__/manifest ()\r\n at async $fetchRaw2 (./node_modules/.pnpm/ofetch@1.0.0/node_modules/ofetch/dist/shared/ofetch.5cb01515.mjs:142:24) \r\n at async ./.nuxt/dev/index.mjs:756:20 \r\n at async ./.nuxt/dev/index.mjs:830:64 \r\n at async ./.nuxt/dev/index.mjs:110:22 \r\n at async Object.handler (./node_modules/.pnpm/h3@1.0.2/node_modules/h3/dist/index.mjs:723:19) \r\n at async Server.toNodeHandle (./node_modules/.pnpm/h3@1.0.2/node_modules/h3/dist/index.mjs:798:7)\r\n[nuxt] [request error] [unhandled] [500] Failed to parse URL from http://200:6873:2359:a0d1:ef41:f25d:c973:dc04:5314/__nuxt_vite_node__/manifest ()\r\n at async $fetchRaw2 (./node_modules/.pnpm/ofetch@1.0.0/node_modules/ofetch/dist/shared/ofetch.5cb01515.mjs:142:24) \r\n at async ./.nuxt/dev/index.mjs:756:20 \r\n at async ./.nuxt/dev/index.mjs:830:64 \r\n at async ./.nuxt/dev/index.mjs:110:22 \r\n at async Object.handler (./node_modules/.pnpm/h3@1.0.2/node_modules/h3/dist/index.mjs:723:19) \r\n at async toNodeHandle (./node_modules/.pnpm/h3@1.0.2/node_modules/h3/dist/index.mjs:798:7) \r\n at async Object.ufetch [as localFetch] (./node_modules/.pnpm/unenv@1.0.0/node_modules/unenv/runtime/fetch/index.mjs:9:17) \r\n at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:443:30) \r\n at async Server.toNodeHandle (./node_modules/.pnpm/h3@1.0.2/node_modules/h3/dist/index.mjs:805:9)\r\n```\r\n\r\nIt almost looks as though something internal dropped the brackets from the url, and then some node library gets confused parsing it.\r\n\r\nI did manage to work around it by adding an entry to /etc/hosts in the chroot, and starting the server with the name alias rather than the raw ipv6 address. That seems to work, and I can connect to the site as expected with my browser.\r\n\r\n```\r\n(elk-git)elk-git@hm90:/elk$ grep ipv6 /etc/hosts\r\n200:6873:2359:a0d1:ef41:f25d:c973:dc04 hm90-ipv6\r\n(elk-git)elk-git@hm90:/elk$ HOST='hm90-ipv6' pnpm dev\r\n\r\nNuxi 3.0.0 21:31:06\r\nNuxt 3.0.0 with Nitro 1.0.0 21:31:06\r\n 21:31:07\r\n > Listening: http://hm90-ipv6:5314/ \r\n\r\n > Vue Inspector: Press Meta+Shift in App to toggle the Inspector 21:31:09\r\n```\r\n\r\n",[3228,3229],{"name":3152,"color":3153},{"name":3155,"color":3156},1305,"Elk gets confused by ipv6 without dns","2023-01-18T21:32:34Z","https://github.com/elk-zone/elk/issues/1305",0.75905776,{"description":3236,"labels":3237,"number":3240,"owner":3158,"repository":3159,"state":3160,"title":3241,"updated_at":3242,"url":3243,"score":3244},"Sometimes, immediately after logging in, Elk opens the (obviously malformed) URL `https://elk.zoneundefined` instead of a proper URL. I don't know why that happens, because I'm always automatically re-directed to that URL, meaning that the browser console is not available anymore when noticing the issue.\r\n\r\nAdguard Home running on my Raspberry Pi has logged plenty of these requests. Not sure why it says `.lan` – in the browser it's always displayed without it.\r\n\r\n\r\n",[3238,3239],{"name":3152,"color":3153},{"name":3155,"color":3156},2240,"Elk opens https://elk.zoneundefined instead of proper URL","2023-07-19T11:36:46Z","https://github.com/elk-zone/elk/issues/2240",0.7618616,{"description":3246,"labels":3247,"number":3250,"owner":3158,"repository":3159,"state":3251,"title":3252,"updated_at":3253,"url":3254,"score":3255},"### Pre-Checks\n\n- [X] Check that there isn't [already an issue](https://github.com/elk-zone/elk/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/elk-zone/elk/discussions) or join our [Discord Chat Server](https://chat.elk.zone).\n- [X] Providing a screenshot or video to reproduce the issue or show visually what was meant.\n- [X] I am willing to provide a PR.\n\n### Describe the bug\n\nFrom discord: https://discord.com/channels/1044887051155292200/1048183611804884992/1063463527005831218\r\n\r\nI think it's really cool that Elk allows you to log in with multiple accounts. However, the experience of setting it up isn't so great if you want to log in to multiple accounts on the same instance. When you press the \"Sign in\" button, it automatically logs you in with whatever account you're signed into on the main web interface. It's not really obvious that you need to go into the main web interface, sign out of your account, and then you can go back to Elk and sign into a different account.\r\n\r\nI would suggest making the following change to login.ts:\r\nhttps://github.com/elk-zone/elk/blob/main/server/api/%5Bserver%5D/login.ts\r\nWithin the query const, add the following property:\r\nforce_login: true\r\n\r\nSetting force_login to true will result in a modal being presented to the user, indicating which account they will be logging in with, and asking them to confirm they wish to login. There is also a logout button so they can change to a different account. This is documented at:\r\nhttps://docs.joinmastodon.org/methods/oauth/#query-parameters\r\n\r\nI personally think this would be useful, but what does the team think?\n\n### Reproduction video or screenshot\n\n_No response_\n\n### Additional Context\n\n_No response_",[3248,3249],{"name":3152,"color":3153},{"name":3155,"color":3156},1091,"closed","allow multiple accounts on same server","2023-01-13T18:08:17Z","https://github.com/elk-zone/elk/issues/1091",0.71090966,["Reactive",3257],{},["Set"],["ShallowReactive",3260],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9ypsi1tc-Qz0nXxYKW-XYyrLL7U3lZlzOz4zNNxHti0":-1},"/elk-zone/elk/1472"]