

Fantastic, thanks for this. Any reason you didn’t go to 17?
Fantastic, thanks for this. Any reason you didn’t go to 17?
If the client doesn’t support the codec or resolution of the media then it’ll need transcoding
That person that is kind of lacking in social skills, still weirdly opinionated about really specific things, doesn’t care enough about their appearance for how old they are, and several other holdovers from being a nerdy high school shut in, but is very slowly becoming better. They’re trying to understand how to have more flexible conversations with people, figuring out a clothing style that works for them, and just doing some general growing up. They’re still kind of hard to be around, but you can tell they’ve made progress and that’s all you can really ask of them.
I used to rely heavily on duckdns and it was great for a time, but moved off them a couple of years ago because resolution became inconsistent. I’ve since rolled my own ddns using a script that utilizes Porkbun.com’s DNS record API.
Not to be confused with white-label products in general
Was your old setup using docker volumes? Your old database could be in one
A kind of similar thing happened to me where I added a music album. It had some weird duplication issue where 2 album entries were created: one entry with all the proper metadata that did not correctly link to the files and one with no metadata besides song names that did link to the files. I had to remove all the files of the artist from my library so Jellyfin could completely remove the album entry. Then, when I added the artist back it read the album properly without duplication.
TLDR try removing the entire show and waiting for Jellyfin to wipe it from the library
This will be of zero help to you if your registrar isn’t Porkbun, but I’ve recently stopped using DuckDNS in lieu of this.
Duckdns has been inconsistent for me as well for the past year. Have you considered alternatives?
I believe the nameservers are what respond to domain resolution requests. Nameservers not responding could mean they are down. If there’s no backup and the domain is resolved using one of those servers, then that might explain it not working.
The desktop app should have maximum encoding compatibility so you direct play. It’s not guaranteed with browsers e.g. I believe Firefox doesn’t and will never support HEVC.
My gripe with the desktop app is lack of ability to easily refresh like with a browser. The UI bugs out sometimes and I end up having to close and reopen the app.
I believe the UDP ports are for discovery on your local network so no need to handle them with your reverse proxy. If you’ve got them passed through docker your local devices should pick them up.
They’re also not required since you can always just enter the address manually. I don’t bother passing them into my container.
https://github.com/gethomepage/homepage
Another vote for Homepage, fantastic project
In school I had a physics teacher who thought it was a good idea one day to use whiteboard markers on the glass windows instead of the whiteboard. I didn’t learn anything that lesson.