SamTV12345 / PodFetch

A sleek and efficient podcast downloader.
https://samtv12345.github.io/PodFetch
Apache License 2.0
347 stars 25 forks source link

Gui/app broken - add podcasts, logout #356

Closed peterpepo closed 11 months ago

peterpepo commented 1 year ago

Describe the bug

Issues:

  1. Can't copy invite link - clipboard remains empty (Reproduce: login as admin, create invite link for user, try to copy it)
  2. Can't add podcast from iTunes podcast (Reproduce: login as user -> all subscriptions -> Add new -> iTunes -> enter something e.g. 'atletika' -> finds podcast 'Mozgová atletika' (by ZAPO) -> loading circle goes on infinitely)
    • tried as pfadmin: finds podcast, click +, green snakebar "Podcast successfuly added", podcast is not added, container log
      
      thread 'tokio-runtime-worker' panicked at src/service/podcast_episode_service.rs:485:14:

called Result::unwrap() on an Err value: reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("feed.podbean.com")), port: None, path: "/mozgovaatletika/feed.xml", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Try again" })) }

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

thread 'actix-rt|system:0|arbiter:3' panicked at src/service/rust_service.rs:192:22:

called Result::unwrap() on an Err value: JoinError::Panic(Id(322), ...)

3. Can't add podcast from rss (Add new -> RSS feed URL -> `https://feed.podbean.com/mozgovaatletika/feed.xml` -> Add) -> button doesn't work nothing happens
  - works as admin console log

