AppFlowy [Bug] Import workspace works on the cloud instance, but not on localhost

Bug Description

I'm setting up a self-hosted Appflowy server for myself on my laptop. I tried to import my existing workspace from "local", so I did the following : In my local session, I went to Settings > Manage Data > Backup your workspace Everything's fine, the ZIP is correctly created. Then I switch to "appflowy self-hosted" in cloud settings, with the address http://localhost (hosted on port 80, I have correctly access to the admin panel, the web app, and I can connect and create workspaces in the desktop app) and from the desktop app connected to the Appflowy cloud server running on localhost, when I try to import my workspace, I get an error (see screenshot below) "Invalid file format". So to see if the backup is corrupted or something, I go back to cloud settings and connect to Appflowy cloud, and from there, the import works fine, and I get my data in the cloud instance. From there I also do a new ZIP backup just in case some magic happens behind the scenes.

What I tried:

import a zip backup from my local workspace in my self-hosted instance (doesn't work)
import a zip backup from my cloud account into my self-hosted instance (doesn't work)
import a zip backup from my local workspace to my cloud account (works!)
both in 0.9.7 and 0.9.8

Am I doing something wrong, is this a bug with the "localhost" FQDN ?

How to Reproduce

Install 0.9.7 Create a local workspace (anonymous) Backup as a ZIP Deploy a self-hosted instance on localhost, default ports, default config other than localhost address In the desktop app, connect to your localhost instance by choosing Self-hosted, address "http://localhost" Once in your self-hosted instance, try to import your zip backup

Expected Behavior

It should import the workspace, as it does on the public cloud instance

Operating System

Arch Linux

AppFlowy Version(s)

0.9.7, 0.9.8

Screenshots

Additional Context

No response

Sep 09 '25 16:09 ulysse42

Hi @ulysse42, did you set up Mino on your local deployment? I've received similar reports before. It's a deployment issue.

sending request for url (http://minio:9000/appflowy/import_presigned_url_fa271450-9fee-4ced-935f-4fa44225af0f?x-id=PutObject&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minioadmin%2F20250909%2F%2Fs3%2Faws4_request&X-Amz-Date=20250909T183745Z&X-Amz-Expires=600&X-Amz-SignedHeaders=content-length%3Bcontent-type%3Bhost&X-Amz-Signature=45278baf60cb2ccead8eb8dce3be05ed42c391d1b9797c855312aa9419570054

Sep 10 '25 02:09 LucasXu0

I didn't modify any minio config, the pod is running and healthy yes. I'll check the logs and come back asap.

Sep 10 '25 08:09 ulysse42

cloud logs

{"timestamp":"2025-09-10T10:04:33.499303Z","level":"INFO","fields":{"message":"[access control v2]: queuing add policy:[[\"500160554623569920\", \"workspace::4b44256d-695a-43c1-b141-ac5fbf398f09\", \"r:1\"]]"},"target":"access_control::casbin::enforcer_v2","filename":"libs/access-control/src/casbin/enforcer_v2.rs","line_number":302,"span":{"name":"insert_role"},"spans":[{"client_version":"0.9.8","device_id":"82d73781184546bc8185b4fe213cb46f","method":"POST","path":"/api/import/create","payload_size":89,"request_id":"04232446bb15ef31609a5041194aa0e7","name":"request"},{"name":"insert_role"}]}
{"timestamp":"2025-09-10T10:04:33.499415Z","level":"INFO","fields":{"message":"[access control v2]: Received 1 policy commands"},"target":"access_control::casbin::enforcer_v2","filename":"libs/access-control/src/casbin/enforcer_v2.rs","line_number":151}
{"timestamp":"2025-09-10T10:04:33.506557Z","level":"INFO","fields":{"message":"User:500160554623569920 import new workspace:4b44256d-695a-43c1-b141-ac5fbf398f09, name:_2025-09-10_12-02-04"},"target":"appflowy_cloud::api::data_import","filename":"src/api/data_import.rs","line_number":77,"span":{"client_version":"0.9.8","device_id":"82d73781184546bc8185b4fe213cb46f","method":"POST","path":"/api/import/create","payload_size":89,"request_id":"04232446bb15ef31609a5041194aa0e7","name":"request"},"spans":[{"client_version":"0.9.8","device_id":"82d73781184546bc8185b4fe213cb46f","method":"POST","path":"/api/import/create","payload_size":89,"request_id":"04232446bb15ef31609a5041194aa0e7","name":"request"}]}

worker logs

{"timestamp":"2025-09-10T10:04:59.725799Z","level":"INFO","fields":{"message":"[Import]: Processing task: WorkspaceImportTask { workspace_id: 4b44256d-695a-43c1-b141-ac5fbf398f09, workspace_name: _2025-09-10_12-02-04 }"},"target":"appflowy_worker::import_worker::worker"}
{"timestamp":"2025-09-10T10:04:59.767743Z","level":"ERROR","fields":{"message":"[Import]: failed to import workspace:WorkspaceImportTask { task_id: 1dbde659-b393-4727-9562-487e204b804e, workspace_id: 4b44256d-695a-43c1-b141-ac5fbf398f09, file_size:Some(0.5398731231689453)MB, workspace_name: _2025-09-10_12-02-04, user_name: <redacted>, user_email: <redacted> }: error:Internal(Failed after 1 attempts: Record not found:blob not found\n\nStack backtrace:\n   0: anyhow::kind::Adhoc::new\n   1: appflowy_worker::import_worker::worker::process_task::{{closure}}\n   2: appflowy_worker::import_worker::worker::process_and_ack_task::{{closure}}\n   3: appflowy_worker::import_worker::worker::consume_task::{{closure}}\n   4: appflowy_worker::import_worker::worker::process_upcoming_tasks::{{closure}}::{{closure}}\n   5: tokio::runtime::task::raw::poll\n   6: tokio::task::local::LocalSet::tick\n   7: appflowy_worker::application::create_app::{{closure}}\n   8: <core::pin::Pin<P> as core::future::future::Future>::poll\n   9: appflowy_worker::main\n  10: std::sys::backtrace::__rust_begin_short_backtrace\n  11: std::rt::lang_start::{{closure}}\n  12: main\n  13: <unknown>\n  14: __libc_start_main\n  15: _start)"},"target":"appflowy_worker::import_worker::import_workspace_handler"}
{"timestamp":"2025-09-10T10:05:07.771349Z","level":"ERROR","fields":{"message":"Failed to send import notion report email: Connection error: failed to lookup address information: Temporary failure in name resolution"},"target":"appflowy_worker::import_worker::email_notifier"}

No logs on Minio during the failure, every request is a 200 OK on nginx and gotrue during the failure

Sep 10 '25 10:09 ulysse42

Can you try installing this version: 0.9.9-250909-0457 and then upload the zip file to your self-hosted server again? If it still fails, please upload the log files.

Sep 11 '25 01:09 LucasXu0

No luck, same error. Here are all the logs from the start of the server (I started the server, tried the operation, and then stopped, so there is not much) :

appflowy-cloud-admin_frontend-1.log appflowy-cloud-ai-1.log appflowy-cloud-appflowy_cloud-1.log appflowy-cloud-appflowy_web-1.log appflowy-cloud-appflowy_worker-1.log appflowy-cloud-gotrue-1.log appflowy-cloud-minio-1.log appflowy-cloud-nginx-1.log appflowy-cloud-postgres-1.log appflowy-cloud-redis-1.log

Sep 12 '25 15:09 ulysse42

Commenting as I have the same issue.

Sep 24 '25 20:09 sunilnc

@LucasXu0 hi, do you know if there is a fix for this? This is the only thing holding me back from migrating to AppFlowy (a proper backup mechanism).

Oct 16 '25 13:10 sunilnc

@sunilnc Could you unzip the zip file and attach a screenshot of the file names inside?

Oct 16 '25 14:10 LucasXu0

@LucasXu0 here you go:

Oct 16 '25 14:10 sunilnc

@sunilnc the files are correct. The most likely reason is the .env file. Did you set up the S3 values correctly?

# File Storage
APPFLOWY_S3_CREATE_BUCKET=true
APPFLOWY_S3_USE_MINIO=true
APPFLOWY_S3_MINIO_URL=http://localhost:9000 # 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
# APPFLOWY_S3_REGION=us-east-1

Oct 16 '25 14:10 LucasXu0

@LucasXu0 Mine match what you have there, apart from: APPFLOWY_S3_MINIO_URL=http://localhost:9000 # change this if you are using a different address for minio"

I have this instead:

APPFLOWY_S3_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT}

# =============================================================================
# AppFlowy Cloud - Production Deployment Configuration
# =============================================================================
# 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 localhost with your domain,
# such as mydomain.com.
FQDN=appflowy.mydomain.co.uk

# Change this to https if you are using TLS.
SCHEME=https
# Change this to wss if you are using TLS
WS_SCHEME=wss

APPFLOWY_BASE_URL=${SCHEME}://${FQDN}
APPFLOWY_WEBSOCKET_BASE_URL=${WS_SCHEME}://${FQDN}/ws/v2

# =============================================================================
# 🗄️ DATABASE & CACHE: Core data infrastructure
# =============================================================================

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

# Redis Settings
REDIS_HOST=redis
REDIS_PORT=6379

# =============================================================================
# 🏗️ INFRASTRUCTURE SERVICES: Object storage and networking
# =============================================================================

# MinIO Configuration: S3-compatible object storage for file uploads and attachments
# Docker service discovery: These values are used for container-to-container communication
# MINIO_HOST refers to the Docker Compose service name, not an external domain/IP
# Used by: AppFlowy Cloud, Worker services, AI service, and Admin Frontend
MINIO_HOST=minio
MINIO_PORT=9000

# MinIO/AWS Credentials: Authentication keys for object storage access
# Development: Uses MinIO's default credentials (minioadmin/minioadmin) for quick setup
# Production: MUST be changed to secure, randomly generated credentials for security
# These credentials are used across all services that access file storage
# Security note: Default credentials are well-known and should never be used in production
AWS_ACCESS_KEY=mykey
AWS_SECRET=mysecret

# =============================================================================
# ☁️ APPFLOWY SERVICES: Application service configuration
# =============================================================================

# AppFlowy Cloud Service Configuration
# 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 Service Configuration
# Access Control System: Enables/disables permission-based access control
# Controls workspace access, collaboration permissions, and realtime access restrictions
APPFLOWY_ACCESS_CONTROL=true

# WebSocket Mailbox Configuration: Controls realtime server message handling capacity
# Sets the maximum number of messages that can be queued in the WebSocket actor's mailbox
# Higher values allow more concurrent WebSocket messages but use more memory
# Lower values may cause message drops under high load but reduce memory usage
APPFLOWY_WEBSOCKET_MAILBOX_SIZE=6000

# Database Connection Pool: Maximum number of concurrent PostgreSQL connections
# Controls the size of the database connection pool for the AppFlowy Cloud service
# PostgreSQL has a default limit of ~100 connections total (15 reserved for superuser)
# Higher values improve concurrency but consume more database resources
# Lower values reduce database load but may cause connection timeouts under load
APPFLOWY_DATABASE_MAX_CONNECTIONS=40

# URL that connects to the redis docker container
APPFLOWY_REDIS_URI=redis://${REDIS_HOST}:${REDIS_PORT}

# GoTrue database connection. 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

# =============================================================================
# 🔐 GOTRUE: Authentication service configuration
# =============================================================================

# GoTrue Admin Credentials
# 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=myapppassword

# JWT Configuration
# Authentication key, change this and keep the key safe and secret
GOTRUE_JWT_SECRET=mypassword

# Expiration time in seconds for the JWT token
GOTRUE_JWT_EXP=1209600

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

# User Registration & Login Settings
# 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=false

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

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

# Email Templates
# 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=

# =============================================================================
# 🎛️ ADMIN FRONTEND: Management interface configuration
# =============================================================================

# 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://appflowy_cloud: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

# =============================================================================
# 📧 EMAIL CONFIGURATION: SMTP settings (optional but recommended for production)
# =============================================================================

# 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=587
[email protected]
GOTRUE_SMTP_PASS=myapppassword
[email protected]

# 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=587
[email protected]
[email protected]
APPFLOWY_MAILER_SMTP_PASSWORD=myapppassword
APPFLOWY_MAILER_SMTP_TLS_KIND=opportunistic # "needone" "wrapper" "required" "opportunistic"

# =============================================================================
# 🔑 OAUTH PROVIDERS: Third-party authentication (optional)
# =============================================================================
# Refer to this for details: https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/AUTHENTICATION.md

# Google OAuth2
GOTRUE_EXTERNAL_GOOGLE_ENABLED=true
GOTRUE_EXTERNAL_GOOGLE_CLIENT_ID=myclientid
GOTRUE_EXTERNAL_GOOGLE_SECRET=mysecret
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: S3/MinIO configuration (required for file uploads)
# =============================================================================

# Storage Architecture Control: Determines the file storage backend for the entire system
# Affects: User uploads, document attachments, collaboration snapshots, AI embeddings, import/export files
# When true: Uses MinIO (S3-compatible) with path-style URLs and MinIO endpoint configuration
# When false: Uses AWS S3 with region-based configuration and standard S3 URLs
# Production options: Keep true for self-hosted MinIO, set false for AWS S3
APPFLOWY_S3_USE_MINIO=true

# Bucket Management: Controls automatic bucket creation during AppFlowy startup
# When true: AppFlowy automatically creates the storage bucket if it doesn't exist
# When false: Assumes bucket exists and was created externally (recommended for production)
APPFLOWY_S3_CREATE_BUCKET=true

# MinIO Endpoint Configuration: URL for MinIO API access
# Uses Docker service discovery variables for container networking
# Format combines MINIO_HOST and MINIO_PORT for internal service communication
# Change this URL if using external MinIO instance or different networking setup
APPFLOWY_S3_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT}

# Storage Authentication: Maps to the MinIO/AWS credentials defined above
# These reference the AWS_ACCESS_KEY and AWS_SECRET variables for consistency
# All AppFlowy services use these credentials to access the file storage backend
APPFLOWY_S3_ACCESS_KEY=${AWS_ACCESS_KEY}
APPFLOWY_S3_SECRET_KEY=${AWS_SECRET}

# Storage Bucket: Default bucket name for all AppFlowy file storage
# Contains: User files, document attachments, collaboration data, AI embeddings
# Must exist in both MinIO and AWS S3 configurations
APPFLOWY_S3_BUCKET=appflowy

# AWS S3 Configuration: Required only when APPFLOWY_S3_USE_MINIO=false
# Uncomment and configure these settings when using AWS S3 instead of MinIO
# APPFLOWY_S3_REGION=us-east-1

# MinIO Presigned URL Endpoint: External URL for client-side file access (optional)
# Enables direct file uploads/downloads from AppFlowy clients through presigned URLs
# Set this to your public MinIO endpoint if using nginx proxy configuration
# Format: Uses the external base URL with /minio-api path for API access
# APPFLOWY_S3_PRESIGNED_URL_ENDPOINT=${APPFLOWY_BASE_URL}/minio-api

# =============================================================================
# 🤖 AI FEATURES: Optional AI capabilities (configure only if needed)
# =============================================================================

# AppFlowy AI
# OpenAI API Authentication: Required API key for AI-powered features and semantic search
# Controls access to OpenAI's embedding models (text-embedding-3-small) for document indexing
# and ChatGPT models (gpt-4o-mini default) for search result summarization
# When configured: Enables semantic document search, AI-powered search summaries, and document embeddings
# When empty: AI features are disabled but core AppFlowy functionality remains fully operational
AI_OPENAI_API_KEY=

# If no summary model is provided, there will be no search summary when using AI search.
AI_OPENAI_API_SUMMARY_MODEL=

# 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 Service Configuration (Docker container defaults)
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_APPFLOWY_BUCKET_NAME=${APPFLOWY_S3_BUCKET}
AI_APPFLOWY_HOST=${APPFLOWY_BASE_URL}
AI_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT}

