You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have ampache install on docker as well as beets install in a separate docker, using the linuxserver image.
I make a beetsremote catalogue after enabling the catalogue plugin and it connects and gathers the art, tags, etc just fine.
However, when I go to play something from the catalogue, it tells me the following error:
2022-12-25T19:22:55+00:00 [user] (beets_catalog) -> Play: Started remote stream - http://172.60.0.220:8337/item/1/file#.flac
2022-12-25T19:22:55+00:00 [user] (play/index) -> Media http://172.60.0.220:8337/item/1/file#.flac (City of Ocala) does not have a valid filename specified
Opening the beets webUI via that IP:port, I can play and download the file just fine.
I have tried:
Installing beets and running the web on the host and also tried installing beets and running the web in the ampache docker container.
Also tried both the develop and stable branch, same error.
Both give me the same error.
Any help on what to do next? Would greatly appreciate any help on this.
Thanks.
The text was updated successfully, but these errors were encountered:
I have ampache install on docker as well as beets install in a separate docker, using the linuxserver image.
I make a beetsremote catalogue after enabling the catalogue plugin and it connects and gathers the art, tags, etc just fine.
However, when I go to play something from the catalogue, it tells me the following error:
Opening the beets webUI via that IP:port, I can play and download the file just fine.
I have tried:
Installing beets and running the web on the host and also tried installing beets and running the web in the ampache docker container.
Also tried both the develop and stable branch, same error.
Both give me the same error.
Any help on what to do next? Would greatly appreciate any help on this.
Thanks.
The text was updated successfully, but these errors were encountered: