Thanks again! I managed to set up caddy and it works well so far. Now I am stuck at installing (or using xcaddy. I installed go and the package xcaddy but to me the doc lacks one or two steps. Do you know any tutorial covering that? Thanks!

I mean the global android settings

Android > settings > apps > audiobookshelf > view logs

Also, you can have a look into the server logs, maybe there’s a hint. podman logs -f audiobookshelf (or docker)

In the global app settings there is an entry “log” maybe you can find some useful info in there. Also, check out the

Try the demo https://audiobooks.dev/ with demo/demo https://www.audiobookshelf.org/showcase

I’ve got 128GB on my phone and instead of compressing images and videos to 480p I sync them to my server with immich. Same for music and movies.

I only store the apps and local info on my device. Everything that has to be stored long term sits on a cheap hdd. I can select the audiobook whenever I want to instead of in advance.

It’s working without issues on my gos

I just update. If it breaks, I read the notes. Probably the wrong way but it worked. And I use it for a long time. To me, it was never that unstable. And since a couple of months it’s very stable. Backup first.

I’ve got the same problem since a month or two with another dyndns provider. That’s not specific to the dydns provider. It is the router. Yet I have no idea how to fix it, and I am too lazy currently.

I’m on graphene, btw.

Fedora is called fed. Ubuntu is ubu. Laptop is laptop 🌝

I run grapheneos since a couple of years and I love it.

Sounds like a good solution as well

I run nextcloud on my machine. If there’s a crack, there would be one in their hosted instance as well. There’s nothing really I can do about security of it.

People should pay for foss. Donations are oftentimes welcome

Thx, thats not it

It makes me sad that you had to spend so much time with this topic. But thank you for publishing it ❤️

Yes, it works with nginxproxymanager. There’s probably something going on with selinux - I may disable it the next time to test the assumption.

Thanks. For now, I spend too much time with it. I’ll try some other time again.

Sorry for not having expressed what I did. I wrote a podman compose file, pulled the caddy image, wrote a caddyfile, started it and tried to connect to a service via subdomain.domain.tld .

The caddyfile contains my http and tls ports and the domain and ip for the reverse proxy routing according to the docs.

The result is no log entry in caddy and no result in the browser or curl.

Thx for offering your help.

If I would know, I could debug it, but I don’t know where the problem is. I assume the problem is somewhere with podman or selinux

Ipv64.net is an alternative, just in case you want to switch some day

I had problems with duckdns as well. Never had problems with ipv64

It doesn’t work. I can’t manage to debug it.

Fedora server. Podman. Selinux. Port 8443. Ipv4.