Assistance With First(ish) Funkwhale Setup

ohkio

Hey funkwhale folks!
I had things somewhat created and then forgot the admin user I must have made and got fed up and did a mass uninstall of funkwhale and nginx thinking I was going to try another service. I'm back trying to use funkwhale, trying to set things up and running into problems I hadn't run into before.

I am trying to run funkwhale on an ubuntu server I built. Most things seem to be running smoothly but nginx does not want to start. There doesn't seem to be anything already running on port 80 but I'm wondering if somehow the remnants of my first install of nginx is blocking the new install of nginx. I'm getting frustrated and keep running around in circles with various documentation. I recognize nginx is probably a common sticking point so is there anybody willing and able to walk me through how to check things and get things up and running again? I'd really like to have this set up. This is the first project for this server so I'm able to even do a hard reset of the entire server if needed. Thanks for the help.

Tired of DDG search optimization,
Kio

ohkio

[emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
[emerg] bind() to [::]:80 failed (98: Unknown error)
[emerg] still could not bind()
nginx.service: Control process exited, code=exited, status=1/FAILURE
nginx.service: Failed with result 'exit-code'.
Failed to start a high performance web server and a reverse proxy server

This is the main error I'm running into. I trust there are more things I can dig into and could just use some help determining where to look, what to look for, what to restart, what to try. It would make sense to me if it's related to the port. Any guidance appreciated.

ohkio

Running lsof -i tcp:80 returns nothing. ufw indicates the port is open and reserved for nginx full. I'm at a loss here

ohkio

More details. When I run sudo nginx -t I get a success:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

When I run nginx -t it is a failure

[emerg] ###: cannot load certificate "file/path/fullchain.pem": BIO_new_file() failed (SSL: error:0200100D:system library:fopen:Permission denied:fopen('file/path/fullchain.pem','r') error:2006D002:BIO routines:BIO_new_file:system lip)
nginx: configuration file /etc/nginx/nginx.conf test failed

I've tried tinkering with the permissions of these directories and files a little bit (changing just the relevant areas to be a part of the sudo group so that it's easier to read them) but I'm nervous to make too many big changes to permissions.

Really not sure what's up or what to try next.

gcrk

Hi and welcome (back) to Funkwhale 🐋 !

Sorry you have so much trouble with our reverse proxy configuration, its indeed one of the pitfalls in our current setup, which is historically grown.

Lets go through your issues!

You can check what services are probably blocking a port by running netstat -tulpn | grep 80. Beyond this it would help a lot to actually see your nginx configurations.

Honestly, I think running nginx -t as a user not owning the actual process doesn't make a lot of sense. This user should then be able to read the certificates, without making them world readable.

ohkio

Okay. Definitely starting to identify things. I though I had checked this but apparently needed to sudo in order to see the process name. it's httpd. I keep trying to kill the process but it keeps coming back. Trying to look into how to kill/uninstall it. And there's only one user on this server. I'm confused how I wouldn't own the process. Are you implying sudo nginx -t should be a fine way to check? Anyway definitely helping and getting closer now.

ohkio

ALRIGHT! Pushed through the nginx trouble. Instance is running. Domain is set up properly. But I do not know how to add or login as the superuser I made and cannot find any reference to it in documentation.

ohkio

I had tried to use the manage.py but kept running into install issues that did not seem like the thing I should be doing.

gcrk

This is what you need to do: https://docs.funkwhale.audio/installation/debian.html#create-an-admin-account

ohkio

AH! Also a very helpful direction. I had done the "quick install." I know ubuntu is based on debian, but I was not sure which set of instructions won out. Alright. Going to try an uninstall and reinstall using these instructions. Thank you very much for the attention and time. Will report back.

gcrk

ohkio wait, if you did the quick install, this should have setup an administrator account for you.

ohkio

gcrk It was a good exercise for me. I understand both linux and this system a lot better. Some notes I noticed:

First, su funkwhale which is the "standard" way to switch users does not work. In the custom install there is a method mentioned near the top that works fairly consistently. sudo -u funkwhale -H bash which you then exit by typing exit it was also important to at least go through the initial steps to learn about the virtual environment where I needed to use source /srv/funkwhale/virtualenv/bin/activate in order to start the virtual environment and then could type deactivate to stop (this was helpful to me for a few reasons, thank you). So, from the admin user of ubuntu, in order to make updates to funkwhale these were the important steps in all

cd /srv/funkwhale
sudo -u funkwhale -H bash
source /srv/funkwhale/virtualenv/bin/activate
# whatever admin things I needed to do
deactivate
exit
cd ~

It's all been created and I was able to listen to music from my server for the first time. It was very exciting. I really appreciate the direction!

gcrk

ohkio First, su funkwhale which is the "standard" way to switch users does not work.

This is because we create the user without shell, so if you don't pass one to the command, it cannot work. This is somehow expected, but really inconvenient.

This is also true for the manual management of the virtual environment. I don't think its useful to have this in a beginners guide and Funkwhale 1.3 will start using poetry as package manager, which has included venv management. So some improvement is on the horizon already 😉

Anyway, congratulations and enjoy! 🙂