AppFlowy AppFlowy Cloud Self-Hosting: Persistent "Incorrect Password" After Exhaustive Troubleshooting

Problem Description: Despite successfully deploying AppFlowy Cloud via Docker Compose on Proxmox LXC, resolving multiple critical setup issues (storage, CPU compatibility, network, and service startup errors), I am unable to log in to the AppFlowy web app or desktop client. The system consistently returns "Your password is incorrect, please try again," even after confirming the admin user exists in the database with the correct password.

Environment Information:

Proxmox VE Version: pve-manager/8.4.1
Proxmox Kernel: Linux 6.8.12-10-pve
Proxmox Node (Hosting AppFlowy LXC): motivation
- CPU: 16 x 12th Gen Intel(R) Core(TM) i7-1260P (Fully compatible with x86-64-v2/v3/v4 instruction sets)
- RAM: 4GB
- Storage: LVM-Thin (pve/data) on a 4TB NVMe SSD.
AppFlowy LXC ID: CT 112
- Base OS: Ubuntu Server LTS 22.04
- Static IP: 192.168.3.105
- Docker Version: Latest stable (installed via official script).
- AppFlowy Cloud Version: latest (from AppFlowy-IO/AppFlowy-Cloud GitHub repository).

Network Configuration:

Topology: FioS Router --> pfSense firewall (192.168.2.1 WiFi, 192.168.3.1 Lab) --> Proxmox cluster (spark, motivation) --> motivation node --> appflowy-ct (LXC)
pfSense: Configured with specific Firewall Pass rules on the LAB interface for 192.168.3.105 to allow ICMP and UDP (Port 53), and TCP/UDP for general internet access.
LXC DNS: nameserver 192.168.3.1, nameserver 8.8.8.8, nameserver 1.1.1.1 in /etc/resolv.conf.
Time Sync: Confirmed correct time synchronization across LXC, Proxmox host, and client machine.

Chronological Troubleshooting & Resolutions:

Initial Problem: no such logical volume pve/data (500) when creating LXC on spark node.
- Cause: spark node's storage.cfg had lvmthin: local-lvm defined, but no underlying LVM-Thin pool existed.
- Resolution: Removed the lvmthin: local-lvm entry from spark's storage.cfg. Created LXC using ZFS storage (rpool-data) on spark.
Second Problem: Fatal glibc error: CPU does not support x86-64-v2 in minio container logs.
- Cause: spark node (Mac Pro 3,1) CPU lacked SSE4.2 instruction set required by modern glibc builds in Docker images.
- Resolution (Corrected Path): Performed vzdump backup of appflowy-ct on spark. Transferred backup to motivation's local storage. Added lvmthin: local-lvm definition to motivation's storage.cfg. Restored appflowy-ct backup to local-lvm on motivation. All core Docker services started (Up and healthy).
Third Problem (Current): Persistent "Your password is incorrect, please try again" on login (both web app and desktop client).
- Troubleshooting Steps for "Incorrect Password" (Chronological):
  - Initial .env Configuration:
    - APPFLOWY_BASE_URL=http://192.168.3.105:3060
    - [email protected] (Replaced the actual value for submission here)
    - GOTRUE_ADMIN_PASSWORD=[YOUR_SIMPLE_PASSWORD_HERE](Replaced the actual value for submission here)
    - GOTRUE_JWT_SECRET=[YOUR_GOTRUE_JWT_SECRET_HERE] (original was specific string)
    - GOTRUE_DISABLE_SIGNUP=true
    - GOTRUE_LOG_LEVEL=debug (though debug output did not appear in logs).
    - Other critical variables in .env like POSTGRES_PASSWORD=[YOUR_POSTGRES_PASSWORD] (original password), AWS_SECRET=[YOUR_MINIO_PASSWORD] (original minioadmin), etc., were set.
  - GoTrue Admin user already exists: Initially, gotrue logs showed "Admin user already exists. Skipping..." preventing password update.
    - Resolution: Performed sudo docker compose down -v to wipe all Docker volumes (including PostgreSQL data), forcing a fresh database state for user creation. gotrue logs then showed "Creating admin user for gotrue..." without "skipping".
  - Password Characters: Attempted with GOTRUE_ADMIN_PASSWORD='my password with spaces' (quoted) and later simplepassword123 (alphanumeric only).
  - Web App Behavior & Email Verification: Web app login gave "Request Failed with Status Code 500" and asked for email verification.
  - SMTP Configuration Errors:
    - Instance 1 (GoTrue): gotrue logs showed FATAL: assigning GOTRUE_SMTP_PORT to Port: converting '' to type int.
    - Cause: docker-compose.yml was explicitly passing ${GOTRUE_SMTP_PORT} (which expanded to empty string from .env) to gotrue.
    - Resolution: Deleted GOTRUE_SMTP_HOST, GOTRUE_SMTP_PORT, GOTRUE_SMTP_USER, GOTRUE_SMTP_PASS, GOTRUE_SMTP_ADMIN_EMAIL lines from gotrue's environment: section in docker-compose.yml.
    - Instance 2 (AppFlowy Cloud): appflowy_cloud logs then showed the same FATAL error regarding APPFLOWY_MAILER_SMTP_PORT.
    - Cause: docker-compose.yml was explicitly passing ${APPFLOWY_MAILER_SMTP_PORT} (empty string) to appflowy_cloud.
    - Resolution: Deleted APPFLOWY_MAILER_SMTP_HOST, APPFLOWY_MAILER_SMTP_PORT, APPFLOWY_MAILER_SMTP_USERNAME, APPFLOWY_MAILER_SMTP_EMAIL, APPFLOWY_MAILER_SMTP_PASSWORD, APPFLOWY_MAILER_SMTP_TLS_KIND lines from appflowy_cloud's environment: section in docker-compose.yml.
    - Outcome: All services are now Up and healthy. Web app no longer asks for email verification.
  - Manual Password Update in DB (Final Attempt):
    - Action: Used python3 bcrypt to generate a new hash for simplepassword123.
    - Action: Directly updated the encrypted_password for [email protected] in the auth.users table in PostgreSQL. Confirmed update via SELECT query. Example SELECT output:
```
id                                   |       email              |          created_at           | last_sign_in_at |    email_confirmed_at     |                 encrypted_password
--------------------------------------+--------------------------+-------------------------------+-----------------+-------------------------------+--------------------------------------------------------------
[UNIQUE_USER_ID_HERE]                 | [email protected] | 2025-05-22 18:46:52.703825+00 |                 | 2025-05-22 18:46:52.705075+00 | [YOUR_NEW_HASH_HERE]
```
    - Outcome: Still "Your password is incorrect, please try again" on both web app and desktop client.

Current Status: All AppFlowy Cloud services are running and appear healthy in docker ps. The database user ([email protected]) exists with a confirmed, manually updated password hash. There are no critical errors in gotrue or appflowy_cloud logs indicating startup failure or password verification issues. The web app is accessible, but login consistently fails with "Incorrect Password."

Request for Assistance: Given the exhaustive troubleshooting and verification that the user exists and the password is correct in the database, the persistent "incorrect password" error is highly unusual. It points to a very subtle issue during the password verification step that is not being logged as an error, or a client-side interaction problem.

Any insights or suggestions for further debugging steps would be greatly appreciated. Thank you.

May 22 '25 20:05 AristotleSays

Thanks for the detailed debugging steps. I am assuming, that by web, you are trying to log in to the admin panel (/console), instead of the web version of the Appflowy (/), because the web version doesn't support password login at the moment (there is no field to even provide the password).

If that is the case, I would try debugging this using the admin panel first. Try checking the browser dev console, and see which API endpoint returns the error. It is likely going to be the same reason why the login failed for the desktop app.

May 23 '25 00:05 khorshuheng

I am self-hosting the server. Can you provide more details? I have exhausted my troubleshooting skills. Please give me clear instructions (step-by-step, if possible) as I am new to AppFlowy application. I didn't even know this application existed until 2 days.

May 24 '25 03:05 AristotleSays

What I meant is, try logging into admin panel using username and password. The admin panel should be on /console, if setup correctly. And if you are not able to do so, the browser console should tell you more on the actual error.

May 24 '25 04:05 khorshuheng

i have the exact same issue and did exactly the same as OP. macos Sequoia 15.5; Docker Compose, pull latest version, everything works, every service shows healthy and up, set a user + pw in the .env file (restarted) and it does not work with provided credentials. I deleted everything multiple times and also tried it multiple times with the [email protected] template that's already set in the .env file. In Web there is no possibility to sign in without a magic link and with the /console i just get a random string, which stretches over the whole screen (can't copy/paste it). In the App it shows the incorrect password message, no matter how many users i create, how simple / hard the pw is, with or without special characters.

May 26 '25 13:05 raylinger

If you get the long random string, it is probably issue with verifying the token, which you might see error either in the AppFlowy cloud server, or on the browser dev console.

Also, just to eliminate some of the more common issues - make sure you pull the latest image by docker compose pull. In addition, the password of the admin user does not get overwritten when you change the env variable.

May 26 '25 14:05 khorshuheng

hello, thank you for the feedback. At this point i am positive, that i have tried everything. The things you mentioned, are common sense. Either i miss something in the .env that needs to be changed/configured, or it simply is broken. I could do a no-cut setup video and upload if it is not believable... :)

Update: when i type some user that does not exist, i get a corresponding message, invalid user credentials. If i type the correct user and password, i get the long string. there is no information in the dev console to read except generic error 500

May 29 '25 11:05 raylinger

Hello,

i have exactly the same problem, with a similar setup.

When i try to log into /console, with the default login ([email protected]) I receive this message as response in the Firefox console:

Reqwest(reqwest::Error { kind: Request, url: "http://appflowy_cloud:8000/api/user/verify/", 
eyJhbGciOiJIUzI1*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************",
source: hyper_util::client::legacy::Error(Connect, ConnectError("dns error", 
Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" })) })

When I change the ADMIN_FRONTEND_APPFLOWY_CLOUD_URL variable in the .env file, to the local IP address of my AppFlowy instance, then I receive this message:

Reqwest(reqwest::Error { kind: Request, url: "http://192.168.2.42:8000/api/user/verify/
eyJhbGciOiJIUzI1***********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************", 
source: hyper_util::client::legacy::Error(Connect, 
ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })) })

(Filled the string with *)

i don't know what is the problem here.

Jun 04 '25 15:06 J-P-Meth

Chances are, AppFlowy cloud service failed to reach some service. For example, if you have modified the name of the gotrue service but didn't modify the env accordingly. There should be more details in the logs in the AppFlowy cloud service.

Jun 04 '25 15:06 khorshuheng

I can't find any errors in the docker logs itself.

What do you mean with 'modified the name of the gotrue service'?

When i do a docker ps -a i get this:

CONTAINER ID   IMAGE                                COMMAND                  CREATED          STATUS                     PORTS                                                                          NAMES
1fb8416f554e   appflowyinc/appflowy_web:latest      "/docker-entrypoint.…"   45 minutes ago   Up 44 minutes              80/tcp                                                                         appflowy-cloud-appflowy_web-1
cc214d096739   appflowyinc/admin_frontend:latest    "admin_frontend"         45 minutes ago   Up 44 minutes              3000/tcp                                                                       appflowy-cloud-admin_frontend-1
ccf05851d58d   appflowyinc/appflowy_cloud:latest    "appflowy_cloud"         45 minutes ago   Up 44 minutes              8000/tcp                                                                       appflowy-cloud-appflowy_cloud-1
f9db0c15fd76   appflowyinc/appflowy_ai:latest       "sh -c 'uvicorn main…"   45 minutes ago   Up 44 minutes              5001/tcp                                                                       appflowy-cloud-ai-1
21821794d889   appflowyinc/appflowy_worker:latest   "appflowy_worker"        45 minutes ago   Up 44 minutes                                                                                             appflowy-cloud-appflowy_worker-1
9204b45c7b24   appflowyinc/gotrue:latest            "./start.sh"             45 minutes ago   Up 44 minutes (healthy)                                                                                   appflowy-cloud-gotrue-1
6e7a83f5fbc5   redis                                "docker-entrypoint.s…"   45 minutes ago   Up 45 minutes              6379/tcp                                                                       appflowy-cloud-redis-1
f4ec51656bb2   pgvector/pgvector:pg16               "docker-entrypoint.s…"   45 minutes ago   Up 45 minutes (healthy)    5432/tcp                                                                       appflowy-cloud-postgres-1
e90b89a8a1a8   nginx                                "/docker-entrypoint.…"   45 minutes ago   Up 45 minutes              0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp   appflowy-cloud-nginx-1
cee0e1a50af9   minio/minio                          "/usr/bin/docker-ent…"   45 minutes ago   Up 45 minutes              9000/tcp                                                                       appflowy-cloud-minio-1
3f30d3eddd5c   dpage/pgadmin4                       "/entrypoint.sh"         6 weeks ago      Exited (0) 3 hours ago                                                                                    appflowy-cloud-pgadmin-1
b4df702bdcb9   5b63066c6b1c                         "/bin/sh -c 'cargo b…"   6 weeks ago      Exited (255) 6 weeks ago

Is it correct, that there is no Ports for the gotrue container?

Jun 06 '25 11:06 J-P-Meth

Hmm...ok, on the first glance it does look correct. Could you share your .env variable ( without the sensitive information)?

Jun 06 '25 11:06 khorshuheng

I am also assuming that, there isn't any other proxy in front?

Jun 06 '25 11:06 khorshuheng

Thanks alot for the fast response.

I don't use any other proxy in front.

My .env file looks like this.

# This file is a template for docker compose deployment
# Copy this file to .env and change the values as needed

# Fully qualified domain name for the deployment. Replace appflowy.localhost with your domain,
# such as mydomain.com.
FQDN=192.168.2.42
# Change this to https if you wish to enable TLS.
SCHEME=http
APPFLOWY_BASE_URL=${SCHEME}://${FQDN}

# PostgreSQL Settings
POSTGRES_HOST=postgres
POSTGRES_USER=postgres
POSTGRES_PASSWORD=************
POSTGRES_PORT=5432
POSTGRES_DB=postgres

# Redis Settings
REDIS_HOST=redis
REDIS_PORT=6379

# Minio Host
MINIO_HOST=minio
MINIO_PORT=9000

AWS_ACCESS_KEY=minioadmin
AWS_SECRET=minioadmin

# AppFlowy Cloud
## URL that connects to the gotrue docker container
APPFLOWY_GOTRUE_BASE_URL=http://gotrue:9999
## URL that connects to the postgres docker container. If your password contains special characters, instead of using ${POSTGRES_PASSWORD},
## you will need to convert them into url encoded format. For example, `p@ssword` will become `p%40ssword`.
APPFLOWY_DATABASE_URL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
APPFLOWY_ACCESS_CONTROL=true
APPFLOWY_WEBSOCKET_MAILBOX_SIZE=6000
APPFLOWY_DATABASE_MAX_CONNECTIONS=40
## URL that connects to the redis docker container
APPFLOWY_REDIS_URI=redis://${REDIS_HOST}:${REDIS_PORT}

# admin frontend
## URL that connects to redis docker container
ADMIN_FRONTEND_REDIS_URL=redis://${REDIS_HOST}:${REDIS_PORT}
## URL that connects to gotrue docker container
ADMIN_FRONTEND_GOTRUE_URL=http://gotrue:9999
## URL that connects to the cloud docker container
ADMIN_FRONTEND_APPFLOWY_CLOUD_URL=http://192.168.2.42:8000
## Base Url for the admin frontend. If you use the default Nginx conf provided here, this value should be /console.
## If you want to keep the previous behaviour where admin frontend is served at the root, don't set this env variable,
## or set it to empty string.
ADMIN_FRONTEND_PATH_PREFIX=/console

# authentication key, change this and keep the key safe and secret
# self defined key, you can use any string
GOTRUE_JWT_SECRET=hello456
# Expiration time in seconds for the JWT token
GOTRUE_JWT_EXP=7200

# User sign up will automatically be confirmed if this is set to true.
# If you have OAuth2 set up or smtp configured, you can set this to false
# to enforce email confirmation or OAuth2 login instead.
# If you set this to false, you need to either set up SMTP
GOTRUE_MAILER_AUTOCONFIRM=true

# Optional. You can provide a public http link (eg. github) to customize your magic link template.
# Refer to https://github.com/supabase/auth?tab=readme-ov-file#configuration for details on how to create a custom email template.
GOTRUE_MAILER_TEMPLATES_MAGIC_LINK=

# Number of emails that can be per minute
GOTRUE_RATE_LIMIT_EMAIL_SENT=100

# If you intend to use mail confirmation, you need to set the SMTP configuration below
# You would then need to set GOTRUE_MAILER_AUTOCONFIRM=false
# Check for logs in gotrue service if there are any issues with email confirmation
# Note that smtps will be used for port 465, otherwise plain smtp with optional STARTTLS
GOTRUE_SMTP_HOST=smtp.gmail.com
GOTRUE_SMTP_PORT=465
GOTRUE_SMTP_USER=email_sender@some_company.com
GOTRUE_SMTP_PASS=email_sender_password
GOTRUE_SMTP_ADMIN_EMAIL=comp_admin@some_company.com

# This user will be created when GoTrue starts successfully
# You can use this user to login to the admin panel
[email protected]
GOTRUE_ADMIN_PASSWORD=password

# Set this to true if users can only join by invite
GOTRUE_DISABLE_SIGNUP=false

# External URL where the GoTrue service is exposed.
API_EXTERNAL_URL=${APPFLOWY_BASE_URL}/gotrue

# GoTrue connect to postgres using this url. If your password contains special characters,
# instead of using ${POSTGRES_PASSWORD}, use the url encoded version. For example, `p@ssword` will become `p%40ssword`
GOTRUE_DATABASE_URL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}?search_path=auth

# Refer to this for details: https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/AUTHENTICATION.md
# Google OAuth2
GOTRUE_EXTERNAL_GOOGLE_ENABLED=false
GOTRUE_EXTERNAL_GOOGLE_CLIENT_ID=
GOTRUE_EXTERNAL_GOOGLE_SECRET=
GOTRUE_EXTERNAL_GOOGLE_REDIRECT_URI=${API_EXTERNAL_URL}/callback
# GitHub OAuth2
GOTRUE_EXTERNAL_GITHUB_ENABLED=false
GOTRUE_EXTERNAL_GITHUB_CLIENT_ID=
GOTRUE_EXTERNAL_GITHUB_SECRET=
GOTRUE_EXTERNAL_GITHUB_REDIRECT_URI=${API_EXTERNAL_URL}/callback
# Discord OAuth2
GOTRUE_EXTERNAL_DISCORD_ENABLED=false
GOTRUE_EXTERNAL_DISCORD_CLIENT_ID=
GOTRUE_EXTERNAL_DISCORD_SECRET=
GOTRUE_EXTERNAL_DISCORD_REDIRECT_URI=${API_EXTERNAL_URL}/callback
# Apple OAuth2
GOTRUE_EXTERNAL_APPLE_ENABLED=false
GOTRUE_EXTERNAL_APPLE_CLIENT_ID=
GOTRUE_EXTERNAL_APPLE_SECRET=
GOTRUE_EXTERNAL_APPLE_REDIRECT_URI=${API_EXTERNAL_URL}/callback
# SAML 2.0. Refer to https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/OKTA_SAML.md for example using Okta.
GOTRUE_SAML_ENABLED=false
GOTRUE_SAML_PRIVATE_KEY=

# File Storage
# Create the bucket if not exists on AppFlowy Cloud start up.
# Set this to false if the bucket has been created externally.
APPFLOWY_S3_CREATE_BUCKET=true
# This is where storage like images, files, etc. will be stored.
# By default, Minio is used as the default file storage which uses host's file system.
# Keep this as true if you are using other S3 compatible storage provider other than AWS.
APPFLOWY_S3_USE_MINIO=true
APPFLOWY_S3_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT} # change this if you are using a different address for minio
APPFLOWY_S3_ACCESS_KEY=${AWS_ACCESS_KEY}
APPFLOWY_S3_SECRET_KEY=${AWS_SECRET}
APPFLOWY_S3_BUCKET=appflowy
# Uncomment this if you are using AWS S3
# APPFLOWY_S3_REGION=us-east-1
# Uncomment this if you are using the Minio service hosted within this docker compose file
# This is so that, the presigned URL generated by AppFlowy Cloud will use the publicly availabe minio endpoint.
# APPFLOWY_S3_PRESIGNED_URL_ENDPOINT=${APPFLOWY_BASE_URL}/minio-api

