Great video! Just used it to install NPM in my Docker. Everything went well until I tried to connect to my proxmox server. I just got a "500 Internal Server Error". Your instructions are good, I must have some other issue as I've also tried NPM directly in an LXC and got the same result.
Hmmm, I am not sure exactly what It could be, however I recommend checking to verify that NPM is running in docker. Using the command "docker ps" you should see if NPM is up, and on what port. I also recommend bringing the NPM container down, and restarting it to see if that resolves it. I really appreciate your comment! I hope your homelab journey is proving a fun experience!
Turns out that trying to access while on the same network (using SSL) will give me this error. If I access from outside my network it will work fine. Something to do with my router and NAT loopback. Not a problem now that I know the cause since the whole purpose of Nginx is to allow external access and that's how I plan to use it.
Hey man love all your videos they have been a great help while I was setting up my lab. I have run into a problem though. I set up npm but I don't have a hostname or an ssl cert so I just set reverse proxies for all the things running on my server using subdomains i.e. whatever.home.lab poining to the right port and then added a DNS rewrite for *.home.lab on my adguard instance. However, any subdomain I try to access in this way, it sends me back to an adguard login page. I know that this is different from what you showed, but you seem to know your stuff and I really need some help. Thanks for everything, man. Keep up the good work.
I am glad you are enjoying the videos! While I haven’t run into this exactly, im wondering if you set up your DNS rewrite to point your wildcard domain (*.home.lab) to the instance of your NPM instance? If you have, I’d try doing another DNS rewrite with NPM specifically ie. npm.home.lab and then point your wildcard to that as a CNAME entry, where instead of the wildcard pointing to the IP of your NPM , it points to the subdomain instead. Give that a go and let me know!
@@SelfHostedToast Thank you very much for your response, man. I tried having one dns rewrite for the npm.home.lab pointing it to the ip of the npm instance (which also happens to be the ip of the adguard instance just port 81 instead of 80) and a different rewrite for *.home.lab pointing them to npm.home.lab. Now instead of all subdomains leading to adguard I get an unable to find the server error. I don't get it man, dns rewrite doesn't allow for me to specify port, so probably the rewrite never goes to npm as it should. I don't know what else I can try.
Because adgaurd doesn’t support port specifications, you’ll need to specify your local dns entries in NPM. Using proxy hosts you can specify any domain to send traffic to a specific host:port service. In NPM you could do a proxy host for adguard.home.lab and filling out the IP, and setting the port to 81 should resolve your issue. Overall I think it’s best to use NPM for your local DNS entries. Let me know if that works!
@@SelfHostedToast I am trying to use npm for my local dns entries, but the problem is the dns rewrite isn't happening for the wildcard domain. What happens is the all the proxy hosts I have setup on npm for my services lead back to adguard at port 80. The queries never reach npm to be reverse proxied to the correct port and I don't get how I can fix that.
Believe me, if you continue this good videos you provide , you will become the next MKBHD 😉Keep it up man .
I really appreciate the support! I hope I was able to assist you in your homelab journey!
Your videos are excellent! Could you do one about Kasm Workspaces sometime?
Great suggestion! I’ll definitely showcase Kasm as it’s an essential part of Linux containerization!
Great video! Just used it to install NPM in my Docker. Everything went well until I tried to connect to my proxmox server. I just got a "500 Internal Server Error". Your instructions are good, I must have some other issue as I've also tried NPM directly in an LXC and got the same result.
Hmmm, I am not sure exactly what It could be, however I recommend checking to verify that NPM is running in docker.
Using the command "docker ps" you should see if NPM is up, and on what port.
I also recommend bringing the NPM container down, and restarting it to see if that resolves it.
I really appreciate your comment! I hope your homelab journey is proving a fun experience!
Turns out that trying to access while on the same network (using SSL) will give me this error. If I access from outside my network it will work fine. Something to do with my router and NAT loopback. Not a problem now that I know the cause since the whole purpose of Nginx is to allow external access and that's how I plan to use it.
Hey man love all your videos they have been a great help while I was setting up my lab. I have run into a problem though. I set up npm but I don't have a hostname or an ssl cert so I just set reverse proxies for all the things running on my server using subdomains i.e. whatever.home.lab poining to the right port and then added a DNS rewrite for *.home.lab on my adguard instance. However, any subdomain I try to access in this way, it sends me back to an adguard login page. I know that this is different from what you showed, but you seem to know your stuff and I really need some help. Thanks for everything, man. Keep up the good work.
I am glad you are enjoying the videos!
While I haven’t run into this exactly, im wondering if you set up your DNS rewrite to point your wildcard domain (*.home.lab) to the instance of your NPM instance? If you have, I’d try doing another DNS rewrite with NPM specifically ie. npm.home.lab and then point your wildcard to that as a CNAME entry, where instead of the wildcard pointing to the IP of your NPM , it points to the subdomain instead.
Give that a go and let me know!
@@SelfHostedToast Thank you very much for your response, man. I tried having one dns rewrite for the npm.home.lab pointing it to the ip of the npm instance (which also happens to be the ip of the adguard instance just port 81 instead of 80) and a different rewrite for *.home.lab pointing them to npm.home.lab. Now instead of all subdomains leading to adguard I get an unable to find the server error. I don't get it man, dns rewrite doesn't allow for me to specify port, so probably the rewrite never goes to npm as it should. I don't know what else I can try.
Because adgaurd doesn’t support port specifications, you’ll need to specify your local dns entries in NPM. Using proxy hosts you can specify any domain to send traffic to a specific host:port service. In NPM you could do a proxy host for adguard.home.lab and filling out the IP, and setting the port to 81 should resolve your issue. Overall I think it’s best to use NPM for your local DNS entries.
Let me know if that works!
@@SelfHostedToast I am trying to use npm for my local dns entries, but the problem is the dns rewrite isn't happening for the wildcard domain. What happens is the all the proxy hosts I have setup on npm for my services lead back to adguard at port 80. The queries never reach npm to be reverse proxied to the correct port and I don't get how I can fix that.
Try specifying a proxy host for NPM inside NPM itself, and then set the wildcard to that new domain instead of the wildcard to the IP of NPM