Error during reqwest: error sending request for url (https://feed.podbean.com/mozgovaatletika/feed.xml): error trying to connect: dns error: failed to lookup address information: Try again

4. Can't import opml (tried to import my opml from antennapod), it got stuck at (also as admin)
`Progress: 0/12`
5. Can't log out (missing logout button, has to delete browsing data in order to login as different user)
6. Can't delete podcast

How to reproduce:
1. Build docker image
2. Add user docker `exec -it podfetch /app/podfetch/users add`, e.g. peter/password
3. Log into 192.168.2.40:8081 with new user peter/password

docker-compose.yml

version: '3' services: podfetch: image: samuel19982/podfetch:postgres container_name: podfetch user: ${UID:-1000}:${GID:-1000} ports:

.env

POSTGRES_USER="podfetch"
POSTGRES_PASSWORD="<myDbPwd>"
POSTGRES_DB="podfetch"
PODFETCH_USR="pfadmin"
PODFETCH_USR_PASS="<myAdminPwd>"

Reproduction

Please see description.

System Info

https://hub.docker.com/layers/samuel19982/podfetch/postgres/images/sha256-aaf52b0bf1d093f864830db34dc3a90d04a7816497aeeea55fc4bdfa531abfd5?context=explore

Used Package Manager

n/a

Validations

SamTV12345 commented 1 year ago

Hi @peterpepo,

image

It works on my installation. Based on the error message it seems that your DNS service doesn't work. Can you try nslookup google.com on your raspberry pi?

peterpepo commented 1 year ago

Hello, I can find it - but only as admin user (from USERNAME, PASSWORD environmental variables), and then when I add it ends up with mentioned error. Shows snakebar in bottom left corner 'Podcast Mozgová Atletika added', but it's not listed under Subscriptions. Cannot be added second time either - it errors out with 'Podcast already exists'

When I try to search for it as regular user - created via cli, it loads indefinitely.

nslookup on my rpi works without issues

peterpepo commented 1 year ago

All podbean hosted podcasts return 403: Forbidden since this morning?, maybe it started earlier. What's weird is - when I open rss in my browser it works ok, it fails only for clients such as: PodFetch, Antennapod, Gpodder - all fail with 403.

One which I mentioned in bug report is podbean hosted, maybe that's the case. Try opening for example this, other one failing: https://feed.podbean.com/hospitalrecords/feed.xml Some podcasts on podbean are actually hosted elsewhere, or at least they provide different url (not on podbean domain), and those can be added.

Regardless all the other issues from my report are still relevant and apply.

SamTV12345 commented 1 year ago

All podbean hosted podcasts return 403: Forbidden since this morning?, maybe it started earlier. What's weird is - when I open rss in my browser it works ok, it fails only for clients such as: PodFetch, Antennapod, Gpodder - all fail with 403.

One which I mentioned in bug report is podbean hosted, maybe that's the case. Try opening for example this, other one failing: https://feed.podbean.com/hospitalrecords/feed.xml Some podcasts on podbean are actually hosted elsewhere, or at least they provide different url (not on podbean domain), and those can be added.

Regardless all the other issues from my report are still relevant and apply.

Hmm. Was this maybe only a temporary failure? I can open both links without a probem

SimonXIX commented 1 year ago

I'm experiencing all these same issues using the same Docker image on Ubuntu 22.04.3.

  1. Clicking on the invite link to copy does not do anything.
  2. When I attempt to add a podcast from iTunes (as admin user), it gives the error message 'You are not an admin or an uploader'.
  3. Adding podcast from RSS, the 'Add' button doesn't do anything.
  4. Adding from OPML runs through the OPML file and ends successfully but nothing is added.
  5. No logout button appears.

docker-compose.yml:

podfetch:
    image: samuel19982/podfetch:postgres
    user: ${UID:-1000}:${GID:-1000}
    ports:
      - "8000:8000"
    volumes:
      - ./podcasts:/app/podcasts
    environment:
      - GPODDER_INTEGRATION_ENABLED=true
      - BASIC_AUTH=true
      - USERNAME=$PODFETCH_USERNAME
      - PASSWORD=$PODFETCH_PASSWORD
      - POLLING_INTERVAL=300
      - SERVER_URL=http://[my server name]:8000
      - DATABASE_URL=postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST:$POSTGRES_PORT/podfetch

System information:

Version
    v4.2.2-78a98aaa (HEAD)
Commit
    v4.2.2-78a98aaa (HEAD)
CI build
    No CI platform
Build date
    Mon, 16 Oct 2023 21:16:07 +0000
Branch
    HEAD
OS
    linux
SamTV12345 commented 11 months ago

I'm experiencing all these same issues using the same Docker image on Ubuntu 22.04.3.

  1. Clicking on the invite link to copy does not do anything.
  2. When I attempt to add a podcast from iTunes (as admin user), it gives the error message 'You are not an admin or an uploader'.
  3. Adding podcast from RSS, the 'Add' button doesn't do anything.
  4. Adding from OPML runs through the OPML file and ends successfully but nothing is added.
  5. No logout button appears.

docker-compose.yml:

podfetch:
    image: samuel19982/podfetch:postgres
    user: ${UID:-1000}:${GID:-1000}
    ports:
      - "8000:8000"
    volumes:
      - ./podcasts:/app/podcasts
    environment:
      - GPODDER_INTEGRATION_ENABLED=true
      - BASIC_AUTH=true
      - USERNAME=$PODFETCH_USERNAME
      - PASSWORD=$PODFETCH_PASSWORD
      - POLLING_INTERVAL=300
      - SERVER_URL=http://[my server name]:8000
      - DATABASE_URL=postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST:$POSTGRES_PORT/podfetch

System information:

Version
    v4.2.2-78a98aaa (HEAD)
Commit
    v4.2.2-78a98aaa (HEAD)
CI build
    No CI platform
Build date
    Mon, 16 Oct 2023 21:16:07 +0000
Branch
    HEAD
OS
    linux
  1. Do you have a valid certificate installed on your desktop for that IP? Browsers don't allow access to the clipboard if accessed without an SSL certificate.
  2. Can you give me the podcast's name?
  3. I'd need the url of the rss feed
  4. And the OPML
  5. Yes there is currently no logout button. I'll add that.
SimonXIX commented 11 months ago

I've since pulled the same image and it's all working as expected now. Perhaps it was adding SSL config to my Nginx configuration for this service that resolved it?

SamTV12345 commented 11 months ago

I've since pulled the same image and it's all working as expected now. Perhaps it was adding SSL config to my Nginx configuration for this service that resolved it?

Nice that it is working now. Yes that is unfortunately required for modern browsers.