Question 1

How do I fix PodFetch on Unraid/Docker creating SQLite database in /app instead of the persistent /app/db volume?

Accepted Answer

Set the `DATABASE_URL` environment variable so PodFetch uses the mounted volume:

```
DATABASE_URL=sqlite:///app/db/podcast.db
```

In Unraid Community Apps, add this variable to the PodFetch container configuration, then recreate/apply the container.

To preserve an existing database before recreating, copy the database files from the running/stopped container to the host volume:

```bash
docker cp PodFetch:/app/podcast.db /mnt/docker_pool/appdata/podfetch/db/podcast.db
docker cp PodFetch:/app/podcast.db-shm /mnt/docker_pool/appdata/podfetch/db/podcast.db-shm
docker cp PodFetch:/app/podcast.db-wal /mnt/docker_pool/appdata/podfetch/db/podcast.db-wal
```

Omit the `shm`/`wal` copy if those files do not exist. After recreating the container, verify that `/app/db` contains `podcast.db`; `docker diff PodFetch` should no longer show `/app/podcast.db` as a newly created file. The Unraid template issue was fixed in `podfetch-unraid-config` commit `b8dcde23c8b653a4108dba2967fd7087ed259619`.

Question 2

How do I fix PodFetch repeatedly re-downloading the same episode with a 'No such file or directory' panic in update_meta_data_mp3?

Accepted Answer

This affects PodFetch v5.2.2 and current `main` when a podcast's cover image is already stored locally, but an episode MP3 has no embedded artwork. The download worker panics while opening a per-episode image that was never written, so `download_time` remains NULL and the episode downloads again on every poll.

Immediate workaround: restore remote image URLs for podcasts whose `image_url` was localized, forcing the per-episode image to be written:

```sql
UPDATE podcasts
SET image_url = original_image_url
WHERE original_image_url LIKE 'http%'
  AND image_url NOT LIKE '%http%';
```

Then trigger the episode download again. Verify that `download_time` is populated and artwork/chapters are inserted.

Code fix: do not treat the optional image as fatal. Replace the unconditional `unwrap()` with a fallible open, for example:

```rust
if tag.pictures().count() == 0
    && let Ok(mut image_file) = File::open(&paths.image_filename)
{
    // embed image_file
}
```

Alternatively, make the image-read condition identical to the condition used when writing the file. Also consider recording `download_time` before metadata processing so a metadata failure cannot cause an endless re-download loop. The maintainer reported the issue as fixed; upgrade to a release containing the fix if available.

Question 3

How to fix PodFetch OIDC invalid_grant and redirect_uri mismatch with Authelia, especially after refreshing an internal page?

Accepted Answer

Upgrade PodFetch to a current `latest`/`main` build newer than the 2026-07-08 image; the fix stops deriving `redirect_uri` from `window.location.href` and uses the server-configured OIDC redirect URI for both the authorization request and token exchange. Set `OIDC_REDIRECT_URI` to the exact callback registered in Authelia, for example `https://podfetch.example.com/ui/`, then update and restart: `docker compose pull && docker compose up -d`. If you cannot upgrade immediately, patch `ui/src/main.tsx` so the callback cleanup regex also removes `scope`, `error`, and `error_description`: `redirectUri.replace(/[?&](code|state|iss|session_state|scope|error|error_description)=[^&]*/g, '')`. The permanent fix is to use the configured fixed redirect URI rather than the current browser URL, which also prevents refresh on routes such as `/ui/home/view` from sending an unregistered `redirect_uri`.

Question 4

Why are version and commit missing or blank on PodFetch's system information page in Docker?

Accepted Answer

This was a bug in the PodFetch Docker image (reported with `samuel19982/podfetch:latest`, presumed 5.2.2) that caused the version and commit data to be unavailable at `/ui/info`. It was fixed in the latest image. Update the container by running `docker pull samuel19982/podfetch:latest`, then recreate it. If using Docker Compose, run `docker compose pull && docker compose up -d`. After the update, open the system information page again to verify the version and commit are displayed.

Question 5

How do I fix podcast episodes showing as "Podfetch" instead of the podcast name in my RSS client?

Accepted Answer

Use the dedicated RSS feed endpoint for each podcast show instead of Podfetch's general combined feed. Open the show in Podfetch, copy its individual feed URL (the feed identified by podcast ID), and subscribe to that URL in your RSS client. The general feed uses a single RSS `Podfetch`, so clients display every episode as "Podfetch". RSS does not support multiple channel titles inside one feed, and changing the author field can produce excessively long titles. As of the discussion, there is no fix for making the aggregate feed show separate podcast names; managing multiple per-show feeds is the supported workaround.

PodFetch

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects