ljm42

Do you see a message on the page saying anything about DNS Rebinding? A screenshot would be helpful, but blank out the myunraid.net url Please upload the latest diagnostics so I can see if the message is still there.

Oh you should probably check your share settings and update any that still reference disk 4

I think if you did New Config -> Preserve All -> remove disk 4 -> rebuild parity (don't trust parity!) I think you are probably fine. But if anyone else sees an issue please speak up because as I said, I haven't actually done this myself.

I'm impressed! I think the normal situation is to put it off long enough that you eventually decide you need a bigger drive anyway. At least, that's what happened to me LOL

Let's fix this first: This error means there is an invalid custom contab in the CA Update Applications plugin. This website should be able to help you fix the crontab expression: https://crontab.guru/ if you aren't sure, post a screenshot of what you're putting into the plugin and let us know what you are trying to do with it.

You have a myunraid.net certificate; looking at the url you can probably guess why an IP address is important : ) https://[IP_address].hash.myunraid.net 6.11.x doesn't handle that situation well - if eth0 doesn't have an IP then nginx is unable to start because it can't generate that URL. You should be able to get around this by logging in to the console and typing: rm /boot/config/ssl/certs/certificate_bundle.pem use_ssl no Then http://localhost will work. This is fixed in the upcoming 6.12 series, where http://localhost will work even if you don't have an IP address.

It looks like you are running an old pre-release version, you should update to the latest. Did this problem with 500 errors happen on 6.11.5 as well? The diagnostics don't show any issues, the next time you get a 500 error, SSH to the server and type "diagnostics" to capture the issue. But be sure you have updated to the latest pre-release

Unraid isn't meant to be a general purpose web server and PHP isn't meant to be modified because the whole webgui relies on it. If you need pecl you'll probably want to do your work in a Docker container instead.

OK, according to your diagnostics, "DNS Rebinding Protection" is enabled on your network. There should be a message warning you about this on the Settings -> Management Access page? The system won't let you enable strict mode when DNS Rebinding Protection is enabled because then you will lose access to the webgui. I think you are saying that https://192-168-0-138.ac9xxxxxxxxxxxxxxx7316ad0567c55e478541f9.myunraid.net/ works from your client. In that case "DNS Rebinding Protection" Isn't an issue for your whole network, just the server. The server is set to use 75.75.75.75 for DNS, try changing that to 8.8.8.8 (see Settings -> Network Settings with the array stopped)

Strict mode only applies when using a myunraid.net cert. For more info about SSL see https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29

Hi folks, I haven't worked on this plugin in quite some time and I'm not sure when I'll get back to it. Currently it is non-functional in PHP 8 so I'm marking it as incompatible with 6.12.

On Settings -> Management Access, are there any messages or warnings on screen? Please upload your diagnostics.zip file from Tools -> Diagnostics

I'm also seeing calltraces in your syslog related to macvlan. The fix is to stop the array and go to Settings -> Docker and change "Docker custom network type" to "ipvlan"

Thanks for helping to test the pre-release, have you had a chance to read the release notes? https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6120-rc1-available-r2297/ https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6120-rc2-available-r2310/ Several of your plugins have not yet been updated for 6.12 and need to be removed from your system. You are getting these warnings from Fix Common Problems: * Warning: corsairpsu.plg Not Compatible with Unraid version 6.12.0-rc2 * Warning: disklocation-master.plg Not Compatible with Unraid version 6.12.0-rc2 * Warning: gpustat.plg Not Compatible with Unraid version 6.12.0-rc2 * Warning: nut.plg Not Compatible with Unraid version 6.12.0-rc2 Let's get those plugins removed and see if that does the trick.

It looks like you are using an unraid.net url, but something has changed on your network to enable "DNS Rebinding Protection". The culprits are likely a setting in your router, or some security software running on your client, or the DNS server used on your client. Follow the instructions here to get access to your server's webgui again: https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

Your screenshot shows that "IPV4 DNS Server assignment" is set to automatic. I would disable that and just set the specific DNS server you want. Or do it at the DHCP level and set it to just the working DHCP server for your whole network.

