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

Basic auth for web server? #383

Open
rubengargar opened this issue Jul 12, 2022 · 5 comments
Open

Basic auth for web server? #383

rubengargar opened this issue Jul 12, 2022 · 5 comments
Assignees
Labels
help wanted third-party Configuration from an external program is not necessarily our problem.

Comments

@rubengargar
Copy link

Hi,

I'm just updated our service to v2, and I see splendid features that I can use. One of them, is the integrated web server, but I would like to know if I can set some kind of Basic Auth for this custom web.

I have overwritten the generated index.html for my custom HTML, because I want some personalization further from default and also because I only need a big player view. Currently, I'm using Cloudflare->Nginx Reverse Proxy with Access List>Restreamer. Can I get rid of Nginx?

Thanks in advance!

@svenerbeck svenerbeck self-assigned this Jul 18, 2022
@svenerbeck svenerbeck added help wanted third-party Configuration from an external program is not necessarily our problem. and removed feature labels Nov 23, 2022
@svenerbeck svenerbeck removed their assignment Dec 8, 2022
@danielgoz
Copy link

@rubengargar - How exeactly are you config the Cloudflare->Nginx Reverse Proxy with Access List>Restreamer?
I am trying the same but can't figure out how.
Off course a native basic athorisation from the app would be way better.

@rubengargar
Copy link
Author

rubengargar commented May 22, 2024

Hi @danielgoz, we are moving away from this approach, but what we were doing is the following:

  1. Under our /data/www of our Nginx Proxy Manager Docker we pasted the custom HTML&JS, based on the one you can find on this repo for the standard webplayer.
  2. Create an A subdomain for our url on Cloudflare pointing to that NPM
  3. On NPM, create an Access List for that web
  4. On NPM, create a Proxy Host, with the domain name, destination ip and port (8080, 80...)
  5. Check Cache Assets, Block Common Exploits. Select the previously created Access List
  6. On Custom Locations, add the location with both slash at start and end, like "/location/". In forward hostname, we have to enter again the ip address with the same location, like "localhost/location/. Keep an eye on the slashes!
  7. Add the SSL, and profit!

Some links about the configuration: NginxProxyManager/nginx-proxy-manager#1027, NginxProxyManager/nginx-proxy-manager#104

I don't know if you are using straight Nginx, in our case were using NPM for easier administration by our staff

@danielgoz
Copy link

Thanks man... I will give it a go...

@danielgoz
Copy link

danielgoz commented May 22, 2024

Legend!
working as a charm.
it's kinda clanky though (sometimes it gets to a 403 forbbiden) but good enough for me.
the custom HTML&JS, thingy... is it because you want to customise the player page?
I dind't do anything like that...

@rubengargar
Copy link
Author

Yep, that was only because we needed to show n number of players by each website, so we did a custom html page and the JS was for a dynamic list of players .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted third-party Configuration from an external program is not necessarily our problem.
Projects
None yet
Development

No branches or pull requests

4 participants