Hardware: Raspberry Pi 4) at home YunoHost version: 11.1.21.4 I have access to my server : Through SSH & through the webadmin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Description of my issue
Hi! Sorry for the trouble… I’m trying to alter the .env file inside of the funkwhale shell, and running into a problem where I need a password, and my admin password apparently doesn’t work.
Entering sudo nano /srv/funkwhale/config/.env should open the file, but it gives me the spiel about talking to the local system admin and asks for [sudo] password for funkwhale: and then doesn’t accept either the admin password for YunoHost or the password for the funkwhale admin (which should be the same anyways).
I’d like to change the funkwhale account registration requirements, as well as a few other internal settings, but have not been able to do so because the sudo password for outside the shell apparently doesn’t work inside the shell.
Is there a way to find/reset the password so I can access these things? Or a workaround? Thanks in advance!
which will then ask you for the password for funkwhale which, for me, nothing worked. Thus, inside the shell, which I can’t access without sudo access, I can’t do anything because it requires sudo access?
Congrats, you are the first to publicly try this new feature.
You should normally not need to do sudo su once more when the shell is opened for Funkwhale. Can you check how the files look like in there with a ls -la?
Especially this /srv/funkwhale/config/.env does not look right. How did you get that path? My guess would be a simple config/.env.
I suppose we can mark this as solved, I spent some time puttering around not in the app shell, and found the .env file at /var/www/funkwhale/config/.env and was able to open it there. I guess if opening the shell is supposed to have allowed me to access things easier/faster/without hunting for a half hour, then it’s still a bug… but at least my problem is solved!
The documentation I was looking at was for the Debian installation, and I was able to get into the .env file through your route when trying it just now, but it also is not writable in that state, which would not work for me.