Paul Mansfield
Paul Mansfield
All logs are written to data/logs
This is left for other tools like awstats, goaccess or many others.
Don't think this is an NPM issue, there is lots of talk of podman issues around DNS after the default network change that was done for Podman 4 which was...
Not sure I can define a real problem point to look at here. I would say: 1. Turn off cloudflare proxying wait a day, try and setup NPM DNS verified...
That error seems to suggest that the forwarding from router to NPM is broken. It isn't an error that comes from a web browser after it connects to a proxy,...
I would say its not a huge security issue as it stands. However, many scans for audit purposes would say otherwise. Therefore the ports should probably be blocked from outside...
Just reading again, are you saying that you are proxying for example test.example.com to 192.168.0.166:7233 but 192.168.0.166:7233 is still available to hit?
As said before, the only thing I can think of is, on the host running docker, block all but the internal IP of the router from getting to the NPM...
@Rod0lphe its pretty simple, when adding an SSL certificate in the web interface, hit SSL certificate and then**custom** and upload the key, cert and intermediate cert. Then it can be...
I think you are talking about TCP Proxying which would be using streams which are also available in NPM. BTW, there is nothing stopping you fronting an HTTPS service behind...