Nginx Proxy Manager - ACCESS LIST protection for internal services

preview_player
Показать описание
Nginx Proxy Manager - ACCESS LIST protection. How can you easily lock down proxy hosts on the Nginx Proxy Manager with Access List protection and protect the proxy host from outside? #Docker #NginxProxyManager #HomeLab

Follow me:

Timestamps:

00:00 - Introduction
00:53 - How do Access Lists work in Nginx Proxy Manager
01:38 - Step by Step walkthrough
02:17 - User Authorization
04:30 - Access based on IP Addresses
07:24 - Conclusion

----
All links with "*" are affiliate links.
Рекомендации по теме
Комментарии
Автор

even after 3 years your video is still helpful

aliengoa
Автор

This was exactly the info I was looking for. I want to use nginx proxy manager to point to portainer but don't want exposed to the external Internet and I can do that now! Thanks!

jcdock
Автор

thank you so much!! that bug where you have to update the host has had me done in for a fair few hours.

nath
Автор

Thank you Christian. It's nice to have an extra layer of security on top of my FoundryVTT server. I wasn't sure how much it could be trusted so this makes me feel somewhat more secure.
Being new to the self hosting world it's great you put out videos like this for us noobs :)

murlock
Автор

Thanks for making this nice, simple and to the point - implemented this in a couple of minutes whilst watching the video

mpessex
Автор

Finally a good explanation about that topic, and the point of refreshing the host is key ¡¡¡, thanks again

MarcosHIDO
Автор

Exactly the information I was looking for. An extra layer of protection for my services seems good.

matuopm
Автор

Another great video about NPN! This channel is just amazing... Thanks.

JoseFerreira-xmzy
Автор

Many thanks for the tip in updating the proxy host after updating there access list credentials! That was driving me and trying to work out what was going on! :-)

GYTZ
Автор

Good guide. I use NPM but was not thinking about this feature until now.

GorkemYildirim
Автор

Obrigado Christian! Você salvou minha vida. / Thanks Christian you saved my life.

flavioalves
Автор

Fantastic tutorial! I am really liking this channel!

Blackwolf
Автор

Thanks for the video. It's weird that NginxProxyManager main website didn't cover this in their docs.

aopen
Автор

Hey. Thanks for this. Just 2 questions:
1. What happens to apps when it's set up this way? For example, bitwarden windows/Android app? Or is this only for the web app?

2. How would you set it up for dynamic ip address as would be the case for most of the users?

RaviWarrier
Автор

Well done! Exactly what I want. keep going.

dgeordgy
Автор

just wanted to say my thanks! finally confident enough to broadcast my apps to the public cloud. what i did was whitelist all cloudflare ip addresses ONLY. with cloudflare in front and npm behind, i should be safe enough ? or am i missing something else...

xorcist
Автор

This was exactly the info i needed, Thanks

WavePuntFrl
Автор

Another thing worth noting is that password given in "Authorization" tab cannot have special characters in them. Just takes alphabets and numbers (as far as I know but may be it does allow some symbols but not all!).

vba
Автор

The major downside of access list based on IP: It checks the public IP of your ISP always. So you have to take the IP which your router has. Allowing your local network is pointless, cause it is never checked.

DaNiePred
Автор

Might want to add somewhere that there's a bug with Custom Locations whereby access lists defined within the GUI do not apply to those locations. You have to define the configuration settings yourselves for each custom location within the "Advanced Settings" cog.

Mark-cfer