Awesome! That was going to be the next thing I looked up was how to do the snap list. It shouldn’t be impacting my libation as that is running in a docker instance managed by portainer. Though now that I think back I had initially installed libation using snap, but couldn’t get it to work, so perhaps I have both instances running and am trying to use the snap one on accident when I need to be opening the docker instance.

That makes sense, are they intended to persist indefinitely, only while the subject application is running, or do they go away after a period of time? Thanks for your help!

Oh okay, so do they go away on their own or do they persist potentially indefinitely? I have used snap in the past but had never noticed these until now. I guess I was just paranoid after the plex vulnerability news haha. Thanks.

I don’t know for certain that these unexpected devices in my disk manager are causing the issue, but I noticed them at the same time as the issue with libation being unable to access the directory it normally uses and so I may be conflating 2 unrelated issues

Okay, I have used snap to install things before but it never generated these faux disks that I can’t seem to delete. Would you guess that it is a temporary issue and a restart should resolve? (haven’t restarted yet because I have been using the audiobookshelf and plex and haven’t scheduled a maintenance window yet)

I think that considering the federal bill in the US currently aimed at forcing ISPs and VPN providers to block foreign piracy websites that copyright holders absolutely see piracy as an untapped market. Even if their plan is to ban their competition rather than change their business practices in a way that would attract those customers

As someone who considers themselves a large proponent of swipe texting i have been increasingly running into issues where a word i want to type is almost unreachable with swipe texting because the letters are in too straight of a line on the keyboard and so it only interprets the beginning and ending letters or it takes another word that lies an a similar line

Ive got a reverse proxy config that was available in the Audiobookshelf github documentation, I was mainly struggling to understand how to get all of the parts working together. Thanks for the help

Is 172.17.0.1 like dockers loopback for its own services?

I had considered the VPN route, but i think its enough of a technical hurdle for other people that it would stop my parents and friends from being able/willing to get onto the audiobookshelf server

I had considered not using nginx for precisely those reasons, but like the plex server i want to make it available to my family and friends and so the nginx reverse proxy build seemed to be the most widely applicable and still secure option so I only need to tell them to download audiobookshelf and point it at the correct domain name.

Thank you so much this is very helpful, I’ll definitely be taking a run at it with all of this advice in mind this week. When you mention running the whole thing as a single stack does that mean getting all of it running inside a single docker container such that it only takes the 1 docker run command? Is it a requirement to get them able to talk or just a more elegant way to have the entirety of the server running in a singular container instead of spread across several?

I know, and that’s on my to-do list, but I wanted to get this up and running at least once before upgrading and potentially having to start from square 1.