ljm42

Interesting. So this is another problem related to having a blank "Local TLD". Discord won't accept the submission with this bare url: "url": "http://Tower/Dashboard", I strongly recommend that you go to Settings -> Management Access and change "Local TLD" from blank to "local" (without the quotes). This will solve this problem with Discord by changing the url to: http://Tower.local/Dashboard I'd also recommend installing the Fix Common Problems plugin as it would have alerted you to other potential issues related to a blank Local TLD, more info here: https://forums.unraid.net/topic/120220-fix-common-problems-more-information/?tab=comments#comment-1099981

This is the expected behavior in Unraid 6.10.x, it only displays details for certificate_bundle.pem. The upcoming Unraid 6.11 release displays details for [servername]_unraid_bundle.pem certs too. Custom certificates should be named [servername]_unraid_bundle.pem as per the wiki. Other than not seeing cert details on the page, are you having any issues? If there are still issues please upload your diagnostics.zip (from Tools -> Diagnostics)

Tower_unraid_bundle.pem is for self-signed or user provided certs. The (my)unraid.net Let's Encrypt certificate has always been named certificate_bundle.pem I am not really clear on what changes were done manually. I think your best bet would be to get back to stock: * change Use SSL/TLS to No * delete all files in the config/ssl/certs/ folder on the flash drive * reboot And then follow the directions here to setup SSL: https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29 If you get stuck, please upload your diagnostics.zip (from Tools -> Diagnostics) along with details on the issue.

If your question is about the previous link, note that it had different instructions for 6.9 and 6.10. The 6.9 section did not talk about a url using the localTLD. If this is a new question... in 6.10 you can have both https://servername.localTLD (with a self-signed cert) and https://hash.unraid.net (with an official Lets Encrypt cert), depending on your settings for "Use SSL/TLS". For more details see https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29

You didn't mention what version of Unraid you are on, but the DNS *should* update automatically when it changes. If something like this happens again, you can use these tips to get into the webgui: https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

The ping itself is meant to fail, the reason we are doing this test is to confirm that 'backup.unraid.net' resolves to a valid IP. If you have set your DNS esrvers to 8.8.8.8 then it should. Note: this is an old thread, so the IP mentioned here is not the only valid one. Please post the output of the ping command so I can review it. As you might have seen from other threads, we have been working through some issues. We made some good progress yesterday, if you are still having issues please post details (including screenshots) of the exact error you are seeing. Also include your diagnostics.zip file (from Tools -> Diagnostics)

Look at the help for the "Local tunnel firewall", I've not used it, but you might be able to block access to your LAN with that.

LOL

traceroute and ping are not going to respond, the behavior you are seeing is expected. No port forward is required for flash backup. As you might have seen in some of my other responses, we are having intermittent issues at the moment. We made some changes today that will hopefully help, are your backups working now?

I'm guessing you have the UD Preclear plugin installed? see https://forums.unraid.net/topic/112073-my-servers-releases/#comment-1154449

Please see this: https://forums.unraid.net/topic/127114-management-ssl-cert-expired-no-ability-to-renew/#comment-1158724

We are seeing some intermittent issues, please try again later

See this: https://forums.unraid.net/topic/127114-management-ssl-cert-expired-no-ability-to-renew/#comment-1158724

Note that if you manually edited any files not on the flash drive ( /boot ), those edits will be lost when you reboot.

You would be better off finding a way to do this though your router.

If we let the tunnel update the main DNS resolver for Unraid then all of Unraid's DNS queries would go through the tunnel, which doesn't make sense. As mentioned in the OP, adding --dns to each container is the solution to this.

What url are you are trying to use to access the server when it fails? What is the error message? What "Peer type of access" did you choose when setting up the WireGuard tunnel? Please upload your diagnostics.zip file (from Tools -> Diagnostics) to your next post in this thread so I can confirm your other settings.

Interesting. Please upload your diagnostics.zip (from Tools -> Diagnostics) Also open a web terminal and run this command, then paste the results here: php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -v

It looks like there are some intermittent problems connecting, but as long as it does connect after a few hours it should be fine. We're working on improvements to reduce the intermittent problems.

Thanks for confirming! We'll track this down and get it fixed in the next release.

Hi folks, I suspect that the certificate was updated but the webserver was not reloaded afterwards. If you are running into this issue when using Chrome, hit the Advanced button and then the Proceed link to get into the webgui. Other browsers likely have similar features to get past certificate errors. Once you are in the webgui, open a web terminal and type: /etc/rc.d/rc.nginx reload Or another option would be to simply reboot the server. Once you have run that command (or rebooted) you will need to close ALL browser tabs pointed at this server in order for your browser to see the new cert. If you have any tabs open that are still using the old cert, the browser will not try to load the new one. You might want to restart the entire browser to be sure. Then try accessing the webgui. If this was the problem you will now able to access the webgui without any certificate errors. If you are still having issues, try a different browser entirely. If that doesn't help, please upload your diagnostics.zip file (from Tools -> Diagnostics)

Thanks. I see now that if the router claims the external IP is 100.x.x.x then it is likely CGNAT and port forwarding isn't really possible. It is basically like being double-NATd except that you don't control the Internet-facing router. Your best bet would be to see if you can upgrade your connection to one that does not use CGNAT. For a rather technical work around, try a Google search for "cgnat vps". That is well out of scope for anything we could support though.

Please upload your full diagnostics.zip file (from Tools -> Diagnostics). I suspect there may be an issue with renewals, but I need to see full logs to investigate.

Two possibilities, either 1) a file on the flash drive is being updated regularly, which means the flash backup has to run regularly or 2) something is wrong with flash backup. Please DM me your /var/log/gitflash file, along with a link to this thread. The easiest way to get it is probably to open a web terminal and type: cp /var/log/gitflash /boot and then grab the file off your flash drive

It is hard to say, there are many ways to complicate your network You'll need to dig through your network config to see what is up. Some things to look for: if you have a VPN running on your router, it could be routing traffic through the VPN. If you have more than one router, they could be directing traffic in different ways. It is possible your ISP has multiple ways for you to get to the Internet. Or maybe something simple like your IP address changed since the last time duckdns updated. The way the Remote Access solution works, whatever IP address Unraid gets when it does: curl https://wanip.unraid.net/ is the IP address that will be used when setting up DDNS for Remote Access. If your server cannot respond on that IP address then this Remote Access solution will not work for you. In that case, WireGuard is an option: https://forums.unraid.net/topic/84226-wireguard-quickstart/