Closed SimonXIX closed 4 months ago
Thanks for the issue. test normally means that there was a problem playing your podcast episode. Can you open the dev console of your browser? It should contain more information. Other than that I'll checkout the docker compose myself.
The console reports several 401s when trying to play and it looks like when trying to retrieve images.
Ah. Could it be that you use Basic Auth with username and password? Try to generate an apikey or add the necessary admin api key env variable for that.
Happy to try either. How do I do that?
There we go. Going to 'Profile' and clicking refresh on the API key field in my production (Ubuntu) environment resolved the issue with both playback and images. This could be spelled out in the documentation for installing through Docker.
Had the same issue. Thanks for providing the fix.
Describe the bug
I've been using PodFetch for a while running in Docker. Until a couple of weeks ago I was using the podfetch:postgres Docker image which recently disappeared so I switched to podfetch:latest. Although the application starts OK and connects to the Postgres database, the application no longer plays podcasts or displays thumbnail images for subscriptions (similar to https://github.com/SamTV12345/PodFetch/issues/823).
When I click 'play' the word 'test' appears in the player bar and nothing else happens. There is nothing in the log to indicate anything wrong.
This happens on my production server running Ubuntu 22.04.4 and Docker version 24.0.2 as well as on my testing MacBook running Sonama 14.5 with an Apple M1 chip and Docker 27.1.1.
Here's the full docker-compose.yml for the test version:
Reproduction
reproduced on Ubuntu and on macOS
System Info
Used Package Manager
n/a
Validations