-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTSP Source 401 after v1.6.0 #3116
Comments
Hello, this can be certainly fixed but you need to provide a server log with option |
|
it seems that a |
@emeryao thanks for providing the log, please test this nightly release and let me know if it fixes the issues (click on "Artifacts", "binaries"): |
(bluenviron/mediamtx#3116) This fixes authentication issues with some TP-LINK cameras.
I have exactly the same issue with cameras from the same brand(TP-Link) |
@bobocancan if you want to solve the issue, download and test the nightly release attached in the previous post and let me know if it fixes the problem. If it doesn't attach server logs with |
Thank you for your reply Alessandro.
I am using the docker version, not really sure how I can replace the binary.
…On Mon, 6 May 2024 at 19:14, Alessandro Ros ***@***.***> wrote:
@bobocancan <https://github.com/bobocancan> if you want to solve the
issue, download and test the nightly release attached in the previous post
and let me know if it fixes the problem. If it doesn't attach server logs
with logLevel: debug option.
—
Reply to this email directly, view it on GitHub
<#3116 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIGL5XHGFYH375CR34R6CPTZA5CXPAVCNFSM6AAAAABEKH2Q2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGUZDMMRRGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sorry for the late repsponse since my computer went down during the weekend and I just fixed it 😅 Below is the debug log of the binary from https://github.com/bluenviron/mediamtx/actions/runs/8945300574
|
@emeryao thanks for the feedback, it seems like my patch was unable to solve the issue. Can you post the same log but using v1.4.2 (last working version)? in this way we can check why v1.4.2 was working and my patch was not (BTW i was not able to spot differences between v1.4.2 and my patch). Also check whether credentials are correct. |
@aler9 your patch just works after the camera rebooted with the nightly build 🎉 and it's still a 401 with the version 1.8.1 even if the camera was just rebooted |
perfect, i'm merging the patch. |
(bluenviron/mediamtx#3116) This fixes authentication issues with some TP-LINK cameras.
(bluenviron/mediamtx#3116) This fixes authentication issues with some TP-LINK cameras.
This issue is mentioned in release v1.8.2 🚀 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Which version are you using?
v1.6.0
Which operating system are you using?
Describe the issue
Hi Team,
Here is my story.
I have 3 different model of TP-Link cameras and added to the mediamtx.yml
at the version of
1.4.x
of mediamtx all 3 cameras works perfectlyafter upgrade to version
1.5.x
one the camera goes down with the log ofERR [path ipc001] [RTSP source] bad status code: 401 (Unauthorized)
and when I update mediamtx to
1.6.0
two of the cameras going down with the401
message only one camera works for now 😂I'm pretty sure all the cameras are fine and can be lived with PotPlayer and VLC with the same rtsp url in
mediamtx.yml
Describe how to replicate the issue
Did you attach the server logs?
yes
Did you attach a network dump?
no
The text was updated successfully, but these errors were encountered: