Any ideas why the import is not working while the export is?

[taubers]

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

I’m running the 1.30.1 version on Docker.

If you are self-hosting, which installation method do you use to run Baserow?

I’m using Docker version 24.0.6, build ed223bc

Installed on Debian.

What are the exact steps to reproduce this issue?

Export data of one workspace (creates ZIP file)
Import data in another workspace (importing the created ZIP file)

Attach screenshots, videos, or logs that demonstrate the issue.

[Przemek]

Hey @taubers

Do can you try exporting only structure and then importing it?

[flow]

Hi @Przemek, I’m having the same problem as OP above. I tried both the complete workspace as well as the empty dataset - both fail due to bad signatures?

[flow]

hi @taubers, were you able to solve the issue? I seem to be stuck in a similar way! many thanks, F

[taubers]

I solved it using this (more technical) approach:

Export/import database

Hi, I have installed baserow in my pre-production cluster and create some tables in a database. I’m using docker images baserow:1.10 I now install basrow in my production environment and want to migrate database from preproduction to production I tried to export each tables and import them in the production baserow but table field are lost (type , fk …) I tried to copy data from /baserow/date but the container failed to start How to migrate database from one cluster to another ?

[qtld]

Hello,
Same issue here, but I’m not sure I can do the technical solution since I’m trying to move from the baserow-hosted to the self-hosted.
Has anyone else found another solution ?

I must specify that when I’m trying to import a full Baserow workspace I have exactly the same message than above👆 but when I’m trying to import a “Structure Only” workspace i’ve got :

Action not completed.
Something went wrong during the import_applications job execution.

Many thanks !

[olgatrykush]

@Przemek could you please take a look here?

[Przemek]

@flow to solve issue with bad signature you need to login as admin settings you can disable signature check

@qtld

Does that happen when you try to import this workspace into baserow too?
Do you have access to logs on your instance - depend if it’s all in one or multiple docker containers - interesting one is export worker one.

[patrickg]

FWIW I’m having the same issue here: Errors when trying to import a Hosted Baserow database

There seems to issues when trying to import a SaaS-hosted baserow export into a self-hosted baserow instance.