glyph
glyph#7713
Joined Oct 6, 2026
Sign in to search- On New accounts on a self-hosted dev instance are flagged as staffYeah never mind - I just forgot to set FLUXER_ENV to production
- Just happened to me on my self-hosted instance as well
- I am seeing the same error running under systemd:
Oct 14 16:07:37 moonlight fluxer-api-start[741327]: {"level":"debug","time":"2026-10-14T14:07:37.089Z","service":"fluxer-api","env":"production","err":{"type":"StreamNotFoundError","message":"stream not found","stack":"StreamNotFoundError: stream not found\n at parseJsResponse (/nix/store/rkqmb3jw7h96x1hzq4ynmxh6l7hkvjkf-fluxer-api-2026.1010.xxx/lib/node_modules/.pnpm/@nats-io+jetstream@3.4.0/node_modules/@nats-io/jetstream/lib/jsbaseclient_api.js:33:23)\n at StreamAPIImpl.parseJsResponse (/nix/store/rkqmb3jw7h96x1hzq4ynmxh6l7hkvjkf-fluxer-api-2026.1010.xxx/lib/node_modules/.pnpm/@nats-io+jetstream@3.4.0/node_modules/@nats-io/jetstream/lib/jsbaseclient_api.js:134:16)\n at StreamAPIImpl._request (/nix/store/rkqmb3jw7h96x1hzq4ynmxh6l7hkvjkf-fluxer-api-2026.1010.xxx/lib/node_modules/.pnpm/@nats-io+jetstream@3.4.0/node_modules/@nats-io/jetstream/lib/jsbaseclient_api.js:103:29)\n at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n at async StreamAPIImpl.info (/nix/store/rkqmb3jw7h96x1hzq4ynmxh6l7hkvjkf-fluxer-api-2026.1010.xxx/lib/node_modules/.pnpm/@nats-io+jetstream@3.4.0/node_modules/@nats-io/jetstream/lib/jsmstream_api.js:389:19)\n at async ConsumersImpl.ordered (/nix/store/rkqmb3jw7h96x1hzq4ynmxh6l7hkvjkf-fluxer-api-2026.1010.xxx/lib/node_modules/.pnpm/@nats-io+jetstream@3.4.0/node_modules/@nats-io/jetstream/lib/jsmstream_api.js:159:9)\n at async watchOnce (file:///nix/store/rkqmb3jw7h96x1hzq4ynmxh6l7hkvjkf-fluxer-api-2026.1010.xxx/lib/fluxer-api/AppEntrypoint.js:93424:20)","name":"StreamNotFoundError"},"msg":"Shared list watch unavailable, retrying"} - Confirmed fixed on rev 4194525933c0facdd4d7c96f325713f1a8ef927f
- Very cool!
- I think we should not focus too much on potentially hostile instances. Yeah, a potentially hostile instance could ignore those requests. It could also ignore bulk deletion requests while you're still in the server, or ignore standard message deletion as well. The focus should be on protocol-compliant instances and in general I'd assume that the community owners and the instance owners are separate groups and the latter don't have any interest in not honoring deletion requests. (A wholly hostile instance that doesn't honor deletion requests would also be in violation of the GDPR, so I think we can generally assume that most instances won't behave this way)