I answered my own question above ๐ . I was running nginx proxy manager at port 880 because I was testing port forwarding. My casaos was running on 80. Hence I wasn't able to access my services this way. Now it's all good. I removed casa os and reassigned npm to port 80 again
castlepeak
So I'm running NPM inside a container and I mapped the external port 880 to 80. This shouldn't have conflict with NPM right? Since the port 80 is internal to the container?
Hi I tried setting up according to this guide. I can't access a proxy that has a subdomain configured in NPM. When I type the root domain, casa-os which is running on my machine opens up. Is there a chance I can't access LAN in my tailnet? Do I need to do additional config?
What steps would you substitute in the above guide if you want to use acme-dns? That'd be helpful for people following the above guide but want to use this option
My main concern is durability. The inner screen is way too fragile to be used without giving it any thought. Until durability is addressed to a sufficient extent that the device hardware can outlast its software support with everyday use, I prefer to stay in candy bar phones without my tablet in tow.
Yes. I can use my custom domain names to access my services when on tailnet now