# Embedding Configuration
APPFLOWY_EMBEDDING_CHUNK_SIZE=2000
APPFLOWY_EMBEDDING_CHUNK_OVERLAP=200

# =============================================================================
# ⚙️ WORKER SERVICES: Background processing (good defaults for production)
# =============================================================================

# AppFlowy Indexer (for search functionality)
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 Collaboration Service Configuration:
# Controls real-time collaboration behavior and performance
# Multi-thread: Whether collaboration service uses multiple threads (can be true for production)
# When deployed as standalone service, can be set to true for better performance
APPFLOWY_COLLABORATE_MULTI_THREAD=false

# Remove batch size: Number of inactive collaboration groups to remove in a single batch (default: 100)
# Higher values improve cleanup efficiency but may cause temporary blocking
APPFLOWY_COLLABORATE_REMOVE_BATCH_SIZE=100

# AppFlowy Worker Service
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}

# =============================================================================
# 🌐 WEB FRONTEND: AppFlowy Web interface
# =============================================================================

# 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

# =============================================================================
# 🗄️ PGADMIN: Database Management Web Interface
# =============================================================================

# PgAdmin credentials for database management web UI
# You can access pgadmin at http://your-host/pgadmin
# Use the APPFLOWY_DATABASE_URL values when connecting to the database
[email protected]
PGADMIN_DEFAULT_PASSWORD=password

