mattie112

So to confirm: You have 4G internet and you don't want to use that external IP but you want to use a VPN external IP? Can you (from an other connection) access yourip:80 and yourip:443 this is really the first step, if that doesn't work there is no need in debugging NPM. I assume something like this should work: Unraid (or router) -> has VPN connection so it can receive traffic from VPNSERVER. Your VPNSERVER will forward ALL traffic on 80/443 (through iptables yes) to your Unraid. Then your NPM should have just the default config everyone uses. (and yes you could also forward 80 -> 8080 if you prefer in iptables) It looks like you also have Nginx on your VPNSERVER? Why? You want to forward all traffic right, not accept it there and then proxy it to NPM? If you want to accept it there you can simply run NPM on your VPNSERVER

I would suggest to just try it out. I use labels yes to manage it but the search is also great so I don't really use the labels to find my documents It seems you can use the "skip_noarchive" to skip doubling it if it contains text but I have no experience with that https://paperless-ng.readthedocs.io/en/latest/configuration.html#configuration-ocr

Why? You can add a cron to trigger certbot manually...

It seems that you have redis setup with a password? Did you set that up correctly? See :

What do you want to do? You can either mount /etc/hosts to the container (a file not a directory, it will "overwrite" the file in the container) You can 'docker exec -it pihole bash' to get a shell in the container and change/read the file from there Supply an 'extra_hosts (or add-host)' to your container then docker will inject it into /etc/hosts (https://docs.docker.com/engine/reference/run/#network-settings)

Well it really is a reverse proxy mostly used for SSL offloading. It has some access control features so you can use that. Like only allowing a certain IP or add a password. But in most routers you can also allow only specific IPs and most containers have some kind of login. So yeah in my opinion it is really just for SSL offloading. Nextcloud for example has users so you won't be adding a password to NPM so really only the accesslist is left over imo :) anyway you can open and close the port yes but you must open the port if you want to renew your certificate in a couple of months. It's not really the way to go with letsencrypt to have a flow like that. But yeah it should work.

So you want to host your site/nextcloud on some other port then 80/443? Why do you want NPM then? Only for SSL? Letsencrypt MUST use port 80 for it's authentication/verification. You can however run https on a different port. Or use your own / custom certificates.

Thanks! I got some e-mails from github so I figured you were looking into it If you need some changes let me know. And about the uninstaller: It seems kinda strange for an uninstaller to leave traces. I would also preferer it to delete everything it created. You might debate on if it needs to delete an entire directory or only the files it created in a directory. I would normally only remove->reinstall a plugin if I wanted to start with a clean state. But then again if everybody does that on Unraid..... Would be great if there where some guidelines from Limetech on how to develop a plugin and about this kind of stuff.

Great, guess I did that at some point but totally forget that I did that Thanks for testing it!

Whoops I think you are correct, I did change the "pluginver" there and probably manually added my version .txz to the flash. The .plg file should be in flash/config/plugins/snmp.plg I'm currently running a backup so I can't reboot it atm but I can try to remove it all and then manually reinstall just to verify my flow again. edit: the txz file should be in: flash\config\plugins\snmp

Upon reboot the "doinst.sh" should be exeuted, that file checks if we have a snmpd.conf on our /boot and if so it will copy it to /etc/snmp/snmpd.conf Does that not work for you? https://github.com/kubedzero/unraid-snmp/pull/1/files#diff-1fb19f48fc458b0bcde23e89158f1de55b789b97f62ba8e059ec029afaad9726R38

@kubed_zero did you manage to have a look at it? I have it running now and made some changes every couple of days. Also rebooted my server a couple of times and it seem to work like a charm here

Can you access 10.10.10.254:80 (and :443) internally? Or is your problem with external access? With my fork you do need to have it set to custom br0 with a fixed IP (like you have) so that should work. Or perhaps there is something in the log?

"When I click the link to lauch the shortcut, the browser times out; this happens if the cert is applied or not" What link/shorcut? You cannot access the NPM control panel? Or you cannot access one of the services proxied? What is proxynet? A docker network on your Unraid? And are the DNS servers your Unraid uses correct? If it doesn't resolve it is probably not using your pfSense as DNS server.

As long as NPM is accessable from the internet that is possible but letsencrypt need to verify you are indeed the owner by placing a small file with a 'challenge' code on the domain you are requesting ssl for. If it cannot read that code it cannot determine that you are the owner and it won't assign a certificate. So if you are 100% offline than this is not an option. You can however buy a ssl certificate if you supply your own CSR. But yeah not with letsencrypt. (well technically you can have an other host that is public request a wildcard certificate and then manually copy that certificate every 2-3 months to your local hosts but I don't have experience with that myself)

Again: what do you want to do? You can use the files as regular certificate if you want to manually configure? If you want to request a SSL certificate (through letsencrypt) than you NEED it to be accessable from the internet, this is how letsencrypt verifies the host. If you have a 100% offline host you cannot use letsencrypt.

What do you want? You want to have the the certificate file? Why not use NPM also for internal hosts? But anyway: /mnt/user/appdata/NginxProxyManager/letsencrypt there they are

Can you please verify / test that from the internet (so test it through 4G for example) you can reach port 80 over http and that that reaches NPM. Letsencrypt needs UNENCRYPTED access to the "acme" files.

Check if the correct folder is mounted (it should contain both config and certificates). Also make sure these files are readable by the specified user/group.

Thanks! Comments are welcome! I have tried the following: - clean install from my plugin, it starts with default - change the config and reboot -> new config is restored - update from your version - as long as you don't save the config once through the UI it won't do anything - as soon as you save it works like above If you manually remove the config it should restore the default config the next boot. btw: I use the snmpd.conf from the plugin as default. It will also use the contents of that file when you click on 'defaults' in the UI. Oh and I added the 'run_before_save' on purpose. If I add the php to the .page itself it will get executed also on first load of the UI. Not only when the form is submitted but hey I'm open to suggestions, I simply could not really find what the expected way was to do this... Thanks for looking into it, no rush it works great for me at the moment (And now I only need to test if snmp v3 auth works so that's really why I simply added the entire file instead of simply a user/pwd input field as the amount of options/config would be quite large in that case)

I think it was needed for when a bridge network is used. You can try it at least to see if it solves your problem? Than at least we know.

Allright, I hope I have done everything right but here it is https://github.com/kubedzero/unraid-snmp/pull/1

Do you have these settings? In network: In docker:

So yeah your NPM container cannot reach your 'target'. What is your target? Is that the IP of your unraid host or a container in the bridge network with it's own IP? Also what network is your NPM container in? ('br0' is the network, could also be something else) And just for funs: from the NPM container can you ping something like 1.1.1.1 or 8.8.8.8 or 192.168.100.1 (assuming this is your router IP)

Remove /mnt/user/appdata/NginxProxyManager to clear everything