cross-posted from: https://discuss.tchncs.de/post/21001865
I just installed Piped using
podman-composebut when open up the frontend in my browser, the trending page is just showing the loading icon. The logs aren't really helping, the only error is inpiped-backend:java.net.SocketTimeoutException: timeout at okhttp3.internal.http2.Http2Stream$StreamTimeout.newTimeoutException(Http2Stream.kt:675) at okhttp3.internal.http2.Http2Stream$StreamTimeout.exitAndThrowIfTimedOut(Http2Stream.kt:684) at okhttp3.internal.http2.Http2Stream.takeHeaders(Http2Stream.kt:143) at okhttp3.internal.http2.Http2ExchangeCodec.readResponseHeaders(Http2ExchangeCodec.kt:97) at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:110) at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109) at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201) at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154) at me.kavin.piped.utils.RequestUtils.getJsonNode(RequestUtils.java:34) at me.kavin.piped.utils.matrix.SyncRunner.run(SyncRunner.java:97) at java.base/java.lang.VirtualThread.run(VirtualThread.java:329)Would appreciate it if anyone could help me. I also wasn't sure what info to include, so please ask if there's any more info you need.

I'm a little late here but I can explain it.
What Sonarr, Radarr and the others do automatically is scan an RSS feed of new releases. Basically, they look through the things that were uploaded to each tracker, since the last scan, to see if anything should be downloaded. The issue with this is that this only finds the things that were uploaded since the media item (show or movie) was added, not things that were uploaded before then. What this software does (and Huntarr used to do) is run a full search on the indexers, so the *arr apps can find any file that has ever been uploaded to the trackers. It's the same search you can trigger manually.
Technically, adding a media item, manually triggering a full search once and then relying on the automatic RSS scan should give you the same result (unless any trackers were down while you ran the manual search, which is one of the issues with this approach) but, for example, I use Seerr, so friends and family can add new stuff to my *arr apps but Seerr doesn't trigger a full search when something gets added, so I would have to manually trigger the full search once every time someone adds something. The point of having something like Fetcharr is that the full search gets triggered automatically. In addition, it does so periodically instead of just once, so that fixes issues like trackers being down when the search was triggered or a download not being found in the RSS feed despite it existing (not sure if the second one ever happens but it technically could and this would solve that issue).
Edit: I also just saw that the GitHub page for this has an explanation as well: