HTTP interface admin username

[tkonto]

Hello all,

Completely new to the forum and very novice with vlc.

Used to work with pre-2.0 releases on my home server, to stream to a satellite box, video from the server.

The closed source module required a username and a password to connect to the http admin interface running on the server and all run smoothly.

With vlc 2.1.x the username is gone. We have to configure the LUA password but there is no username required/configured.

I run vlc service as a non privileged user on the server (id: vlcuser)

Obviously I can not change the closed source module so the question goes for vlc.

Can I configure again a username for logging into the http admin interface?

Thank you All for Your time.

BR
TK

[edwardw]

https://wiki.videolan.org/Documentation ... _and_later

[eEll]

Not nice being condescending it beats the whole point of a forum... The wiki source doens't provide and answer at all. It's true that VLC has a flaw: requires a damn user name that doesn'exist! ... If someone could help us (and not just throw a useless link without READING THE CONTENT OF THE QUESTION) that'd be great.

the doc says to leave the field blank... Well, that doesn't work at all. VLC, when I attempt to play a stream from VLC client to VLC streaming server, asks for the username and won't allow to leave it blank... Soooo?

THANK YOU

[chubinou]

Hi,

hum, last post was 5 years ago.....

for your question, you can't set a username for HTTP admin interface in the current version of VLC.

[liatoss]

Just getting in the same issue... Well, according to the documentation (https://wiki.videolan.org/Documentation:Modules/http_intf/) hereby are tricks:
1) Is you start the VLC from command line, just add parameter --http-password type_your_pass_here and start the VLC
2) Go to the vlc http:port, it gives you login dialog
3) Leave username empty, type your password from the step 1) in the password box and click Ok.

For me it works,
B.r. Vlad.

[Rémi Denis-Courmont]

Not nice being condescending it beats the whole point of a forum... The wiki source doens't provide and answer at all. It's true that VLC has a flaw: requires a damn user name that doesn'exist!

I fail to see a flaw and the valid user name exists - it's just empty.

[STEPHANVS]

Jumping around the posts regarding the username and passwords, I see only arrogance, but no solution. PowerShell webrequests does not accept empty username, VLC will not accept webrequests without a password, and thus here we are in 2020 not being able to control VLC with simple PowerShell scripting.

[Rémi Denis-Courmont]

I don't care about PowerShell bugs. This is not arrogance. I just have other things to care about, for instance actual bugs in VLC.

And I don't think Edward was being arrogant in posting a link to the wiki. Mind you, we have a very small team of unpaid people, with very finite time to deal with support requests. And you just caused me to waste 5 minutes of that time.

[STEPHANVS]

Why should this be a PowerShell bug? If reasoning is the main objective, then I think both are design decisions (required username in PS and empty username in VLC), and... Ah, forget it...

[Rémi Denis-Courmont]

Empty username is a valid username under HTTP basic authentication and URL syntax. If PowerShell fails to account for this, it's very clearly a bug in PowerShell.

[Neotechni]

It's not just PowerShell though, Windows' HTTPrequest API also requires a non-blank username. And making it non-blank causes VLC to respond with "not authorized"

[vstefan]

It's not just PowerShell though, Windows' HTTPrequest API also requires a non-blank username. And making it non-blank causes VLC to respond with "not authorized"

Did you come up with a solution, I'm also looking for a workaround or solution