# =============================================================================
# 🌐 NGINX: Reverse proxy and web server configuration
# =============================================================================

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

# =============================================================================
# 🛠️ INFRASTRUCTURE: Networking, logging, and admin tools
# =============================================================================

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

# Cloudflare Tunnel (Advanced Networking)
# Leave empty unless you're using Cloudflare tunnel for secure connections
CLOUDFLARE_TUNNEL_TOKEN=

# Enable AI tests in production environment (usually false)
# Set to true only if you want to run AI-related tests in production
AI_TEST_ENABLED=false

Oct 16 '25 14:10 sunilnc

@sunilnc You can change APPFLOWY_S3_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT} to APPFLOWY_S3_MINIO_URL=http://localhost:9000. The port depends on your local configuration.

Oct 17 '25 01:10 LucasXu0

@LucasXu0, replacing that line seems to break my instance of AppFlowy. I get this message unless I revert it to the original line:

I have checked my .env and I am using port 9000:

MINIO_HOST=minio
MINIO_PORT=9000

Oct 17 '25 09:10 sunilnc

It shouldn't affect your connection. Did you deploy the server successfully after changing that line? You can upload your log files from the settings page. This will show the error that's preventing you from connecting to the server.

Oct 17 '25 10:10 LucasXu0

After I made the change to .env file, I ran:

docker compose down

Waited for all the containers to stop, and then I ran:

docker compose up -d

Oct 17 '25 10:10 sunilnc

Did you try using the dev.env as the default template?

Oct 17 '25 10:10 LucasXu0

@LucasXu0

Should I copy across all the default config from dev.env to .env and then add my specific config?

And do the same by copying the default config from docker-compose-dev.yml to docker-compose.yml and then run:

docker-compose up -d

Oct 17 '25 10:10 sunilnc

@sunilnc

Should I copy across all the default config from dev.env to .env and then add my specific config?

Yes.

And do the same by copying the default config from docker-compose-dev.yml to docker-compose.yml and then run:

You can run the docker-compose up -d directly after changing the .env.

Oct 17 '25 13:10 LucasXu0