Тёмный

Using Portainer to install NPM and Configure Custom DNS Name Access for Portainer & NPM 

NetSec
Подписаться 19 тыс.
Просмотров 4,4 тыс.
50% 1

Опубликовано:

 

15 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 16   
@neoflix59
@neoflix59 2 года назад
Thank you for the videos you do . Some of them are out of my depth, but this one was really useful for me.. thank you
@NetSec
@NetSec 2 года назад
Great to hear!
@billimantecas
@billimantecas 2 года назад
Thank you for your video, help me a lot to understand NPM
@NetSec
@NetSec 2 года назад
Glad it helped!
@homelabservers
@homelabservers 6 месяцев назад
Hello, I bought a VPS server on the VULTR platform and installed docker, I did exactly what they said step by step, the status appears online on the proxy manager screen, but when I try to connect to my domain address, the website does not load and eventually I get Gateway time-out Error code 504 error. How can I solve this problem?
@AresNamjai
@AresNamjai Год назад
hello i have issue i got Gateway time-out when point domain , ip , port 81 on NPM
@NetSec
@NetSec Год назад
Not sure how you set it up, is ip:81 working? do you have port 81 opened to Internet?
@CatalystReaction
@CatalystReaction Год назад
do you think there is a way to not expose the portainer port and have npm use an internal ip:port?
@NetSec
@NetSec Год назад
if they are on same server, you should be able to use Internet ip:port.
@uparaupara
@uparaupara Год назад
This is useful. Thanks a ton. Can you show how to install Flowise and Botpress v12 through Portainer? And how to https them through Nginx Proxy Manager? I'd really appreciate!
@NetSec
@NetSec Год назад
sorry, never used them before.
@AresNamjai
@AresNamjai Год назад
thank you i just type command to open port ufw allow 80 ufw allow 81 ufw allow 443
@Kifixo
@Kifixo Год назад
Thanks for the video! But I think it's something wrong with it. At 16:26 you are creating a proxied subdomain at Cloudflare. This means that SSL/TLS certificates will be handled by Cloudflare, not NPM!! So the steps you do to create SSL Certificates at NPM are completly useless, if you leave them at HTTP Only you will get same behaviour with HTTPS working, as that's being handled by Cloudflare. I also tried to create a non-proxied subdomain and let the SSL be handled by NPM and Let's Encrypt, but that didn't work. Basically HTTPS request will not work that way :(
@NetSec
@NetSec Год назад
Great question. I am using Full, not Full (Strict), SSL/TLS setting in Cloudflare. Cloudflare will take care of the certificate between brower and Cloudflare. And NPM will take care the certificate between Cloudflare and destination Server.
@Kifixo
@Kifixo Год назад
@@NetSec Oh I see, so then, the let's encrypt certificate from NPM is not actually useless as I thought. All my setup finally worked thanks to you well explained video. Thank you!
Далее
You want a real Name Server at home? // DNS
32:31
Просмотров 258 тыс.
Quick and Easy Local SSL Certificates for Your Homelab!
12:08
The cloud is over-engineered and overpriced (no music)
14:39
Remotely access and share your self-hosted services
18:05
Flarum - Host Your Own Forums on Linode
32:21
Просмотров 2,8 тыс.
HomeLab SSL certificates for FREE with minimal effort
19:41
The intro to Docker I wish I had when I started
18:27