mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 21:00:19 +00:00
[GH-ISSUE #8211] [Bug] Import workspace works on the cloud instance, but not on localhost #12065
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#12065
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ulysse42 on GitHub (Sep 9, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8211
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:
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
@LucasXu0 commented on GitHub (Sep 10, 2025):
Hi @ulysse42, did you set up Mino on your local deployment? I've received similar reports before. It's a deployment issue.
@ulysse42 commented on GitHub (Sep 10, 2025):
I didn't modify any minio config, the pod is running and healthy yes. I'll check the logs and come back asap.
@ulysse42 commented on GitHub (Sep 10, 2025):
cloud logs
worker logs
No logs on Minio during the failure, every request is a 200 OK on nginx and gotrue during the failure
@LucasXu0 commented on GitHub (Sep 11, 2025):
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.
@ulysse42 commented on GitHub (Sep 12, 2025):
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
@sunilnc commented on GitHub (Sep 24, 2025):
Commenting as I have the same issue.
@sunilnc commented on GitHub (Oct 16, 2025):
@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).
@LucasXu0 commented on GitHub (Oct 16, 2025):
@sunilnc Could you unzip the zip file and attach a screenshot of the file names inside?
@sunilnc commented on GitHub (Oct 16, 2025):
@LucasXu0 here you go:

@LucasXu0 commented on GitHub (Oct 16, 2025):
@sunilnc the files are correct. The most likely reason is the
.envfile. Did you set up the S3 values correctly?@sunilnc commented on GitHub (Oct 16, 2025):
@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}@LucasXu0 commented on GitHub (Oct 17, 2025):
@sunilnc You can change
APPFLOWY_S3_MINIO_URL=http://${MINIO_HOST}:${MINIO_PORT}toAPPFLOWY_S3_MINIO_URL=http://localhost:9000. The port depends on your local configuration.@sunilnc commented on GitHub (Oct 17, 2025):
@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:
@LucasXu0 commented on GitHub (Oct 17, 2025):
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.
@sunilnc commented on GitHub (Oct 17, 2025):
After I made the change to .env file, I ran:
docker compose downWaited for all the containers to stop, and then I ran:
docker compose up -d@LucasXu0 commented on GitHub (Oct 17, 2025):
Did you try using the dev.env as the default template?
@sunilnc commented on GitHub (Oct 17, 2025):
@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@LucasXu0 commented on GitHub (Oct 17, 2025):
@sunilnc
Yes.
You can run the
docker-compose up -ddirectly after changing the.env.