Our great sponsors
-
Wonder if this is more my problem. I've just setup nextcloud using this postgres & fpm example. My end result is that Nextcloud creates a network for itself, and seemingly NginxProxyManager can't see that / access it. My solution previously was that I put Nextcloud and NPM on the same nginx2_Default network. Is this the problem, what's an alternative resolution
-
below is literally ALL I had to tell caddy to get RP with a cert. Caddy is easy to install on any machine (bare metal) cause it's compiled GO. So really can't help you with issues caused by NPM, never used it never will. If you are running this say from home you either run caddy on your router if that is possible or NAT port 443 to where your caddy instance is running. It might take a little time to get used to using caddy but in the end you'll be glad you never have to use NPM again. https://caddyserver.com/ They also run a very nice discourse forum that is really good for getting help. https://files.gpccaor.org { import r53-gpcca reverse_proxy /* http://server.gpccaor.net:11080 }
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.