ljm42

Glad you're up and running!

Please upload your diagnostics.zip file (from Tools -> Diagnostics)

DNS Rebinding is enabled on your network, the myunraid.net url will work work until you disable that. Google "[router name] disable DNS rebinding" for hints. In the meantime, if you ssh to the system and type: use_ssl no you will be able to access the webgui via http://ipaddress

Can you clarify what you mean by this? What isn't working, and are there any error messages?

First, be aware that the dashboard will only show the remote access url if you are currently remote from your system, i.e. accessing the dashboard from outside of your house. If you are in your house it shows the local access url. If that doesn't explain the issue, double check that Remote Access is still enabled and double check your port forward. Setup instructions are here: https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29

Just a quick heads up we'll be making changes to our cloud services (mothership) in the next 30 minutes. Shouldn't be any downtime. We're back! Everything is looking good, if you're having issues open the terminal and run: unraid-api restart

right

Interesting. I see IPv6 messages on my system too. We might need to make some changes, but I'd be surprised if that ends up being your issue.

Glad you got it working

Interesting that restarting Docker resolves the problem. Next time it happens, try restarting just the network - at a web terminal type: inet reload The only odd thing I see in your syslog from the 6th are error messages about IPv6. Do you actually need IPv6? If not, you might disable that just to simplify things.

By far the simplest solution is to host the PiHole on another system. If you host it on Unraid then you have to enable "Host access to custom networks" and give the PiHole its own IP. This puts you in the "Complex Networks" category of the guide: https://forums.unraid.net/topic/84226-wireguard-quickstart/ which requires you to setup a static route on your router. All of the details are explained in first two posts of that guide. I can't really offer 1:1 support because there are too many variables and WireGuard fails silently so there aren't a lot of clues as to where the problem lies. But yes, the simplest solution is to avoid "Host access to custom networks".

DNS Rebinding prevents a DNS lookup from resolving to a local IP address. It has to be disabled in order for an unraid.net or myunraid.net url to point to your server. On some routers you can disable it for specific domains, on others it is an all on/off setting. Depending on your setup, another option would be to locally set a DNS record that points xxx.hash.myunraid.net to the right local IP. But if you forget that you did that it becomes very difficult to troubleshoot down the road

Swapping out your router should be fine, seems like there must be an issue with your port forward. It is difficult to troubleshoot WireGuard because it fails silently. All I can suggest is to read the first two posts in this thread carefully, particularly the part about forwarding a UDP port and not a TCP port. If WireGuard on 6.9.2 was working previously you should be able to get it working again. But note that it is rather old code at this point, and no fixes are available for this version. I recommend you look into upgrading to the current version of Unraid.

Would you be open to doing a screenshare over Discord? You can join our Discord server here: https://forums.unraid.net/topic/104017-unraid-official-discord-server/

Thanks for reporting, I hadn't noticed it previously but can confirm it is happening.

Yeah the issue is that eth0 doesn't have an ip address and that is needed in order to use a myunraid.net cert. If you don't want to swap the cables around... At the console, type: rm /boot/config/ssl/certs/certificate_bundle.pem use_ssl no Or if ssl is already disabled, do: rm /boot/config/ssl/certs/certificate_bundle.pem /etc/rc.d/rc.nginx reload Hopefully that should get the webgui to load again. Then go to Settings -> Network Settings -> Interface rules and reassign things so that the nic that has an ip address is recognized as eth0. Once you have an ip on eth0 you should be able to provision a cert.

Your cert should be good. Would you please update to today's release of Fix Common Problems and confirm it no longer warns about your setup?

Thanks for reporting this, I see the issue. Also mine and not Squid's

On the Settings -> Management Access page, do you see any errors/warnings about DNS Rebinding? The issue is your network is has DNS Rebinding enabled for the myunraid.net domain. You must have previously disabled that feature for the unraid.net domain, you need to do the same thing now for the myunraid.net domain. If you don't remember what you did previously, try doing a Google search for "[router brand] dns rebinding". This was mentioned in the OP here: https://forums.unraid.net/topic/132136-update-your-legacy-ssl-certificate-now/ and there are comments from other users in that thread that may be helpful as well.

Would you please Ah, in your other message you said "everything seems to be working" so I thought the certificate change had worked. Please get your diagnostics.zip file (from Tools -> Diagnostics) and upload it here.

I don't have a wildcard cert to test with, but I'll use the output from those commands to mimic it on a 6.9.2 system. Would you mind uploading your diagnostics.zip file (from Tools -> Diagnostics) as well?

Would you run these two commands please? openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g' Is this is an official cert provided by a certificate provider or one you generated?

see https://forums.unraid.net/topic/131564-myservers-error-after-changing-usb-stick/

Oh sorry I thought I replied to this. We plan to offer support for user provided ALLOWED_ORIGINS in the future but at the moment the My Servers plugin does not support this.

Once you have migrated your Unraid system(s) to use the myunraid.net certificate, then DNS Rebinding on the unraid.net domain is no longer a concern. You can remove any special handling of DNS Rebinding for the unraid.net domain from your router.