pitsi

New week, new error :p ``` $ curl https://api.consumet.org/movies/fmovies/deadpool {"statusCode":500,"error":"Internal Server Error","message":"write EPROTO C087EAD08C7F0000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 80\n" ``` On top of that, tmdb is now broken...

And the watch function for tmdb is now broken too :( ``` $ curl https://api.consumet.org/meta/tmdb/watch/19694?id=movie/watch-deadpool-19694 {"message":{} ```

@forsyth47 Sorry for the 4-month late question. Do you still update your self-hosted instance? I still can not host my own, so I can not check if anything has changed...

Today, 1 year after opening the issue, I had the chance of making a new vm to test if anything has changed. And sadly nothing has changed, fmovies remains broken,...

With fmovies dead and buried for almost a month now, there is no reason to keep this open. After all, it never worked.

I do not wait for the main repo to package it. I use deb-multimedia.org since ever and I have been getting kodi from there since kodi was called xbmc and...

I just noticed that, for some unknown reason, kodi creates a file named core in my home once it crashes. Sometimes it's small, a few megabytes, and sometimes it's big...

Thank you for the instructions. I did what the wiki suggests on step 1.1 and it's gone now. I think systemd's upgrade to 256rc3 caused it and I have a...

Now that debian unstable is moving to python 3.12 and dmo's kodi is built with it, I made a debian unstable installation and installed it there. Stock installation without any...

Python 3.12 reached testing today and I gave kodi one more try. It does not exit with the gil error at the start, but exits with segmentation fault like above....