Leaderboard

Thanks for the feedback ! Yes, I'll implement the other features in an upcoming release 👍

Danke, jetzt ging es...es hat gebootet.

I have run the command in the provided link and it shows that there are 81 corruption errors. Anyway, I've reset the stats, ran a correction scrub, and also setup a user script as suggested. Let's see if any more errors shall occur.

There you go:

Interesting reply. I think I will leave it there with remote access using this feature. Given the ease at which an OpenVPN or Wireguard (using either your router or unRAID itself - native or via a Docker) connection can be established I see no reason why I would change that. It was good to experiment though. Thank you @ljm42 for taking the time to make such a thorough reply, it is appreciated.

Klick Mal nix. Was passiert dann? Erscheint der Text Loading ... oder wird tatsächlich neu gebootet. Wenn letzteres: Check Mal den USB Stick. Ist das eine Erstinstallation?

You are right... i didn't see the "TrueNAS" and was thinking about "unraid-to-unraid"

Exactly, just follow the procedure and your admin page is no longer accessible over the internet, only via local network.

Nur so zur Fehlersuche: Hast Du mal den Safe Modus probiert?

Did you read the recommended post at the top of every page of this thread?

ok merci pour le plugin et oui j'y avais pensé qu'en supprimant le dossier on perd tout mais une case a cocher au moment de la suppression et c'est plus propre et intégré

Doch das geht. Die Fritz!Box am entfernten Standort baut zur anderen einen Tunnel auf. So werden beide Netze verbunden. Natürlich müssen beide dann ändere IP Adressräume haben. Zb 192.168.178.x und 192.168.177.x Ich weiß nur gerade nicht ob die Multicast Pakete von Plex an die zweite Fritz!Box gesendet werden, damit die dortigen Clients von dem Plex Server erfahren. Müsste mal jemand von den Tunnel-Nutzern was zu sagen. @Ford Prefect du vielleicht?

open unriad terminal wondow, type the following mkdir /mnt/ram mount -t tmpfs -o size=115G tmpfs /mnt/ram/ add path into your machinaris setup inside machinaris plotting config

will do

Can't really tell why the image filled up, but the resolution would be Settings - Docker, set the service to be disabled. Reboot, Settings - Docker, Delete the image, then Re-enable the serivce. Followed by Apps - Previous Apps, check off what you need.

Vielen Dank habe es geschaft der Container ecomailz läuft mit einem Template 👍

So einen Container gibt es bereits: https://hub.docker.com/r/ecomailz/donnie Du musst nur das Template dafür anlegen. Also Add Container und dann vom Beispiel-Kommando die Werte übernehmen. Eventuell hilft das Video:

I ended up adding a completely new NPM container and was able to register new certs without issue, i guess I'll see if they renew in a couple months. Thanks for your help in troubleshooting, I'm still learning Linux and Docker, so any help is invaluable.

When I open up my dashboard I'm able to login but it's not showing any of my hosts, nothing shown in the main dashboard tab, just blank white below. Functionally all of the hosts are working. I tried restarting the container and clearing cache without luck. I did a few docker container updates so not sure if this was one that upgrading to the latest version has caused it. Any ideas on fixing it? Also, could I get a reminder on how to set a version tag for unraid/docker to revert to? Edit: Nevermind, changed browser and it appears to be a browser related issue. However, still curious the best way to revert container versions based on the tag. I tried adding :v1.16.1 and it didn't work..

For the people using my fork, (the port 80/443 one): I have just merged the latest v1.16.1 into my branch and pushed a new version. I'm doing this manually so I don't really push every version (as I have to notice it). But if there is any major issue of a fix that you'd like just send me a message and I will push it

You could check the location of the .htpasswd file (if you use one). That should not be readable by the web. Some generic pointers: https://stackoverflow.com/questions/6441578/how-secure-is-htaccess-password-protection/6442113 Not sure if NPM has somekind of bruteforce protection.

So your bitwarden is on 182.168.100.99 right? In your browser I don't see a port appended so it is running on port 80? Then why are you using port 8888? Or am I missing something?

You can try it manually: docker exec -it NginxProxyManager bash And then something like: certbot renew --dry-run or certbot renew --force-renewal Run certbot --help renew to see all options available

See: https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/?do=findComment&comment=944261

And the certificate is indeed correct? With all the required intermediate certificates? Is it from letsencrypt or an other provider? You can test your certificate with a site like ssllabs.com

So :80 works great but :443 does not? What is the issue then when visiting a https link? Do you get an error? No connection? You can also run a wireguard docker: https://hub.docker.com/r/linuxserver/wireguard And then on your NPM container:

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

You have to change all ports in your config to not overlap with the first container and then you have to delete all port mappings in the template and redo it with the same container and host ports. Most gameservers doesn't like it when you just change the port in the template itself like container 27015 and host 27016 <- if you do it like this you can query the game but you will get a timeout since the game thinks it's on port 27015 and tries to connect throught that port but can't because it's actually 27016, hope this makes sense to you...

i guess wireguard doesn't do a cleanup if you uninstall it: ip link delete wg0 deleting this wg0 made everything start working again

Worked like a charm. I think this should be noted somewhere as being "best practice" for new people setting the app up.

I added the following to my reverse proxy for the admin panel location /admin { return 404; } I only access the panel locally using the direct ip.

The same happens with Sophos XG, only seems to work with q35-2.6 Any feedback about this issue? @limetech

you have to use q35-2.6 - nothing higher works

Having issues connecting to the web ui of Deluge and use PIA?, if so make its not the changes regards port forwarding, see Q10 (and Q11 if you want to switch endpoint):- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md If the above is not related to your issue then please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md