# AppFlowy Cloud Mailer
# Note that smtps (TLS) is always required, even for ports other than 465
APPFLOWY_MAILER_SMTP_HOST=smtp.gmail.com
APPFLOWY_MAILER_SMTP_PORT=465
APPFLOWY_MAILER_SMTP_USERNAME=email_sender@some_company.com
APPFLOWY_MAILER_SMTP_EMAIL=email_sender@some_company.com
APPFLOWY_MAILER_SMTP_PASSWORD=email_sender_password
APPFLOWY_MAILER_SMTP_TLS_KIND=wrapper # "none" "wrapper" "required" "opportunistic"

# Log level for the appflowy-cloud service
RUST_LOG=info

# PgAdmin
# Optional module to manage the postgres database
# You can access the pgadmin at http://your-host/pgadmin
# Refer to the APPFLOWY_DATABASE_URL for password when connecting to the database
[email protected]
PGADMIN_DEFAULT_PASSWORD=************

# Portainer (username: admin)
PORTAINER_PASSWORD=************

# Cloudflare tunnel token
CLOUDFLARE_TUNNEL_TOKEN=

# NGINX
# Optional, change this if you want to use custom ports to expose AppFlowy
NGINX_PORT=80
NGINX_TLS_PORT=443

# AppFlowy AI
# Standard OpenAI API:
# Set your API key here if you are using the standard OpenAI API.
AI_OPENAI_API_KEY=openai_api_key
# If no summary model is provided, there will be no search summary when using AI search.
AI_OPENAI_API_SUMMARY_MODEL=
APPFLOWY_EMBEDDING_CHUNK_SIZE=2000
APPFLOWY_EMBEDDING_CHUNK_OVERLAP=200

