AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 04:46:56 +00:00

[GH-ISSUE #8004] [Bug] Cloud sync not working #3491

New issue

Open

opened 2026-03-23 21:30:43 +00:00 by mirror · 7 comments

mirror commented

2026-03-23 21:30:43 +00:00

Owner

Originally created by @HrisD9823 on GitHub (May 29, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8004

Bug Description

When I work on a shared draft to another pc, the sync is not working, what we have to do is, goto -> settings -> cloud settings -> toggle "Enable sync" -> restart and do that again with turning the "Enable sync" back to on and then restart once again and the sync is working for an hour and then stops, its not syncing constantly on change.

How to Reproduce

goto -> settings -> cloud settings -> toggle "Enable sync" -> restart and do that again with turning the "Enable sync" back to on and then restart once again

Expected Behavior

not to have to restart it everyday

Operating System

mac

AppFlowy Version(s)

0.9.1

Screenshots

No response

Additional Context

No response

Originally created by @HrisD9823 on GitHub (May 29, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8004 ### Bug Description When I work on a shared draft to another pc, the sync is not working, what we have to do is, goto -> settings -> cloud settings -> toggle "Enable sync" -> restart and do that again with turning the "Enable sync" back to on and then restart once again and the sync is working for an hour and then stops, its not syncing constantly on change. ### How to Reproduce goto -> settings -> cloud settings -> toggle "Enable sync" -> restart and do that again with turning the "Enable sync" back to on and then restart once again ### Expected Behavior not to have to restart it everyday ### Operating System mac ### AppFlowy Version(s) 0.9.1 ### Screenshots _No response_ ### Additional Context _No response_

mirror added the

cloud

data sync

bug

labels

2026-03-23 21:30:43 +00:00

mirror commented

2026-03-23 21:30:43 +00:00

Author

Owner

@LucasXu0 commented on GitHub (May 30, 2025):

Hi @HrisD9823, can you share the log files from the PC that has the sync issue? You can export them from the settings page.

@LucasXu0 commented on GitHub (May 30, 2025): Hi @HrisD9823, can you share the log files from the PC that has the sync issue? You can export them from the settings page.

mirror commented

2026-03-23 21:30:43 +00:00

Author

Owner

@HrisD9823 commented on GitHub (May 30, 2025):

appflowy_logs.zip

@HrisD9823 commented on GitHub (May 30, 2025): [appflowy_logs.zip](https://github.com/user-attachments/files/20516924/appflowy_logs.zip)

mirror commented

2026-03-23 21:30:44 +00:00

Author

Owner

@slinky34 commented on GitHub (Jun 28, 2025):

im having a similar issue. Attaching my logs
Im running docker through a prxmox container on debian

appflowy_logs.zip

@slinky34 commented on GitHub (Jun 28, 2025): im having a similar issue. Attaching my logs Im running docker through a prxmox container on debian [appflowy_logs.zip](https://github.com/user-attachments/files/20958778/appflowy_logs.zip)

mirror commented

2026-03-23 21:30:44 +00:00

Author

Owner

@micahlt commented on GitHub (Jul 1, 2025):

I'm having the same issue here, too. In my instance, clearing the cache of the app was the only thing that would help. My server is running on Docker on Ubuntu.

appflowy_logs.zip

@micahlt commented on GitHub (Jul 1, 2025): I'm having the same issue here, too. In my instance, clearing the cache of the app was the only thing that would help. My server is running on Docker on Ubuntu. [appflowy_logs.zip](https://github.com/user-attachments/files/21006481/appflowy_logs.zip)

mirror commented

2026-03-23 21:30:44 +00:00

Author

Owner

@khorshuheng commented on GitHub (Jul 2, 2025):

If clearing the cache is the only way that the cloud sync would work, and you are using self hosted server, chances are, there is some issue with websocket connection. Especially if you are using another nginx in front of our docker compose and didn't set the configuration for allow connection upgrade.

@khorshuheng commented on GitHub (Jul 2, 2025): If clearing the cache is the only way that the cloud sync would work, and you are using self hosted server, chances are, there is some issue with websocket connection. Especially if you are using another nginx in front of our docker compose and didn't set the configuration for allow connection upgrade.

mirror commented

2026-03-23 21:30:44 +00:00

Author

Owner

@micahlt commented on GitHub (Jul 2, 2025):

Interesting, okay. I'll look into it. Thanks!

@micahlt commented on GitHub (Jul 2, 2025): Interesting, okay. I'll look into it. Thanks!

mirror commented

2026-03-23 21:30:44 +00:00

Author

Owner

@theadley commented on GitHub (Jul 7, 2025):

I run nginx proxy manager and had a similar issue and ended up needing to use the external proxy config with minor tweaks.

I followed this FR comment for ideas to get NPM working well and then made the following updates within the root directory of the Appflowy-Cloud repo:

docker-compose.yml

services:
  nginx:
    restart: on-failure
    image: nginx
    ports:
      - ${NGINX_PORT:-80}:80   # Disable this if you are using TLS
      - ${NGINX_TLS_PORT:-443}:443
    volumes:
      - ./external_proxy_config/nginx/appflowy.site.conf:/etc/nginx/nginx.conf
      # - ./nginx/nginx.conf:/etc/nginx/nginx.conf
      # - ./nginx/ssl/certificate.crt:/etc/nginx/ssl/certificate.crt
      # - ./nginx/ssl/private_key.key:/etc/nginx/ssl/private_key.key

./external_proxy_config/nginx/appflowy.site.conf

# add this to let nginx start without errors
events {}

# and this (map without http throws errors)
http {
    # Add the docker dns resolver
    resolver 127.0.0.11 valid=10s;

    map $http_upgrade $connection_upgrade {
        default upgrade;
        '' close;
    }

    server {
        server_name appflowy.h2l.dev;
        listen 80;
        underscores_in_headers on;
        # Don't use these
        # set $appflowy_cloud_backend "http://127.0.0.1:8000";
        # set $gotrue_backend "http://127.0.0.1:9999";
        # set $admin_frontend_backend "http://127.0.0.1:3001";
        # set $appflowy_web_backend "http://127.0.0.1:3000";
        # set $minio_backend "http://127.0.0.1:9001";
        # set $minio_api_backend "http://127.0.0.1:9000";
        # # Host name for minio, used internally within docker compose
        # set $minio_internal_host "127.0.0.1:9000";

        # Rather let Docker resolve the services from nginx/nginx.conf
        set $appflowy_cloud_backend "http://appflowy_cloud:8000";
        set $gotrue_backend "http://gotrue:9999";
        set $admin_frontend_backend "http://admin_frontend:3000";
        set $appflowy_web_backend "http://appflowy_web:80";
        set $minio_backend "http://minio:9001";
        set $minio_api_backend "http://minio:9000";
        # Host name for minio, used internally within docker compose
        set $minio_internal_host "minio:9000";
        set $pgadmin_backend "http://pgadmin:80";
        ...
    }
}

@theadley commented on GitHub (Jul 7, 2025): I run nginx proxy manager and had a similar issue and ended up needing to use the external proxy config with minor tweaks. I followed [this FR](https://github.com/AppFlowy-IO/AppFlowy/issues/6711#issuecomment-2459434218) comment for ideas to get NPM working well and then made the following updates within the root directory of the Appflowy-Cloud repo: docker-compose.yml ``` services: nginx: restart: on-failure image: nginx ports: - ${NGINX_PORT:-80}:80 # Disable this if you are using TLS - ${NGINX_TLS_PORT:-443}:443 volumes: - ./external_proxy_config/nginx/appflowy.site.conf:/etc/nginx/nginx.conf # - ./nginx/nginx.conf:/etc/nginx/nginx.conf # - ./nginx/ssl/certificate.crt:/etc/nginx/ssl/certificate.crt # - ./nginx/ssl/private_key.key:/etc/nginx/ssl/private_key.key ``` ./external_proxy_config/nginx/appflowy.site.conf ``` # add this to let nginx start without errors events {} # and this (map without http throws errors) http { # Add the docker dns resolver resolver 127.0.0.11 valid=10s; map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { server_name appflowy.h2l.dev; listen 80; underscores_in_headers on; # Don't use these # set $appflowy_cloud_backend "http://127.0.0.1:8000"; # set $gotrue_backend "http://127.0.0.1:9999"; # set $admin_frontend_backend "http://127.0.0.1:3001"; # set $appflowy_web_backend "http://127.0.0.1:3000"; # set $minio_backend "http://127.0.0.1:9001"; # set $minio_api_backend "http://127.0.0.1:9000"; # # Host name for minio, used internally within docker compose # set $minio_internal_host "127.0.0.1:9000"; # Rather let Docker resolve the services from nginx/nginx.conf set $appflowy_cloud_backend "http://appflowy_cloud:8000"; set $gotrue_backend "http://gotrue:9999"; set $admin_frontend_backend "http://admin_frontend:3000"; set $appflowy_web_backend "http://appflowy_web:80"; set $minio_backend "http://minio:9001"; set $minio_api_backend "http://minio:9000"; # Host name for minio, used internally within docker compose set $minio_internal_host "minio:9000"; set $pgadmin_backend "http://pgadmin:80"; ... } } ```

mirror referenced this issue

2026-03-23 23:18:51 +00:00

[PR #6238] [MERGED] feat: cover in database row #7267