ljm42

Please update to the latest version of the FCP plugin, there was a bug in the first release today.

Clear your browser's cache, and disable any popup blockers / ad blockers for the new url

Sorry about that, I see the bug. p.s. this was my bug, not Squid's

The best way to get the new url is to go to the Settings -> Management Access page. On newer versions of Unraid there is a section titled "Local URLs" that lists out your options, otherwise you can click on the "Certificate URL" for the myunraid.net certificate.

I agree with @dada051, your client is either having issues with DNS Rebinding or with DNS propagation. If you were previously running with an unraid.net certificate, then DNS Rebinding should not be an issue. Although depending on your network you may have taken steps to allow DNS Rebinding specifically for the unraid.net domain, in which case you'll need to do the same for the myunraid.net domain. On the client computer, open a command prompt and run these commands, pasting the results back here: nslookup rebindtest.unraid.net nslookup rebindtest.unraid.net 8.8.8.8 nslookup rebindtest.myunraid.net nslookup rebindtest.myunraid.net 8.8.8.8

Can you walk me through this in a bit more detail? What page are you refreshing? Are you seeing any error messages? What makes you think it is disconnecting and reconnecting every minute? If it helps, you might try capturing the behavior in a Loom video: https://www.loom.com/ If you feel the details are private, feel free to send it to me in a DM.

There are a couple of different topics in this thread. But if you had problems for a few hours just on Monday then it was likely this: https://forums.unraid.net/topic/131964-web-gui-ssh-broke/#comment-1199606

Proactive notifications are coming (we are still in beta afterall), but we first we had to give you the ability to delete corrupt backups without dropping to the command line (this was a recent add). Glad you were able to use that to get back up and running! This is exactly what we recommend in this case: https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1196555

Hmm, I'm not sure how provisioning a cert would have affected the download. But I'm glad you got past it!

Sorry folks. We made further enhancements to the health tracker after yesterday's outage so it would be able to detect this issue. And more importantly, we are working on improvements to the infrastructure.

Sorry folks, we had a DNS issue yesterday that prevented our unraid.net or myunraid.net urls from working for a few hours. This has been resolved and we are working on changes to prevent this issue. If DNS breaks in the future (i.e. your Internet goes down) there are instructions here for disabling SSL so you can get into your webgui via http: https://wiki.unraid.net/Manual/Security#Https_with_Myunraid.net_certificate_-_with_no_fallback_URL

Sorry folks we did have some DNS issues last night, we are working to prevent that from happening again. Your browser gets confused when SSL is enabled/disabled and there are multiple tabs open, so please close all browser windows/tabs pointing at your server. Not enough? completely restart your browser If you continue to have issues, please post your diagnostics.zip file (from Tools -> Diagnostics) and provide the full url that works along with one that doesn't.

Hey folks, we recently added a "Certificate provisioning" health check to our status board: https://status.unraid.net/ It will automatically alert us when it detects a problem, this should allow us to resolve issues more quickly. If you have provisioning issues in the future and the status board says everything is ok, please let us know!

At the command line, type: /etc/rc.d/rc.nginx reload If that brings back the webgui, great! Otherwise you'll need to type this to reboot: reboot So the system is throwing call traces: Nov 24 16:48:34 treebeard kernel: WARNING: CPU: 15 PID: 0 at net/netfilter/nf_conntrack_core.c:1205 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] Nov 24 16:48:34 treebeard kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark nvidia_uvm(PO) xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 igb i2c_algo_bit r8169 realtek nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core nvidia(PO) kvm_amd wmi_bmof mxm_wmi drm_kms_helper kvm drm btusb btrtl btbcm crct10dif_pclmul btintel crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd bluetooth mpt3sas cryptd sr_mod rapl Do you have "Docker custom network type" set to macvlan? You might try changing that to ipvlan (on Settings -> Docker Settings). I'm not super familiar with this but there are other discussions about it here, or maybe someone else can chime in. In general, I'd recommend upgrading from Unraid 6.11.1 to 6.11.5 but I know that can be scary if you are remote. The only other thing I see are some potential attacks: Nov 11 15:06:33 treebeard nginx: 2022/11/11 15:06:33 [crit] 5800#5800: *65198 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 43.128.225.197, server: 0.0.0.0:443 Nov 12 10:47:18 treebeard kernel: TCP: request_sock_TCP: Possible SYN flooding on port 22922. Sending cookies. Check SNMP counters. I'm guessing you have My Servers Remote Access enabled? If script kiddies have found your server I would change your Remote Access port to a different, high random number. Something between 1024 and 64,000. I don't know if this could be causing issues but I would change the port out an abundance of caution. You should also switch from the old unraid.net certificate to the new myunraid.net certificate, it has a different style of url that is more private. You can do this on the Settings -> Management Access page, I forget the exact wording but it is something like "upgrade certificate" And optionally, you can ask your ISP for a new IP address if you think someone is targeting you specifically. Oh, and it won't affect anything we've talked about here but please upgrade your My Servers plugin https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1196555

