Error 1001, 1002 and 1003 #2915
Comments
|
(When I click on your video I get error 1002; there are other videos in my feed also encounter error 1002 as well. Yet some videos play fine. I joined few hours ago on Chrome 116.0.5845.180 with duckduckgo search engine |
|
Now the video is playing fine for me, no errors. @ReshmaM8 let us know when there are no errors, until then I'll leave the issue open. |
|
I have inconsistent response when I try to play this video: Link |
|
You can send it to kavin@kavin.rocks, I'll have a look! |
|
are you facing this issue still? i am getting this same error in every video . |
|
yeah, I'm having the same issue. The network traffic shows the video playback in a cycle of cancelled -> 500 --> one 200 request --> pending. |
Not anymore. Now I get misterious Error 1002 for the video I reported in the first place. Here's new error log in stack: |
|
Having the same problem. Getting 1002 error. Sometimes just changing instance works. But once a video fails on a specific instance it keeps failing on that instance, but switching to another video generally works. So maybe there is a cache issue. |
|
Apart from Error 1002, I've also seen 1003 several times. |
Again. Got no errors |
|
The bug appears to be cause by missing cors headers in the http response: #2970 (comment) |
I've noticed CORS errors many times in the past in plenty videos, though they led to video starting playing later than usual or load for a long time, they haven't let to any errors displayed. |
Checked the video out once more. Error 1002. |
Well, if you look at the error object, you can see it is caused by the network error. And the network error is caused by the connection not completing because of the missing cors header. |
|
I got a 1002 on the Syncpundit instance as well, but only once, and a reload fixed it immediately. |
|
kavin.rocks now returns the proper headers and I no longer receive the error.
|
|
Everything seems to be back to normal. I'm not getting any errors and no CORS errors, although the video was loading endlessly. After reloading the page several times and setting the playback indicator to the beginning of the video, the video started playing and played to the end without any problems. I suspect this was something to do with the cache. Overall, the issue seems to have been resolved. I'm going to keep it open for a while in case anyone else is still experiencing these errors. So if you got them in any videos, check them now and report if any of them still seem to be broken. |
|
@DanielProg39 can you check this https://piped.video/watch?v=oRdxUFDoQe0 ? |
Strangely, I got no errors or problems. The whole video played perfectly |
I checked as well, no issues (chrome, win 10) |
|
@DanielProg39 @ReshmaM8 |
|
Still had some 1002's yesterday. Had to switch back and forth between instances to be able to watch the intended videos. |
|
1002 here. happens all the time on almost all instances. |
|
In inside the |
The same issue here. |
Can confirm that this is working. |
Confirmed as well. |
Can confirm too |
On web yes its working, but on libretube it stopped wotking. |
Yeah, it seems to break libretube |
|
@nanedi I'm using Yattee on iOS, and it's working perfectly fine. Before the fix, I had the same issue as I had on the web frontend. Now all the videos are playing again. |
Can also confirm that my self hosted instance is working again.
I managed to make libretube to work with this modification by using HLS instead of DASH |
fix for libretube |
Fixed it, Thanks |
But libretube still get error 1002. |
|
I didn't use any of the fixes suggested in this issue (for now) and Libretube (using my self hosted instance) is working just fine with HLS enabled - just reporting |
Do you also get 1002 on the web? |
Web is fine. |
|
idk it works for me, I dont get 1002 on libretube with the fix, try using HLS like @maximushugus and @ @agpsl pointed out |
Yes I understand that dash. |
|
Pulling latest container images and restarting my piped seems to have finally fixed the issues, thanks! |
on the web, yes, on the libretube still get error 1002. |
|
As far as I can tell this is Piped and LibreTube is https://github.com/libre-tube/LibreTube/issues |
|
Please everyone affected with 1002, just re-pull your container(s) and restart it. If your Then you're not running latest enough. |
|
Hadn't any issues since the last container update. Thank you ;) |
|
Now I have the same issue here |
|
I use the libretube app with a self hosted piped instance, and i've noticed that dash is disabled, so I've dived into the code and this is what I have found in regards to dash/hls From what I can see is that newpipe extractor defaults to hls except for livestream, they set the properties here. public static final class Builder {
private String id;
private String content;
private boolean isUrl;
private DeliveryMethod deliveryMethod = DeliveryMethod.PROGRESSIVE_HTTP;
@Nullable
private MediaFormat mediaFormat;
@Nullable
private String manifestUrl;
// Use of the Boolean class instead of the primitive type needed for setter call check
private Boolean isVideoOnly;
private String resolution;
@Nullable
private ItagItem itagItem;
/**
* Create a new {@link Builder} instance with its default values.
*/
public Builder() {
}There's a method in which you can set the delivery method in the same class /**
* Set the {@link DeliveryMethod} of the {@link VideoStream}.
*
* <p>
* It must not be null.
* </p>
*
* <p>
* The default delivery method is {@link DeliveryMethod#PROGRESSIVE_HTTP}.
* </p>
*
* @param deliveryMethod the {@link DeliveryMethod} of the {@link VideoStream}, which must
* not be null
* @return this {@link Builder} instance
*/
public Builder setDeliveryMethod(@Nonnull final DeliveryMethod deliveryMethod) {
this.deliveryMethod = deliveryMethod;
return this;
}From what I can gather, the piped backend requests the stream info from here you can call on that method to set the stream type if (!livestream) {
info.getVideoOnlyStreams().forEach(stream -> videoStreams.add(new PipedStream(stream.getItag(), rewriteVideoURL(stream.getContent(), extraParams),
String.valueOf(stream.getFormat()), stream.getResolution(), stream.getFormat().getMimeType(), true,
stream.getBitrate(), stream.getInitStart(), stream.getInitEnd(), stream.getIndexStart(),
stream.getIndexEnd(), stream.getCodec(), stream.getWidth(), stream.getHeight(), stream.getFps(), stream.getItagItem().getContentLength())));
info.getVideoStreams()
.forEach(stream -> videoStreams
.add(new PipedStream(stream.getItag(), rewriteVideoURL(stream.getContent(), Map.of()), String.valueOf(stream.getFormat()),
stream.getResolution(), stream.getFormat().getMimeType(), false, stream.getItagItem().getContentLength())));
info.getAudioStreams()
.forEach(stream -> audioStreams.add(new PipedStream(stream.getItag(), rewriteVideoURL(stream.getContent(), extraParams),
String.valueOf(stream.getFormat()), stream.getAverageBitrate() + " kbps",
stream.getFormat().getMimeType(), false, stream.getBitrate(), stream.getInitStart(),
stream.getInitEnd(), stream.getIndexStart(), stream.getIndexEnd(), stream.getItagItem().getContentLength(), stream.getCodec(), stream.getAudioTrackId(),
stream.getAudioTrackName(), Optional.ofNullable(stream.getAudioTrackType()).map(Enum::name).orElse(null),
Optional.ofNullable(stream.getAudioLocale()).map(Locale::toLanguageTag).orElse(null)
)));
} final Map<String, String> extraParams = Map.of(
// "ump", "1",
// "srfvp", "1"
);I think the bug is somewhere in the newpipe deliveryMethod, the stream builder expects a single value in the delivery method and piped is passing 2. However, I'm not an familiar with Java, and I hope I could contribute to the project. |
In my experience, the error (1001 as an example) seems to happen on just some channels, possibly related to the type of video being used there. |
and others
Official Instance
Describe the bug
I opened this video and got a message saying: "Failed with error code 1001, see logs for more info". Other videos play properly without any issues.
To Reproduce
Expected behavior
Video should play like any other.
Logs/Errors
Found this in logs:
Can provide more logs if required
Browser, and OS with Version.
Brave 1.57.62 on Chromium 116.0.5845.180
Additional context
No response
The text was updated successfully, but these errors were encountered: