New table from CSV

[inbredtom]

Describe the bug
Creating a new table from CSV does not work.
Once file is selected or dragged into browser, I get a green box with a black cross.
No obvious errors in docker logs.

To Reproduce
New Base -> New table -> Import Data -> Local Files -> a csv file with 2 number columns and 2 entries from a table previously exported from teable.
Similarly when importing data into table that already exists.

Expected behavior
I expect a new table with data to be created.

Client (please complete the following information):

• OS: Mac OS 15.3
• Browser: Firefox

Platform (Please tell us which deployment version you are using)
teable.io (CE)
docker-standalone on linux box accessed on home network
this was observed on a fresh install.

[caoxing9]

Could you offer more elaborate detail?

[inbredtom]

This is the data I'm trying to upload.
New table.csv

This is the error icon I get.

[inbredtom]

Interestingly, loading data from a link, eg https://support.staffbase.com/hc/en-us/article_attachments/360009197031/username.csv works. The same file can not be uploaded from my Mac client.

[caoxing9]

Interestingly, loading data from a link, eg https://support.staffbase.com/hc/en-us/article_attachments/360009197031/username.csv works. The same file can not be uploaded from my Mac client.

Could to upload attachment in attachment field, maybe the problem is attachment relative config.

[zjaan7946]

This is the data I'm trying to upload. New table.csv

This is the error icon I get.

Currently, I've also installed it locally using the docker-compose.yml file, and I'm seeing the same issue as shown in the attached image. When I upload a CSV file, there's no response at all.

[caoxing9]

This is the data I'm trying to upload. New table.csv
This is the error icon I get.

Currently, I've also installed it locally using the docker-compose.yml file, and I'm seeing the same issue as shown in the attached image. When I upload a CSV file, there's no response at all.

It means that attachment config problem. could you show that?

[inbredtom]

I resolved the issue by setting PUBLIC_ORIGIN to the IP address:port of the host machine and designated port. This is instead of the default 127.0.0.1:3000 and the hostname:port which I also tried.