This is by design. You can read more here: https://unraid.net/pricing Attached storage devices refer to the total number of storage devices you are allowed to have attached to the server before starting the array, not counting the USB Flash boot device. There are no other limitations in the software based on license type.

Depending on how your Docker containers are setup, it is possible for them to override the system DNS. In fact, I recommend doing that exact thing over here: https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/ Not sure if that explains your situation or not. The bottom line is, I am completely stumped as to how/why resolve.conf disappeared and then came apparently came back on its own later. I am glad the diagnostics had some proof of it. But this area of the forum is specific to the My Servers plugin, which means that the folks who know more about the core system are probably not reading this thread. That's why I'm suggesting to create your own thread under General Support the next time it happens. And for best results it often helps to be on the latest version. This was my same suggestion to boianski once we realized they were having general networking problems. It appears that My Servers has a side hustle of showing people when their systems have random networking problems

At the time of the diagnostics, resolve.conf was broken, which led to the My Servers error message because DNS did not work. I don't know what caused the issue but it wasn't My Servers. My Servers was simply alerting you to the problem. 6.11.5 is the best stable version of Unraid currently available. At the time of those diagnostics there was a problem with the resolve.conf file. Checking for plugin updates likely would have failed during this time, probably other things as well. If nothing you care about fails then simply ignore the message. Or you can troubleshoot further as mentioned above, up to you.

Yeah, it takes a bit of network magic to allow docker containers to run on their own IP, and WireGuard tunnels running on Unraid require help from your router to access them. The ISP-provided routers I have used allowed static routes, maybe do a Google search for "[router name] static route" and see if anything comes up. Otherwise, moving either WireGuard or the docker container that needs to run on its own IP to a different system will allow everything to work.

Access the command line of the server via PiKVM and type: diagnostics Note where it tells you it put the file on your flash drive. Then download that file from your flash drive and upload it here.

This anonymized line shows that DDNS for your Remote Access url is working properly. The issue is with the port forward, I recommend that you contact your ISP.

I think it is likely you'll need to contact your ISP for help with the port forward. But there is one last thing we can check... open a web terminal and type: php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -v then post the results here (they are anonymized)

So looking at logs/syslog.txt, early on I do see that DNS looks like it was setup correctly: Nov 9 22:36:22 BlackPearl dnsmasq[11285]: reading /etc/resolv.conf Nov 9 22:36:22 BlackPearl dnsmasq[11285]: using nameserver 192.168.1.1#53 Nov 9 22:36:22 BlackPearl dnsmasq[11285]: read /etc/hosts - 2 addresses But then yesterday, the DNS configuration broke: Nov 28 07:27:34 BlackPearl dnsmasq[11285]: no servers found in /etc/resolv.conf, will retry I don't know what would cause that, but it would mean the server could not do DNS lookups which explains the error message from My Servers. I also can't tell if it was fixed? What do you get if you open a web terminal and run: cat /etc/resolv.conf Looking at system/plugins.txt, we can see that at the time diagnostics were taken, the system was not able to download the list of current plugin versions for comparison: Could not download current plugin versions So something was going on with your server's networking (likely the broken DNS) and the error message from My Servers is another symptom of it. My recommendation would be to upgrade to 6.11.5 (not much point in troubleshooting an older version). Then if you see the error message again, try checking for plugin updates, I imagine it will fail. Grab a fresh diagnostic and post to General Support asking for help with a networking/dns issue. Feel free to tag me, but I'm hoping someone else will see something that I don't.

The issues mentioned in this thread are resolved in today's release, please update your My Servers plugin: https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1196555

The issues mentioned in this thread are resolved in today's release, please update your My Servers plugin: https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1196555

The issues mentioned in this thread are resolved in today's release, please update your My Servers plugin: https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1196555