# Azure-hosted OpenAI API:
# If you're using a self-hosted OpenAI API via Azure, leave AI_OPENAI_API_KEY empty
# and set the following Azure-specific variables instead. If both are set, the standard OpenAI API will be used.
AI_AZURE_OPENAI_API_KEY=
AI_AZURE_OPENAI_API_BASE=
AI_AZURE_OPENAI_API_VERSION=

AI_ANTHROPIC_API_KEY=
AI_SERVER_PORT=5001
AI_SERVER_HOST=ai
AI_DATABASE_URL=postgresql+psycopg://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
AI_REDIS_URL=redis://${REDIS_HOST}:${REDIS_PORT}
AI_TEST_ENABLED=false
AI_APPFLOWY_BUCKET_NAME=${APPFLOWY_S3_BUCKET}
AI_APPFLOWY_HOST=${APPFLOWY_BASE_URL}
AI_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT}

# AppFlowy Indexer
APPFLOWY_INDEXER_ENABLED=true
APPFLOWY_INDEXER_DATABASE_URL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
APPFLOWY_INDEXER_REDIS_URL=redis://${REDIS_HOST}:${REDIS_PORT}
APPFLOWY_INDEXER_EMBEDDING_BUFFER_SIZE=5000

# AppFlowy Collaborate
APPFLOWY_COLLABORATE_MULTI_THREAD=false
APPFLOWY_COLLABORATE_REMOVE_BATCH_SIZE=100

