Fighting with Funkwhale

  • READ ME AND USE THIS TEMPLATE IF YOU WANT TO GET HELP ! You may ask your question in english or french, whichever is easiest for you… But please use one of the templates provided below :wink:
  • LISEZ-MOI ET UTILISEZ CE MODÈLE DE TOPIC SI VOUS SOUHAITEZ OBTENIR DE L’AIDE ! Vous pouvez poser votre question en anglais ou français, selon ce qui est le plus simple pour vous… Mais de préférence en utilisant l’un des deux modèles fournis ci-dessous :wink:

:uk:/:us: Message template (english)

The “support” category is meant to ask for help or troubleshooting related to installing or using YunoHost or its applications. It is not to ask assistance on general system administration, network administration or special use cases that goes beyond the scope of the project. If you wish to discuss more advanced use case, please post in the “Advanced Use Case” category.

Before posting, please :

My YunoHost server

Hardware: VPS
YunoHost version: 4.3.6
I have access to my server : SSH/web
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If yes, please explain:

Description of my issue

I’m debugging this in a few places, but have filed this GitHub issue where I’m working on a solution.

  1. Funkwhale shows tht I’m logged in, but I get various permission errors accessing API endpoints in the logs. It’s as if the SSO/front-end and the back-end disagree as to whether I’m authenticated.
  2. I’m seeing this in the logs a lot:
Feb 16 16:00:40 thewordnerd.info gunicorn[11777]: 2022-02-16 16:00:40,564 django_auth_ldap WARNING uid=nolan,ou=users,dc=yunohost,dc=org does not have a value for the attribute "uid"}

It’s odd to me that it’s showing the uid right there in the DN, but claims that the attribute doesn’t exist. I’m not super familiar with LDAP so maybe there’s something I’m missing?

I poked the server a bit with phpldapadmin and ldapsearch. Unless I’m mistaken, the uid attribute is in fact there. It also seems as if I can query it anonymously.

The relevant Funkwhale YNH configuration seems to be here. I’m running from the testing branch, but experienced similar errors on stable. [Here are Funkwhale]s LDAP docs](LDAP configuration — funkwhale 1.2.2 documentation).

Any other thoughts on how to debug this? I tried commenting out the search filter but that made no difference, unless the config mechanism has changed.

Thanks.

OK, so I figured out part of this. The environment syntax for the user mapping changed, so I submitted this PR. Now the LDAP errors seem to be gone.

But I’m still unable to subscribe to podcasts. I get “This object cannot be retrieved” when entering multiple, working URLs in the podcast subscription dialog.

Any idea where I can track down logs for why this might fail? Not seeing anything in funkwhale-server/funkwhale-worker logs. I don’t suppose there’s a manifest setting/permission that needs to be tweaked for outbound network access?

Thanks.

OK, more progress. I wanted to figure out where this error was coming from, so I grabbed the source and grepped. Turns out the front-end requests the podcast URL directly from the browser, then presumably subscribes to some value from that.

My assumption is that the podcast URLs are probably fine, but there are a bunch of headers in the Nginx config. Are any of them responsible for preventing my browser from directly requesting the podcast feed? Again, given that this happens with multiple large feeds, I’d be stunned if the headers on the remote servers hosting the feeds are misconfigured.

Thanks.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.