./appctl run stops at [uWSGI] getting INI configuration from uwsgi.ini

I'm using Google Translate to translate this

I finally managed to install misago without errors (./appctl setup)
But at startup time (./appctl run) it stops at the following line: [uWSGI] getting INI configuration from uwsgi.ini

Please do you know how to solve this?

My internet is really slow, but I don't think this is the cause, since the system monitor doesn't have any use of the network, so I don't think he's trying to download anything

Did you make alteration to the uwsgi.ini file?

No

Remove these lines from your uwsgi.ini and try run setup again to see if it works.

# Enable logging
log-x-forwarded-for
logger              = file:/misago/logs/uwsgi.log

I removed these lines and ran ./appctl rebuildall now it displays this:

sudo ./appctl run
[sudo] senha para noroot:
Starting misagodocker_postgres_1 ...
Starting misagodocker_redis_1 ...
Starting misagodocker_postgres_1
Starting misagodocker_nginx-proxy_1 ...
Starting misagodocker_redis_1
Starting misagodocker_nginx-proxy_1 ... done
Starting misagodocker_nginx-lets-encrypt_1 ...
Starting misagodocker_nginx-lets-encrypt_1 ... done
[uWSGI] getting INI configuration from uwsgi.ini
Starting uWSGI 2.0.18 (64bit) on [Thu Aug 13 03:54:24 2020]
compiled with version: 8.3.0 on 13 August 2020 03:13:39
os: Linux-4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020
nodename: 599f51317274
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 1
current working directory: /misago
detected binary path: /usr/local/bin/uwsgi
uWSGI running as root, you can use --uid/--gid/--chroot options
WARNING: you are running uWSGI as root !!! (use the --uid flag)
chdir() to /misago/
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address 0.0.0.0:3031 fd 3
uWSGI running as root, you can use --uid/--gid/--chroot options
WARNING: you are running uWSGI as root !!! (use the --uid flag)
Python version: 3.7.8 (default, Aug 5 2020, 08:30:24) [GCC 8.3.0]
Python threads support is disabled. You can enable it with --enable-threads
Python main interpreter initialized at 0x564e4cf907d0
uWSGI running as root, you can use --uid/--gid/--chroot options
WARNING: you are running uWSGI as root !!! (use the --uid flag)
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 364600 bytes (356 KB) for 4 cores
Operational MODE: preforking
WSGI app 0 (mountpoint='') ready in 11 seconds on interpreter 0x564e4cf907d0 pid: 1 (default app)
uWSGI running as root, you can use --uid/--gid/--chroot options
WARNING: you are running uWSGI as root !!! (use the --uid flag)
uWSGI is running in multiple interpreter mode
spawned uWSGI master process (pid: 1)
spawned uWSGI worker 1 (pid: 8, cores: 1)
spawned uWSGI worker 2 (pid: 9, cores: 1)
spawned uWSGI worker 3 (pid: 10, cores: 1)
spawned uWSGI worker 4 (pid: 11, cores: 1)

Its working...

That line you removed were the logs.....

If you access your web page, it should load.

If it loads, add the lines back because logging is very crucial for debug purpose.

Okay, but I'm still getting a 500 Internal Server Error
nginx / 1.17.6 when I access https: // my_ip / admincp / and now I have no idea why

I'm using a virtual machine so I tried to use the backup of linux right after installing it and it continues the same thing

My installation differs from the tutorial (misago.gitbook.io/docs/setup/misago) in the following points:

I don't use ssh
I did not install fail2ban
I do not have a domain name, at the time of installation I put my ip, it is real and I have already configured ports 80 and 443

When I turn on the virtual machine, the docker starts automatically, and I use the sudo ./appctl run, should I run any other commands?

uwsgi.log presents the same as I already posted a little above

access.log

my ip here 10.0.2.2 - - [14 / Aug / 2020: 20: 42: 51 +0000] "GET / HTTP / 2.0" 500 177 "-" "Mozilla / 5.0 (X11; Ubuntu; Linux x86_64; rv: 79.0 ) Gecko / 20100101 Firefox / 79.0 "
my ip here 10.0.2.2 - - [14 / Aug / 2020: 20: 42: 51 +0000] "GET /favicon.ico HTTP / 2.0" 500 177 "-" "Mozilla / 5.0 (X11; Ubuntu; Linux x86_64; rv: 79.0) Gecko / 20100101 Firefox / 79.0 "
my ip here 10.0.2.2 - - [14 / Aug / 2020: 21: 01: 40 +0000] "GET / HTTP / 2.0" 500 177 "-" "Mozilla / 5.0 (X11; Ubuntu; Linux x86_64; rv: 79.0 ) Gecko / 20100101 Firefox / 79.0 "
my ip here 10.0.2.2 - - [14 / Aug / 2020: 21: 01: 42 +0000] "GET /favicon.ico HTTP / 2.0" 500 177 "-" "Mozilla / 5.0 (X11; Ubuntu; Linux x86_64; rv: 79.0) Gecko / 20100101 Firefox / 79.0 "
my ip here 10.0.2.2 - - [14 / Aug / 2020: 21: 01: 45 +0000] "GET / HTTP / 2.0" 500 177 "-" "Mozilla / 5.0 (X11; Ubuntu; Linux x86_64; rv: 79.0 ) Gecko / 20100101 Firefox / 79.0 "
my ip here 10.0.2.2 - - [14 / Aug / 2020: 21: 01: 48 +0000] "GET / HTTP / 2.0" 500 177 "-" "Mozilla / 5.0 (X11; Ubuntu; Linux x86_64; rv: 79.0 ) Gecko / 20100101 Firefox / 79.0 "

error.log

2020/08/14 19:39:38 [notice] 37 # 37: signal process started
2020/08/14 19:39:47 [notice] 42 # 42: signal process started
2020/08/14 19:40:31 [notice] 63 # 63: signal process started
2020/08/14 19:41:06 [notice] 84 # 84: signal process started
2020/08/14 19:41:45 [notice] 87 # 87: signal process started
2020/08/14 19:42:06 [notice] 90 # 90: signal process started
2020/08/14 19:51:07 [notice] 93 # 93: signal process started
2020/08/14 19:54:31 [notice] 53 # 53: signal process started
2020/08/14 20:00:26 [notice] 56 # 56: signal process started
2020/08/14 20:00:49 [notice] 78 # 78: signal process started

I installed it on a droplet and everything is working even without a domain name, except https

Even after setting up a domain using freenom, https continues to answer nginx error 500, http loads the page, but does not accept login because of CSRF

I registered the domain in the frenom and pointed to the digitalocean nameserver, in the digital ocean I pointed to my droplet, I think it is not a problem with the domain name since it is pointing correctly to the droplet's ip

Should I have waited a while between setting up the domain and installing the misago?

I'll wait a while to see if the https hits itself

edit: I tried to reinstall by placing https: // when he asks me for the domain, find out that it doesn't matter because he won't let me put it on, so I proceeded with the installation normally and in the end the https worked miraculously, okay