WeblateOrg / weblate

Web based localization tool with tight version control integration.
https://weblate.org/
GNU General Public License v3.0
4.63k stars 1.02k forks source link

in VCS Config in New compoment, 504 error occur and zip upload is 413 error #3685

Closed readingsnail closed 4 years ago

readingsnail commented 4 years ago

Describe the bug i wanna uploaded to 1.6 Mb (54~150) files in source code repo(https://github.com/readingsnail/stellaris - git@github.com:readingsnail/stellaris.git) and branch, weblate is print 504, and not maked error messages. only took for this. zip file upload is same, it's 413 message. so what i upload my translation files? (SSH is already linked)

To Reproduce Steps to reproduce the behavior:

  1. type source repo to git@github.com:readingsnail/stellaris.git
  2. master branch check
  3. OK
  4. some working and 504 printed.
    weblate_1   | uwsgi stderr | INFO europa-cafe/stellaris: updating repository
    weblate_1   | uwsgi stderr | INFO europa-cafe/stellaris: update took 4.14 seconds
    weblate_1   | uwsgi stderr | INFO europa-cafe/stellaris: repository updated from 006040bb402f45b62527ed8cf69f19d9c41b49fa to 006040bb402f45b62527ed8cf69f19d9c41b49fa
    weblate_1   | uwsgi stderr | DEBUG europa-cafe/stellaris: update: 006040bb402f45b62527ed8cf69f19d9c41b49fa
    weblate_1   | uwsgi stderr | INFO europa-cafe/stellaris: rebase remote into repo 006040bb402f45b62527ed8cf69f19d9c41b49fa..006040bb402f45b62527ed8cf69f19d9c41b49fa
    weblate_1   | uwsgi stderr | [pid: 336|app: 0|req: 6/12] 172.19.0.1 () {40 vars in 523 bytes} [Tue Apr  7 15:26:34 2020] GET / => generated 0 bytes in 5 msecs (HTTP/1.0 301) 5 headers in 222 bytes (1 switches on core 0)
    weblate_1   | nginx stdout | 172.19.0.1 - - [07/Apr/2020:15:26:34 +0900] "GET / HTTP/1.0" 301 0 "-" "masscan/1.0 (https://github.com/robertdavidgraham/masscan)"
    weblate_1   | uwsgi stderr | [pid: 336|app: 0|req: 7/13] 172.19.0.1 () {40 vars in 523 bytes} [Tue Apr  7 15:26:37 2020] GET / => generated 0 bytes in 0 msecs (HTTP/1.0 301) 5 headers in 222 bytes (1 switches on core 0)
    weblate_1   | nginx stdout | 172.19.0.1 - - [07/Apr/2020:15:26:37 +0900] "GET / HTTP/1.0" 301 0 "-" "masscan/1.0 `(https://github.com/robertdavidgraham/masscan)"

Expected behavior Project is created and english files in the original files

Screenshots en.zip - upload and seen 413 error.

Using docker-compose:

list_versions
 * Weblate: 3.11.3
 * Django: 3.0.4
 * siphashc: 1.3
 * Whoosh: 2.7.4
 * translate-toolkit: 2.5.0
 * lxml: 4.3.2
 * Pillow: 7.0.0
 * bleach: 3.1.1
 * six: 1.14.0
 * python-dateutil: 2.8.1
 * social-auth-core: 3.2.0
 * social-auth-app-django: 3.1.0
 * django-crispy-forms: 1.8.1
 * oauthlib: 3.1.0
 * django-compressor: 2.4
 * djangorestframework: 3.11.0
 * django-appconf: 1.0.3
 * user-agents: 2.1
 * filelock: 3.0.12
 * setuptools: 40.8.0
 * jellyfish: 0.7.2
 * openpyxl: 3.0.1
 * celery: 4.4.0
 * kombu: 4.6.8
 * celery-batches: 0.3
 * translation-finder: 1.8
 * html2text: 2020.1.16
 * pycairo: 1.16.2
 * pygobject: 3.30.4
 * diff-match-patch: 20181111
 * requests: 2.23.0
 * django-redis: 4.11.0
 * hiredis: 1.0.1
 * sentry_sdk: 0.14.2
 * Cython: 0.29.15
 * misaka: 2.1.1
 * GitPython: 3.1.0
 * borgbackup: 1.1.11
 * Python: 3.7.3
 * Git: 2.20.1
 * psycopg2: 2.7.7
 * phply: 1.2.5
 * chardet: 3.0.4
 * ruamel.yaml: 0.16.10
 * tesserocr: 2.5.0
 * akismet: 1.1
 * boto3: 1.12.18
 * zeep: 3.4.0
 * aeidon: 1.7.0
 * Mercurial: 4.8.2
 * git-svn: 2.20.1
 * Database backends: django.db.backends.postgresql
 * Cache backends: default:RedisCache, avatar:FileBasedCache
 * Email setup: django.core.mail.backends.smtp.EmailBackend: smtp.naver.com
 * Celery: redis://cache:6379/1, redis://cache:6379/1, regular
 * Platform: Linux 4.18.0-147.5.1.el8_1.x86_64 (x86_64)

Additional context Add any other context about the problem here.

nijel commented 4 years ago

Maybe you have some additional reverse proxy in front of Weblate which caused this? The logs do not show the 504 error...

readingsnail commented 4 years ago

at your advice, additional reverse proxy is down, but it's still 524 (this time, same - VCS, zip) occurs. so idk what's going on here. maybe my ram problem? i'm currently using 4Gib RAM

nijel commented 4 years ago

Not a RAM problem, check the logs which server does cause this error. It seems that 524 is CloudFlare specific, so maybe you are using that?

readingsnail commented 4 years ago

yeah, i using Cloudflare and this setting was DNS Only setting. not Proxyed. maybe changed

readingsnail commented 4 years ago

Tested completed. so my server is hang in minutes... (20 minute+). CF is disconnect hang on minute. thanks for advise. hmmm....

github-actions[bot] commented 4 years ago

The issue you have reported seems to be resolved now.