Looks like in Linux, the name servers are queried in order: https://linux.die.net/man/5/resolv.conf ...If there are multiple servers, the resolver library queries them in the order listed.... I'd adjust your DHCP server so that it doesn't hand out the failing DNS server.

For everyone else in this thread, assuming you are just having issues with My Servers connecting to mothership and not other things... First thing to do is go to the Plugins tab and make sure you are running the latest version of the plugin. Currently that is 2023.03.09.1140 Then check https://status.unraid.net/ and confirm we are not having back-end issues. If we are, then I apologize and ask you to please wait until those are cleared. If there are no issues reported on our end, try restarting the Unraid API via `unraid-api restart`. Wait at least 30 seconds, then reload the webgui. If restarting the api solves the issue then we still have more work to do on our reconnection logic. The API should be able to detect that it was disconnected and automatically reconnect. If restarting the api doesn't solve the issue then you need to check your network for a firewall or pihole or adguard that might be blocking the connection.

My Servers is like the "canary in the coal mine", it is quite visible so when there are networking issues it is the first thing people see. If multiple things are breaking then you have an underlying issue that needs to be resolved. It is very unlikely that My Servers is the cause of your issues, it is just another symptom. To completely rule it out, I'd suggest that you uninstall the My Servers plugin. When the problem happens with your containers, grab your diagnostics.zip file (from Tools -> Diagnostics) and upload to a new thread under General Support where you describe the problem in full.

First thing to do is go to the Plugins tab and make sure you are running the latest version of the plugin. Currently that is 2023.03.09.1140 Then check https://status.unraid.net/ and confirm we are not having back-end issues. If we are, then I apologize and ask you to please wait until those are cleared. If there are no issues reported on our end, try restarting the Unraid API via `unraid-api restart`. Wait at least 30 seconds, then reload the webgui. If restarting the api solves the issue then we still have more work to do on our reconnection logic. The API should be able to detect that it was disconnected and automatically reconnect. If restarting the api doesn't solve the issue then you need to check your network for a firewall or pihole or adguard that might be blocking the connection.

Please go to the Plugins tab and confirm you are running version 2023.03.09.1140 of the My Servers plugin. If you are still having trouble on the latest version, can you tell me about your system? 1) Have you used My Servers before on this server and suddenly this problem started? Or is this server new to My Servers? 2) What kind of router do you have? Is there any sort of firewall or pihole that could be interfering? 3) What are you using for DNS? 8.8.8.8 is a good non-blocking DNS server to use

You mentioned having issues over VPN. The same advice applies - your client still needs to be able to access a reliable DNS server. If you are using Unraid's built-in WireGuard client then be sure to set the "Peer DNS server" to something like 8.8.8.8 and not your local router. TBH though, if you already have a secure VPN connection, then there is less of a need for SSL. So accessing the server via IP address is probably fine.

The myunraid.net URL is an optional feature that allows you to access your server via an https URL without any browser warnings. In order to work, your server and web browsers need a solid connection to a DNS server which can resolve a local IP address for the domain name. You don't want to use this solution if your Internet drops regularly, because if the Internet is down then the DNS lookup will fail. When your browser is reporting "server cannot be found" that means at that moment the DNS server your client is using is unable to resolve the domain name to an IP address. The most likely cause is that either the DNS server your clients are using is flaky or your Internet connection is flaky. To rule out an issue with your DNS server running at 10.0.1.1, I would point the server and your clients to 8.8.8.8. If there are still intermittent issues then there is likely an Internet connection problem. Admittedly, there is also the chance the issue could be on our end with our authoritative DNS server. We do occasionally have issues setting up new servers, but I've not seen any issues once domains have been setup. If you make the changes above and continue to have issues, PM me your full hash.myservers.unraid.net URL and I'll see if it resolves for me. Note that uninstalling the My Servers plugin will have no effect on the url used to access your server as this is a feature of the base OS not the plugin. If you would like to disable the myunraid.net url for your server see https://wiki.unraid.net/My_Servers#How_to_disable_SSL_for_local_access

Huh. I wonder why my emoticons don't work

LOL it is still date based, just instead of a/b/c it includes the time. Thanks for adding the workarounds