Skip to content
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

ERR: username and password must be both provided #395

Closed
5 tasks
eljefe80 opened this issue May 21, 2021 · 5 comments
Closed
5 tasks

ERR: username and password must be both provided #395

eljefe80 opened this issue May 21, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@eljefe80
Copy link

eljefe80 commented May 21, 2021

Which version are you using?

v0.16.1 from dockerhub

Which operating system are you using?

OS

  • [ x] Linux
  • Windows
  • macOS

Architecture

  • [ x] amd64
  • arm64
  • arm7
  • arm6

Describe the issue

I have a couple of no-name ip cameras that require basic auth, without a password. IE, the paths: would look something like:

front_room_large:
source: rtsp://admin:@10.200.12.53:8001

regrettably, rtsp-simple-server refuses to start saying only:

rtspproxy | ERR: username and password must be both provided

The issue appears to be here

vlc and ffplay (among other rtsp ingesters) appear to accept this URL format.

Describe how to replicate the issue

  1. configure a paths: entry url with a username, but no password
  2. start the server

This failure occurs before network is initiated.
no

@dorinclisu
Copy link
Contributor

Would the cameras refuse authentication with a dummy password? If not, this would be an easy workaround.

@eljefe80
Copy link
Author

Yes, using anything but an empty password results in a 401 unauthorized from the camera and I cannot change the password through the interface.

@aler9 aler9 added the bug Something isn't working label May 29, 2021
@aler9
Copy link
Member

aler9 commented May 29, 2021

Thanks for reporting the issue, sources with empty passwords are now supported in main and will be added to the next release.

@aler9
Copy link
Member

aler9 commented May 30, 2021

added to v0.16.2

@aler9 aler9 closed this as completed May 30, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Jan 1, 2023

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants