ljm42

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/

There can be transient errors connecting, giving it a few hours is a good solution. We're working on improvements to reduce that.

The My Servers plugin doesn't work on 6.8, so I guess you updated to 6.10.1 and then installed the My Servers plugin? Why did you stop on 6.10.1, you really should go all the way to 6.10.3 How are you currently doing remote access? You won't be able to sign in via a reverse proxy or anything that changes the url. Open a web terminal and run: unraid-api report -vv then look in the ALLOWED_ORIGINS area, that lists out the urls that will work. If you have further questions, please provide the output of this command (with one -v, as it is anonymized): unraid-api report -v and upload your diagnostics.zip file (from Tools -> Diagnostics) to your next post in this thread

A CORS error means you are not using an expected URL to access the server. If you open a web terminal and run: unraid-api report -vv it will list out all of the expected urls in the ALLOWED_ORIGINS area. As long as you use one of those you should not get the CORS error. Note: that command (with two v's) is Very Verbose, meaning it is not anonymized. If you want to post the output in the forums use a single -v (for Verbose)

Can you explain this more? What type of WireGuard tunnel was it? Did you use a different url to access the server once the tunnel was up?

Thanks for including your diagnostics, it says that your apikey is missing. Please click on your username in the upper right corner of the webgui, that will open a menu. Click the "Sign Out of Unraid.net" option. Then sign back in to get a new apikey.

To clarify, you updated what to what version?

What IP do you get when you go here? https://wanip.unraid.net/ Test first with a browser on your client computer, then open a web terminal on Unraid and type: curl https://wanip.unraid.net/ If the IPs are different then you must have Unraid behind a VPN or using a different route to the Internet. The IP that Unraid sees when connecting to that site is the one that matters.