Здравствуйте. Не получается загружать видео, даже 2mb. «Этот файл слишком большой», как решить проблему ? [IMG_3543] [IMG_3542]

this is not a build issue. it is a VPSmanager issue with eurobytes.ru - they seem to have enabled a firewall that is blocking sign up payloads as well as file uploads. i went through the nginx config and it’s working but post payloads are being blocked before the server. i have already discussed with the OP and provided messages (in Russian) to send to the support at vds.eurobyte.ru.

Перезапустили сервер, ошибка теперь стала другой [IMG_3548]

why did you control C? and please, paste the test into a code snippet section, screenshots of terminals kind of a bit hard to read :face_with_spiral_eyes:

Я решил сам увеличить размер загружаемых файлов ( Что теперь можно сделать ?

rebuild again and don’t cancel it! :smiley:

Вы имеете ввиду повторить все заново ? Все по инструкции? Run the following command in the /var/discourse directory: ./launcher rebuild app

Не помогло (( [IMG_3551]

Какую команду нужно вписать что бы запустить сайт (

copy the output of that entire block of text in the terminal and paste it here inside backtics like this entire error code here

System load: 0.51318359375 Processes: 156 Usage of /: 64.6% of 58.98GB Users logged in: 1 Memory usage: 30% IPv4 address for docker0: 172.17.0.1 Swap usage: 14% IPv4 address for eth0: 130.49.175.102 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s just raised the bar for easy, resilient and secure K8s cluster deployment. https://ubuntu.com/engage/secure-kubernetes-at-the-edge Expanded Security Maintenance for Applications is not enabled. 355 updates can be applied immediately. 260 of these updates are standard security updates. To see these additional updates run: apt list --upgradable 15 additional security updates can be applied with ESM Apps. Learn more about enabling ESM Apps service at https://ubuntu.com/esm New release '24.04.4 LTS' available. Run 'do-release-upgrade' to upgrade to it. Last login: Mon May 4 02:46:51 2026 from 188.212.135.3 root@xn--80adjnib4bfe:~# cd /var/discours/ -bash: cd: /var/discours/: No such file or directory root@xn--80adjnib4bfe:~# ^C root@xn--80adjnib4bfe:~# cd/var/discourse/ -bash: cd/var/discourse/: No such file or directory root@xn--80adjnib4bfe:~# cd /var/discourse/ root@xn--80adjnib4bfe:/var/discourse# nano containers/app.yml root@xn--80adjnib4bfe:/var/discourse# /var/discourse directort: -bash: /var/discourse: Is a directory root@xn--80adjnib4bfe:/var/discourse# ./launcher rebuild app x86_64 arch detected. WARNING: This output is designed for human readability. For machine-readable output, please use --format. WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 app app ^C root@xn--80adjnib4bfe:/var/discourse# Summary Switched to a new branch ‘latest’ branch ‘latest’ set up to track ‘origin/latest’. I, [2026-05-04T00:10:45.196920 #1] INFO – : > cd /var/www/discourse && sudo -H -E -u discourse git config user.discourse-version latest I, [2026-05-04T00:10:45.219625 #1] INFO – : > cd /var/www/discourse && mkdir -p tmp I, [2026-05-04T00:10:45.224249 #1] INFO – : > cd /var/www/discourse && chown discourse:www-data tmp I, [2026-05-04T00:10:45.228162 #1] INFO – : > cd /var/www/discourse && mkdir -p tmp/pids I, [2026-05-04T00:10:45.232331 #1] INFO – : > cd /var/www/discourse && mkdir -p tmp/sockets I, [2026-05-04T00:10:45.235959 #1] INFO – : > cd /var/www/discourse && touch tmp/.gitkeep I, [2026-05-04T00:10:45.239939 #1] INFO – : > cd /var/www/discourse && mkdir -p /shared/log/rails I, [2026-05-04T00:10:45.243184 #1] INFO – : > cd /var/www/discourse && bash -c “touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log” I, [2026-05-04T00:10:45.249244 #1] INFO – : > cd /var/www/discourse && bash -c “ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log” I, [2026-05-04T00:10:45.254893 #1] INFO – : > cd /var/www/discourse && bash -c “mkdir -p /shared/{uploads,backups}” I, [2026-05-04T00:10:45.259994 #1] INFO – : > cd /var/www/discourse && bash -c “ln -s /shared/{uploads,backups} /var/www/discourse/public” I, [2026-05-04T00:10:45.265173 #1] INFO – : > cd /var/www/discourse && bash -c “mkdir -p /shared/tmp/{backups,restores}” I, [2026-05-04T00:10:45.270733 #1] INFO – : > cd /var/www/discourse && bash -c “ln -s /shared/tmp/{backups,restores} /var/www/discourse/tmp” I, [2026-05-04T00:10:45.275325 #1] INFO – : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp I, [2026-05-04T00:10:45.306388 #1] INFO – : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete I, [2026-05-04T00:10:45.310659 #1] INFO – : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run I, [2026-05-04T00:10:45.312450 #1] INFO – : > cd /var/www/discourse/plugins && git clone GitHub - discourse/docker_manager: Plugin for use with discourse docker image · GitHub Cloning into ‘docker_manager’… I, [2026-05-04T00:10:47.384104 #1] INFO – : > cd /var/www/discourse/plugins && git clone GitHub - kaktaknet/discourse-vkid-oauth: 🔐 VK ID Authentication for Discourse. OAuth 2.1 authentication plugin with VK ID, OK.ru, and Mail.ru support. · GitHub Cloning into ‘discourse-vkid-oauth’… I, [2026-05-04T00:10:48.258431 #1] INFO – : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf I, [2026-05-04T00:10:48.265868 #1] INFO – : > rm /etc/nginx/sites-enabled/default I, [2026-05-04T00:10:48.268731 #1] INFO – : > mkdir -p /var/nginx/cache I, [2026-05-04T00:10:48.272147 #1] INFO – : > grep -q ‘outlets/before-server’ /etc/nginx/conf.d/discourse.conf || ( >&2 echo ‘The “before-server” Nginx outlet is missing. This version of discourse_docker is not compatible with the chosen Discourse version.’ ; exit 1 ) I, [2026-05-04T00:10:48.275719 #1] INFO – : > grep -q ‘outlets/server’ /etc/nginx/conf.d/discourse.conf || ( >&2 echo ‘The “server” Nginx outlet is missing. This version of discourse_docker is not compatible with the chosen Discourse version.’ ; exit 1 ) I, [2026-05-04T00:10:48.278848 #1] INFO – : > grep -q ‘outlets/discourse’ /etc/nginx/conf.d/discourse.conf || ( >&2 echo ‘The “discourse” Nginx outlet is missing. This version of discourse_docker is not compatible with the chosen Discourse version.’ ; exit 1 ) I, [2026-05-04T00:10:48.282330 #1] INFO – : > mkdir -p /etc/nginx/conf.d/outlets/before-server I, [2026-05-04T00:10:48.285122 #1] INFO – : > touch /etc/nginx/conf.d/outlets/before-server/20-redirect-http-to-https.conf I, [2026-05-04T00:10:48.287468 #1] INFO – : > touch /etc/nginx/conf.d/outlets/before-server/30-ratelimited.conf I, [2026-05-04T00:10:48.289859 #1] INFO – : > mkdir -p /etc/nginx/conf.d/outlets/server I, [2026-05-04T00:10:48.292228 #1] INFO – : > touch /etc/nginx/conf.d/outlets/server/10-http.conf I, [2026-05-04T00:10:48.294468 #1] INFO – : > touch /etc/nginx/conf.d/outlets/server/20-https.conf I, [2026-05-04T00:10:48.296500 #1] INFO – : > touch /etc/nginx/conf.d/outlets/server/30-offline-page.conf I, [2026-05-04T00:10:48.298536 #1] INFO – : > mkdir -p /etc/nginx/conf.d/outlets/discourse I, [2026-05-04T00:10:48.300855 #1] INFO – : > touch /etc/nginx/conf.d/outlets/discourse/20-https.conf I, [2026-05-04T00:10:48.302998 #1] INFO – : > touch /etc/nginx/conf.d/outlets/discourse/30-ratelimited.conf I, [2026-05-04T00:10:48.305475 #1] INFO – : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf I, [2026-05-04T00:10:48.307426 #1] INFO – : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections; in /etc/nginx/nginx.conf I, [2026-05-04T00:10:48.308392 #1] INFO – : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size; in /etc/nginx/conf.d/discourse.conf I, [2026-05-04T00:10:48.309109 #1] INFO – : > sed -i ‘s#listen 80;##g’ /etc/nginx/conf.d/discourse.conf I, [2026-05-04T00:10:48.313112 #1] INFO – : > if [ -f “/proc/net/if_inet6” ]; then echo “listen 80;\nlisten [::]:80;” > /etc/nginx/conf.d/outlets/server/10-http.conf else echo “listen 80;” > /etc/nginx/conf.d/outlets/server/10-http.conf fi I, [2026-05-04T00:10:48.316201 #1] INFO – : > echo “done configuring web” done configuring web I, [2026-05-04T00:10:48.319501 #1] INFO – : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} + I, [2026-05-04T00:10:54.375027 #1] INFO – : > cd /var/www/discourse && if [ -f yarn.lock ]; then if [ -d node_modules/.pnpm ]; then echo “This version of Discourse uses yarn, but pnpm node_modules are preset. Cleaning up…” find ./node_modules ./app/assets/javascripts/*/node_modules -mindepth 1 -maxdepth 1 -exec rm -rf {} + fi su discourse -c ‘yarn install --frozen-lockfile && yarn cache clean’ else su discourse -c ‘CI=1 pnpm install --frozen-lockfile && pnpm prune’ fi Scope: all 54 workspace projects Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +537 -412 ++++++++++++++++++++++++++++++++++++++++++++±---------------------------------- Progress: resolved 537, reused 3, downloaded 0, added 0 Progress: resolved 537, reused 145, downloaded 0, added 0 Progress: resolved 537, reused 203, downloaded 10, added 0 Progress: resolved 537, reused 203, downloaded 44, added 1 Progress: resolved 537, reused 203, downloaded 85, added 9 Progress: resolved 537, reused 203, downloaded 94, added 9 Progress: resolved 537, reused 203, downloaded 102, added 9 Progress: resolved 537, reused 203, downloaded 133, added 10 Progress: resolved 537, reused 203, downloaded 146, added 10 Progress: resolved 537, reused 203, downloaded 151, added 10 Progress: resolved 537, reused 203, downloaded 152, added 10 Progress: resolved 537, reused 203, downloaded 153, added 10 Progress: resolved 537, reused 203, downloaded 160, added 11 Progress: resolved 537, reused 203, downloaded 161, added 11 Progress: resolved 537, reused 203, downloaded 173, added 11 Progress: resolved 537, reused 203, downloaded 210, added 13 Progress: resolved 537, reused 203, downloaded 216, added 15 Progress: resolved 537, reused 203, downloaded 244, added 18 Progress: resolved 537, reused 203, downloaded 291, added 26 Progress: resolved 537, reused 203, downloaded 317, added 26 Progress: resolved 537, reused 203, downloaded 319, added 26 Progress: resolved 537, reused 203, downloaded 331, added 26 Progress: resolved 537, reused 203, downloaded 332, added 26 Progress: resolved 537, reused 203, downloaded 334, added 41 Progress: resolved 537, reused 203, downloaded 334, added 70 Progress: resolved 537, reused 203, downloaded 334, added 92 Progress: resolved 537, reused 203, downloaded 334, added 99 Progress: resolved 537, reused 203, downloaded 334, added 140 Progress: resolved 537, reused 203, downloaded 334, added 141 Progress: resolved 537, reused 203, downloaded 334, added 167 Progress: resolved 537, reused 203, downloaded 334, added 195 Progress: resolved 537, reused 203, downloaded 334, added 200 Progress: resolved 537, reused 203, downloaded 334, added 206 Progress: resolved 537, reused 203, downloaded 334, added 208 Progress: resolved 537, reused 203, downloaded 334, added 214 Progress: resolved 537, reused 203, downloaded 334, added 215 Progress: resolved 537, reused 203, downloaded 334, added 231 Progress: resolved 537, reused 203, downloaded 334, added 259 Progress: resolved 537, reused 203, downloaded 334, added 347 Progress: resolved 537, reused 203, downloaded 334, added 365 Progress: resolved 537, reused 203, downloaded 334, added 378 Progress: resolved 537, reused 203, downloaded 334, added 379 Progress: resolved 537, reused 203, downloaded 334, added 380 Progress: resolved 537, reused 203, downloaded 334, added 382, done devDependencies: @discourse/lint-conf@fortawesomegs 2.39.0 @discourse/lint-configs@fortawesome2.45.0 @fortawesome/fontawesome-fre@glint 7.1.0 @fortawesome/fontawes@glintme-free 7.2.0 @glint/e@glintber-tsc 1.1.1 @glint/ember-t@glintc 1.2.3 @glint/tsserver-plug@swcn 2.1.0 @glint/tss@swcrver-plugin 2.2.4 @swc/core 1.15.7 @swc/core 1.15.30 chrome-remote-interface 0.33.3 chrome-remote-interface 0.34.0 esbuild 0.25.12 esbuild 0.28.0 lefthook 2.1.0 lefthook 2.1.6 playwright 1.57.0 playwright 1.59.1 puppeteer-core 24.34.0 puppeteer-core 24.42.0 stylelint 17.1.0 stylelint 17.4.0 terser 5.44.1 terser 5.46.2 ╭ Warning ─────────────────────────────────────────────────────────────────────╮ │ @swc │ │ Ignored build scripts: @swc/core@1.15.30, core-js@2.6.12, │ │ core-js@3.49.0, esbuild@0.27.7, esbuild@0.28.0, lefthook@2.1.6. │ │ Run “pnpm approve-builds” to pick which dependencies should be allowed │ │ to run scripts. │ │ │ ╰──────────────────────────────────────────────────────────────────────────────╯ Done in 1m 0.7s using pnpm v10.28.0 Lockfile is up to date, resolution step is skipped Already up to date ╭ Warning ─────────────────────────────────────────────────────────────────────╮ │ @swc │ │ Ignored build scripts: @swc/core@1.15.30, core-js@2.6.12, │ │ core-js@3.49.0, esbuild@0.27.7, esbuild@0.28.0, lefthook@2.1.6. │ │ Run “pnpm approve-builds” to pick which dependencies should be allowed │ │ to run scripts. │ │ │ ╰──────────────────────────────────────────────────────────────────────────────╯ I, [2026-05-04T00:12:00.534265 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘bundle install --jobs (((nproc) - 1)) --retry 3’ Fetching gem metadata from https://rubygems.org/.^CI, [2026-05-04T00:12:07.601086 #1] INFO – : Terminating async processes I, [2026-05-04T00:12:07.602251 #1] INFO – : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/15/bin/postmaster -D /etc/postgresql/15/main pid: 44 2026-05-04 00:12:07.602 UTC [44] LOG: received fast shutdown request I, [2026-05-04T00:12:07.602710 #1] INFO – : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 111 111:signal-handler (1777853527) Received SIGTERM scheduling shutdown… 2026-05-04 00:12:07.604 UTC [44] LOG: aborting any active transactions 2026-05-04 00:12:07.623 UTC [44] LOG: background worker “logical replication launcher” (PID 58) exited with exit code 1 2026-05-04 00:12:07.626 UTC [53] LOG: shutting down 2026-05-04 00:12:07.628 UTC [53] LOG: checkpoint starting: shutdown immediate 2026-05-04 00:12:07.644 UTC [53] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.008 s, sync=0.002 s, total=0.017 s; sync files=3, longest=0.001 s, average=0.001 s; distance=3 kB, estimate=3 kB 2026-05-04 00:12:07.653 UTC [44] LOG: database system is shut down 111:M 04 May 2026 00:12:07.671 * User requested shutdown… 111:M 04 May 2026 00:12:07.672 * Saving the final RDB snapshot before exiting. 111:M 04 May 2026 00:12:07.972 * DB saved on disk 111:M 04 May 2026 00:12:07.972 # Redis is now ready to exit, bye bye… /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:130:in ‘Process.wait’: Interrupt from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:130:in ‘Pups::ExecCommand#spawn’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:88:in ‘block in Pups::ExecCommand#run’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:86:in ‘Array#each’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:86:in ‘Pups::ExecCommand#run’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/command.rb:10:in ‘Pups::Command.run’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/config.rb:239:in ‘block (2 levels) in Pups::Config#run_commands’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/config.rb:223:in ‘Hash#each’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/config.rb:223:in ‘block in Pups::Config#run_commands’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/config.rb:222:in ‘Array#each’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/config.rb:222:in ‘Pups::Config#run_commands’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/config.rb:203:in ‘Pups::Config#run’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/cli.rb:96:in ‘Pups::Cli.run’ from /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/bin/pups:9:in ‘ ’ from /usr/local/bin/pups:25:in ‘Kernel#load’ from /usr/local/bin/pups:25:in ‘’ Кто может помочь восстановить форум? Я могу выслать доступы на сервер в личные сообщения. Я столько сил потратил на создание форума ( и сломал все

It’s unlikely you will find somebody who will go into your server and fix it all for you for free. Lots of people can do it but you will need to pay them, I believe @pfaffman offers recovery services but I may be incorrect

هذا الملف كبير جداً

دعم المنتج تثبيت

merefield (Robert) 4 مايو 2026، 4:25ص 28

أهه! لست متأكدًا من سبب استمرارك في فعل ذلك؟ لن يساعد ذلك

كن صبورًا ودع الأمر يكتمل.

الموضوع		الردود	مرات العرض
Rebuild taking ~3hours Self-hosting server-resources	35	2266	16 مارس 2025
Error trying to edit a post with an image in (NginX Proxy Manager?) Self-hosting	43	4639	7 مايو 2022
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	723	10 يوليو 2025
Unable to rebuild discourse due to no space left on device Self-hosting	32	3775	19 نوفمبر 2022
Discourse stopped working all of a sudden Self-hosting	8	511	6 يوليو 2024

هذا الملف كبير جداً

الموضوعات ذات الصلة