board icon indicating copy to clipboard operation
board copied to clipboard

Failure To Import Taiga (No Errors)

Open PenguinzTech opened this issue 4 years ago • 3 comments

Expected Behavior

Import JSON from Taiga succeeds

Current Behavior

We see "GET /api/v1/users/1/activities.json?type=all&last_activity_id=6&direction=ASC&token=XXX" 200 in nginx logs multiple times, but no successful import. Eventually we get a 524 http code from Cloudflare. The import file is 2MB. We upped the amount of workers to 50 and the memory limit to 1024 for the script. We're running the docker image via the compose example.

Possible Solution

Not sure, unable to determine the issue currently.

Steps to Reproduce (for bugs)

Docker-Compose: `version: "2" services: restyaboard: image: restyaplatform/restyaboard:dev ports: - 1234:80 volumes: - ./media:/var/lib/nginx/html/media - ./apps:/var/lib/nginx/html/client/apps environment: - POSTGRES_HOST=postgres - POSTGRES_PORT=5432 - POSTGRES_ADMIN_USER=postgres - RESTYA_DB_USERNAME=restya #- RESTYA_DB=restyaboard #- SMTP_SERVER=smtp_relay #- SMTP_PORT=587 #- TZ=Etc/UTC depends_on: - postgres restart: always

See https://hub.docker.com/r/boky/postfix for documentation

or try https://github.com/WeAreGenki/docker-smtp

smtp_relay:

image: boky/postfix

environment:

#  - RELAYHOST=<Replace_Public_Instance_IP>:1587
 # - ALLOW_EMPTY_SENDER_DOMAINS=true

postgres: image: postgres:12-alpine volumes: - /var/lib/postgresql/data environment: - POSTGRES_USER=postgres restart: always ` I have the password defined for each too, but stripped for security.

1.Login 2.Go to organization 3.Click on boards -> Import Boards -> Tiaga 4. Wait for it to fail to 524

Context

We're trying to migrate from Tiaga

Your Environment

Using docker / docker-compose Docker version 20.10.2, build 20.10.2-0ubuntu1~20.04.3 docker-compose version 1.25.0, build unknown

I am trying the v1.7 tag and seeing if it works as expected next.

PenguinzTech avatar Aug 28 '21 06:08 PenguinzTech

Failed on v1.7 too

PenguinzTech avatar Aug 28 '21 06:08 PenguinzTech

Determined it was related to nginx client_max_body_size ! Added a larger value to my proxy and the host, and it works like a charm.

PenguinzTech avatar Aug 28 '21 06:08 PenguinzTech

Reopening to fix client_max_body_size in the nginx conf

rrjanbiah avatar Aug 28 '21 13:08 rrjanbiah