Upgrade to pleroma 2.4.0~ynh1 from 2.3.0~ynh3 succeeds but results in 502 bad gateway

[lightnin]

Upgrade to 2.4.0~ynh1 from previous release results in 502 afterwards on YunoHost 4.2.8.1 (stable) on Rpi4.

Steps to reproduce

Upgrade via webadmin.

Expected behavior

Successful upgrade with working pleroma install afterwards.

Logs: https://paste.yunohost.org/raw/xijanaleza

Many thanks for making pleroma available on Yunohost!

[yalh76]

Seems weird, tests were ok. You should look if the pleroma service is running. can be done on the YunoHost webadmin of from the command line service pleroma restart

[lightnin]

Thanks for looking at this so quickly! Tried rebooting, still get 502. Tried restart, still 502. Here's service status:

URL instance is here: https://masto.amosamos.net/

[lightnin]

There's quite a lot of pleroma running, in spite of the 502.

[yalh76]

ok, can you check the value of the port indicated in /etc/pleroma/config.exs L9. and if it's the same as in /etc/nginx/conf.d/your_pleroma_domain/pleroma.conf L16

[lightnin]

config.exs: config :pleroma, Pleroma.Web.Endpoint, url: [host: "masto.amosamos.net", scheme: "https", port: 443], http: [ip: {127, 0, 0, 1}, port: 8095],

Line 16 of pleroma.conf: proxy_pass http://localhost:8095;

So yep, the same.

Gonna have to restore the backup now unfortunately, as I need my instance for documentation this week. But can try upgrade again next week.

[lightnin]

@yalh76 I see there is a 2.4.1 release out now - do you think it's likely to resolve this issue?

[lightnin]

Installed the 2.4.1 release and no 502s, everything seems A ok. :) Thanks!