Issue after upgrading to 1.3.1

JustBru00

[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2023-08-15/1692131174-487465-image.png]

Now when attempting to run the upgrade, I get an error about ansible-galaxy not found.

geraldbigot

gcrk
Same error for me 🇦

sudo sh -c "$(curl -sSL https://get.funkwhale.audio/upgrade.sh)"

[Beginning upgrade]
[1/4] Retrieving currently installed version from /srv/funkwhale/ansible/playbook.yml
[1/4] No target version specified, retrieving latest version from https://docs.funkwhale.audio/latest.txt

Upgrade summary:

- Current version: 1.3.1
- Target version: 1.3.1
- Upgrading may cause temporary downtime on your pod

Do you want to proceed with the upgrade? [YES/no]: yes
[2/4] Replacing current version number in /srv/funkwhale/ansible/playbook.yml…
[3/4] Upgrading ansible dependencies...
[3/4] Upgrading Funkwhale using ansible playbook in /srv/funkwhale/ansible...
sh: 99: /root/.local/ansible/bin/ansible-galaxy: not found

gcrk

Thank you for the reports, looking into it now!

gcrk

@JustBru00 @geraldbigot I just put a patch in place that should fix your issue. It is merged, so you can try again. This will hopefully allow you to finally upgrade to Funkwhale 1.3.x. Let me know how its going!

JustBru00

gcrk

This patch seems to have fixed my installation.
After running the upgrade script, everything is working as far as I can tell.
Thanks for your work on fixing this issue.

geraldbigot

gcrk
This patch does not seem to fix my installation
[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2023-08-21/1692597974-762046-capture-decran-du-2023-08-17-09-47-43.png]
[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2023-08-21/1692597974-659465-capture-decran-du-2023-08-17-09-54-20.png]

gcrk

@geraldbigot Please don't post screenshots of the terminal but copy and paste the text. Its almost unreadable this way.

Additionally, the two issues don't seem to be related since your instance has working https. However, do you still use Apache? As I already explained several times in different locations, we lack the ability to update the apache configs. I might dig into this in the following weeks, but no promises.

To debug the issue, please run apt list | grep certbot and post the output, I am curious if you have certbot installed by other means already

geraldbigot

Ok. I won't post screenshots anymore.
Yes, I'm using Apache2. Sorry.
Here is the output : WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

certbot/jammy,jammy,now 1.21.0-1build1 all [installed]
python-certbot-dns-cloudflare-doc/jammy,jammy 1.18.0-1 all
python-certbot-dns-digitalocean-doc/jammy,jammy 1.18.0-1 all
python-certbot-dns-dnsimple-doc/jammy,jammy 1.18.0-1 all
python-certbot-dns-gehirn-doc/jammy,jammy 1.18.0-1 all
python-certbot-dns-google-doc/jammy,jammy 1.18.0-1 all
python-certbot-dns-linode-doc/jammy,jammy 1.7.0-1 all
python-certbot-dns-ovh-doc/jammy,jammy 1.3.0-1 all
python-certbot-dns-rfc2136-doc/jammy,jammy 1.21.0-1 all
python-certbot-dns-route53-doc/jammy,jammy 1.3.0-1 all
python-certbot-dns-sakuracloud-doc/jammy,jammy 1.3.0-1 all
python-certbot-doc/jammy,jammy 1.21.0-1build1 all
python3-certbot-apache/jammy,jammy,now 1.21.0-1 all [installed]
python3-certbot-dns-cloudflare/jammy,jammy 1.18.0-1 all
python3-certbot-dns-digitalocean/jammy,jammy 1.18.0-1 all
python3-certbot-dns-dnsimple/jammy,jammy 1.18.0-1 all
python3-certbot-dns-gandi/jammy,jammy 1.3.2-1 all
python3-certbot-dns-gehirn/jammy,jammy 1.18.0-1 all
python3-certbot-dns-google/jammy,jammy 1.18.0-1 all
python3-certbot-dns-linode/jammy,jammy 1.7.0-1 all
python3-certbot-dns-ovh/jammy,jammy 1.3.0-1 all
python3-certbot-dns-rfc2136/jammy,jammy 1.21.0-1 all
python3-certbot-dns-route53/jammy,jammy 1.3.0-1 all
python3-certbot-dns-sakuracloud/jammy,jammy 1.3.0-1 all
python3-certbot-dns-standalone/jammy,jammy 1.0.3-2 all
python3-certbot-nginx/jammy,jammy,now 1.21.0-1 all [installed]
python3-certbot/jammy,jammy,now 1.21.0-1build1 all [installed,automatic]

gcrk

geraldbigot Okay, I fixed the role to respect your local installation of certbot.

gcrk

This means you have certbot installed from apt, which is something we don't expect. I will try to fix that today.

However, for the current state about Apache please check this thread

geraldbigot

gcrk
Thank you gcrk !
Now, Funkwhale 1.3.1 runs well with Nginx but I need to stop Apache instance.
I can't manage to have these 2 servers running together...

gcrk

geraldbigot I can't manage to have these 2 servers running together...

Thats because they both try to use the same ports, at least 80 and 443, but only one application can listen on a port.

geraldbigot

gcrk
Yes, I understand that but I need to care about 15 websites and crm with Apache2 and only Funkwhale with Nginx
I can't buy a new server only for Funkwhale Nginx session.
I'm looking for a trick to have both, Apache2 and Nginx, running together but not easy...

ToneLune

Same Loading Funkwhale error here after 1.3.3 upgrade (I'm using Nginx).

I've juste two lines in console :

Loading module from “https://****.****.*****/assets/index-f7369c39.js” was blocked because of a disallowed MIME type (“text/html”). Loading failed for the module with source https://****.****.****/assets/index-f7369c39.js

Edit : solved !

I've found a mistake from doc : https://docs.funkwhale.audio/administrator/upgrade/debian.html

${NGINX_MAX_BODY_SIZE} variable isn't replaced with the following script:

set -a && source /srv/funkwhale/config/.env && set +a
envsubst "`env | awk -F = '{printf \" $%s\", $$1}'`" \
   < /etc/nginx/sites-available/funkwhale.template \
   > /etc/nginx/sites-available/funkwhale.conf

I've manually fix it in funkwhale,conf

client_max_body_size ${NGINX_MAX_BODY_SIZE}
to
client_max_body_size 500M;

And restarting Nginx/Funkwhale. 🙂

« Previous Page