Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beetsremote catalog does not work #97

Open
Wmartin417 opened this issue Dec 25, 2022 · 2 comments
Open

Beetsremote catalog does not work #97

Wmartin417 opened this issue Dec 25, 2022 · 2 comments
Labels

Comments

@Wmartin417
Copy link

Wmartin417 commented Dec 25, 2022

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.

@lachlan-00
Copy link
Member

possibly a bug here.

image

It is checking whether the link is readable and it's obviously not cause it's a url

@lachlan-00 lachlan-00 added the bug label Jan 16, 2023
@lachlan-00
Copy link
Member

I think this change should resolve it for you
image

        if (filter_var($path, FILTER_VALIDATE_URL)) {
            return true;
        }

I'll make a new develop container today with this change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants