I self host appwrite 1.8.1. The genereal functionallity works fine. But my realtime subscription isn't updating. I see "Received heartbeat response from realtime server" every couple of seconds. I had it working in the past but also not easily. Recently I switched from native nginx to nginx-proxy-manager. Maybe thats an issue? Websockets is enabled and why would the heartbeat work? I tried different channels. This is the basic code:
final subscription = Appwrite().realtime.subscribe([
'databases.*',
]);
print(
'eventsListener: subscription created, channels: ${subscription.channels}',
);
Appwrite().subscriptions.add(subscription);
subscription.stream
.listen(
(RealtimeMessage message) {
print('eventsListener: received message');
print(' channels: ${message.channels}');
print(' events: ${message.events}');
print(' payload: ${message.payload}');
},
)
.onError((e) {
print('eventsListener: stream error: $e');
log('eventsListener error', error: e);
});
print('eventsListener: listening established');
I also tried 'databases.[id].collections.[id].documents' or 'tablesdb.[id].tables.[id]' and different wildcards. No idea what to do.
Yep, it seems to be broken / partially working. https://discord.com/channels/564160730845151244/1482365925742350407
Recommended threads
- Realtime for files() works almost well, ...
I have been trying to make use of realtime, today (14.03.26) I have pulled all the latest versions of docker images, and sdk available. Whats working: - Conn...
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...
- Impossible to get USER after createEmail...
Am using provider to deal with functions linked to appwrite. Here is my login. Future<String?> login(String email, String password) async { try { aw...