# AppFlowy Worker
APPFLOWY_WORKER_REDIS_URL=redis://${REDIS_HOST}:${REDIS_PORT}
APPFLOWY_WORKER_DATABASE_URL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
APPFLOWY_WORKER_DATABASE_NAME=${POSTGRES_DB}

# AppFlowy Web
# If your AppFlowy Web is hosted on a different domain, update this variable to the correct domain
APPFLOWY_WEB_URL=${APPFLOWY_BASE_URL}
# If you are running AppFlowy Web locally for development purpose, use the following value instead
# APPFLOWY_WEB_URL=http://localhost:3000

Jun 06 '25 12:06 J-P-Meth

Try changing the admin AppFlowy cloud service back to the original value (appflowy_cloud) again. One possibility that I can think of, is that, at the time when you try to login, the container is somehow not ready yet.

Basically the error message means that the admin frontend service is not able to send a http request to appflowy_cloud:8000 - which shouldnt be the case if the container is up and running.

And I am also assuming that, you are not running docker compose in host network mode?

Jun 06 '25 12:06 khorshuheng

The login works now :)

Thank you very much.

I don't know why it was not working before (with the value appflowy_cloud) I don't running docker compose in host network mode.

The sync between Linux App and the ios App is not working properly. I need to log out and log in again, that the client is syncing.

But that is a other Problem.

Thanks a lot again.

Jun 06 '25 14:06 J-P-Meth

@J-P-Meth , I'm closing this issue for now. We'll be rolling out a new syncing protocol soon, which will resolve many of the past issues and offer more reliable performance. We look forward to getting your feedback!

Jun 13 '25 04:06 annieappflowy