Separate the fat. Make soap with it. Sell it to the rich.

Thank you, I didn’t know that. I know that record labels have been screwing artists for decades… but I didn’t know that Spotify was actually paying good money for the listens, it just doesn’t reach the artist.

I’m not saying that’s wrong, because I don’t have the information, but I have repeatedly read on different news articles that Spotify pays peanuts: way less than that to big artists. I will have to check for updated and reliable sources.

What’s with the clickbait title?

This is not news, it has been happening since Smart TVs started being a thing.

One of the most common TV OSs is AndroidTV / GoogleTV. Google is the biggest ad company in the world.

I recently set up a small home server and started trying to self host stuff. I found it pretty hard to get started. People have been very helpful on this community and other public forums, but I’m afraid it’s often not enough. They give me advice in trying this or that, doing this and avoiding that… but I still don’t understand more than half of the concepts that they use. I consider myself tech literate above the average user: I recently switched to Linux (after years on MacOS, using the command line, and even building a couple of programs from source), I also installed a custom ROM on my phone. I feel comfortable learning and doing these things… but still felt very very lost when trying to self host a few services. At the moment I settled for a local-only network where I run Jellyfin, Navidrome and Syncthing on OpenMediaVault. I’m lost with what I’d need to do to access my server from outside my local network, and terrified of doing something wrong and leaving a hole open so any hacker can access my server. I’d like to do it some day, but I’d rather have a safe local network than screw and get my data stolen or deleted.

So, in my opinion, we would need good tutorials or a MOOC to explain the basics from scratch.

I am not sure about this and cannot check myself because my server died last night :( but… I know that you can restrict certain functions for different users (log in as admin and go to Settings/Users). You could check if it’s possible to disable x265 playback for a user, then create a new user that you use exclusively to log in on that device.

Thank you! That’s exactly what I was looking for. I am familiar with Little Snitch for macOS, so this looks perfect.

For anyone interested: https://github.com/evilsocket/opensnitch

If you’re on windows run glass wire or OSX run little snitch. I used to know a Linux alternative for those

Would you happen to know the name of a similar tool for Linux? I was just yesterday searching myself but I couldn’t find anything

Thank you for this new tip, I think we found the problem: ports 80 and 443 are not open. After I installed nmap (which was surprisingly not present in my Raspbian installation), the output of nmap localhost reads:

Not shown: 997 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
53/tcp  open  domain
631/tcp open  ipp

I guess I did something wrong when following the tutorial (or the tutorial had some mistake, but I’d me more inclined to think the mistake was mine). I will try to clear this installation on docker and start all over again, then I will check nmap localhost again to see if it works fine then.

Thank you very much for your support. I still feel quite lost, but I finally found out why this is not working and I can repeat the steps and pay special attention… or look for a different method (someone here suggested using Nextcloud All-In-One).

Thanks for your answer. I am indeed getting no warning on my browser, just “Unable to connect” on LibreWolf and “This site can’t be reached” on Chromium. I tried the same format (https://192.168.50.30:80) with ports 80, 8080 and 443. The only difference is it was always https:// (since I think my browsers are configured to force https everywhere).

The out put of docker container ls looks like this:

CONTAINER ID   IMAGE              COMMAND                  CREATED        STATUS                                  PORTS     NAMES
95a71b3ce4f6   nextcloud:apache   "/entrypoint.sh apac…"   24 hours ago   Restarting (1) 30 seconds ago                     nextcloud-app-1
590b07333fa1   nextcloud:apache   "/cron.sh"               24 hours ago   Restarting (1) Less than a second ago             nextcloud-cron-1
337fd48a72e8   nextcloud-proxy    "/app/docker-entrypo…"   24 hours ago   Restarting (1) 17 seconds ago                     nextcloud-proxy-1
401d57a50ec8   mariadb:10.6       "docker-entrypoint.s…"   24 hours ago   Restarting (1) 57 seconds ago                     nextcloud-db-1
c6093edc9f71   redis:alpine       "docker-entrypoint.s…"   24 hours ago   Restarting (1) 9 seconds ago                      nextcloud-redis-1

I notice that the “PORTS” column is empty. I am running Raspbian GNU/Linux 11 (bullseye) on my Raspberry Pi, yes.

Thank you for your answer. I will look into getting a domain, but I want to try to fight with this a bit more, mainly as a learning experience. I will also look for easier projects for a beginner, like the dokuwiki you recommended.

Thanks, the tip for Nextcloud All-In-One is actually a very good one. I want to try to make my current setup work, as I said mainly as a learning experience. But I will definitely consider that option once I’m done with this experiment. I guess I will also get a domain.

Thank you for your reply. I think I will look into getting a domain, however I still want to try this, to use it as a learning experience. Try to make it work like this, then keep learning and probably switch to a domain, which seems to be the common thing.

Thanks for your reply. I am not sure about this. Following the tutorial I created a compose.yaml file that had proxy settings:

  proxy:
    ports:
      - 80:80
      - 443:443

so I would assume that already takes care of the ports?

I will have a look at dedyn.io and the tutorial you shared once I manage to reach NextCloud locally via the IP address. Thanks

Thank you, the ip a command helped me get the IP clear, however I am still not sure about the port. I tried with :80, :8080 and :443 (because 80 and 443 are the ones mentioned in the compose.yaml file, and I saw online that 8080 is also a common one?) but none of them worked :(.

I think I will try zerotier, but first I need to be able to access NextCloud from my home network via the IP, which I’m currently unable to do. The tutorial I followed says

The other option is to use a self-signed certificate. This certificate is signed by your own server and won’t be verifiable by any web browser unless you manually install the certificate.

However, it doesn’t explain where that certificate will be stored nor how I can manually install it in the browser I want to use to access NextCloud. Could that help with my issue?