Problems migrating 0.13.3 to 0.13.5 about lemmy-ansible

[dessalines]

@Nutomic have you ever run into this before?

[pixlguru]

problem solved, seems the old
/etc/nginx/sites-enabled/lemmy.conf
was conflicting with a new
/etc/nginx/sites-enabled/<your-domain>.conf

[Nutomic]

You're right, and everyone that switches from the previous playbook to this one will run into the same problem. Maybe we should add an ansible task which removes that file (or moves it to sites-available).

[spa086]

In new install have a some problem.

fatal: [[email protected]]: FAILED! => {"changed": true, "cmd": "nginx -s reload", "delta": "0:00:00.072777", "end": "2021-11-04 19:07:41.321895", "msg": "non-zero return code", "rc": 1, "start": "2021-11-04 19:07:41.249118", "stderr": "nginx: [emerg] unknown log format "main" in /etc/nginx/sites-enabled/fwz.ru.conf:117", "stderr_lines": ["nginx: [emerg] unknown log format "main" in /etc/nginx/sites-enabled/loc.org.conf:117"], "stdout": "", "stdout_lines": []}

What should i do?

[Nutomic]

@spa086 Your errors look different, it seems like there is something wrong in the two files it mentions (fwz.ru.conf and loc.org.conf). Either delete them, or move them somewhere else (eg sites-available, then they will be ignored).

[pixlguru]

@spa086 @Nutomic
["nginx: [emerg] unknown log format "main"
check
/templates/nginx.conf
lines 115 & 117
lemmy_main vs. main

[spa086]

@Nutomic
fatal: [[email protected]]: FAILED! => {"changed": true, "cmd": "nginx -s reload", "delta": "0:00:00.069230", "end": "2021-11-05 06:22:19.782802", "msg": "non-zero return code", "rc": 1, "start": "2021-11-05 06:22:19.713572", "stderr": "nginx: [emerg] unknown log format "main" in /etc/nginx/sites-enabled/fwz.ru.conf:117", "stderr_lines": ["nginx: [emerg] unknown log format "main" in /etc/nginx/sites-enabled/fwz.ru.conf:117"], "stdout": "", "stdout_lines": []}

Was try to install in new vps, but the same problem.

@pixlguru
thx, will check.

[spa086]

@pixlguru you was right, installation finished ok. But now, when accessing the server, a 502 bad gateway error

[pixlguru]

@spa086
if i remember correctly, there were some other tweaks necessary,
like docker volumes paths changed and old containers had to be removed,
good luck!

[dessalines]

Please let me know if there's anything missing, so I can document them on the migration section of this readme.

[applelhf]

@spa086
if i remember correctly, there were some other tweaks necessary,
like docker volumes paths changed and old containers had to be removed,
good luck!

Hello, my error is also 502 bad gateway error, but I did not find a solution. Can you tell me which need to be changed please? my email is [email protected]