ljm42's post in 6.10.0 - access issues was marked as the answer
Docker containers aren't really an issue, it is plugins that have the ability to interfere with the system.
I would go ahead and update to 6.10.1. After deleting the certificate, I expect this url will work in 6.10.1:
ljm42's post in My Servers Invalid Version: null 1652859771384 was marked as the answer
Developers are sometimes aware of small bugs but don't fix them because we are *sure* users will never see them. And then sometimes users do see them anyway
That is what happened with the "Invalid version: null" message, we didn't expect anyone to ever see it outside of testing.
Anyway, the message was harmless and has been suppressed.
Hopefully the server will come online when you run 'unraid-api restart', but if not our next release should resolve that.
ljm42's post in My Servers Error > Unraid API • CORS Error was marked as the answer
Hmm, the unraid-api should have noticed when you changed the Local TLD, I'll look into that. Please run these two commands:
/usr/local/emhttp/plugins/dynamix.my.servers/scripts/makestate unraid-api restart (no need to paste the output here)
Then run the report again and it should have the lyons url listed in the allowed origins.
ljm42's post in Restart only the webgui? was marked as the answer
This should do it:
FYI - Unraid 6.10 is a bit more strict with making sure your certificate matches your settings. I'd recommend running the Fix Common Problems plugin, it will warn you if your certificate is actually valid or not before you upgrade.
ljm42's post in Can't acces my UnRaid with the same link from inside and outside of home network was marked as the answer
We use two distinct urls because it means you don't need to setup split DNS, where a single url resolves to the WANIP if you are outside of your network and the LANIP if you are on your network. So:
hash.unraid.net resolves to the local IP of your server and is meant to be used when you are on the same network as the server. If you have My Servers Remote Access enabled, then www.hash.unraid.net resolves to your WAN IP and is meant to be used when you are outside your network. If your router has "local loopback" enabled, then you may be able to use the external url from inside your network. But that is a function of your router, not something we can control. It is usually only available on high end routers.
ljm42's post in json parse unexpected error was marked as the answer
What url are you using to access the server?
Based on your settings, it should either be:
If you are using a different url the API will have CORS errors
Also, there is an issue with this DNS server:
DNS_SERVER1="192.168.3.1" I'm seeing multiple errors:
ERROR: When using DNS server 192.168.3.1, the host 192-168-3-252.hash.myunraid.net does not resolve. May 5 13:54:24 SuperMicroTower root: âš ï¸ Warning: Your DNS server (192.168.3.1) is unable to resolve 'registration.unraid.net' May 5 13:54:38 SuperMicroTower root: âš ï¸ Warning: Your DNS server (192.168.3.1) is unable to resolve 'mothership.unraid.net' May 5 13:54:52 SuperMicroTower root: âš ï¸ Warning: Your DNS server (192.168.3.1) is unable to resolve 'wanip4.unraid.net' May 5 13:55:06 SuperMicroTower root: âš ï¸ Warning: Your DNS server (192.168.3.1) is unable to resolve 'backup.unraid.net'
Also, the syslog shows some network issues:
May 5 14:05:25 SuperMicroTower root: Fix Common Problems: Error: Unable to communicate with GitHub.com May 5 14:05:25 SuperMicroTower root: Fix Common Problems: Other Warning: Could not check for blacklisted plugins May 5 14:05:26 SuperMicroTower root: Fix Common Problems: Other Warning: Could not perform unknown plugins installed checks
This may be due to the DNS Server issue above, or it may be because of this:
May 5 14:05:26 SuperMicroTower root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network ** Ignored which is described here: https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/?tab=comments#comment-1100014
ljm42's post in Issue connecting via remote access was marked as the answer
Just to fill everyone else in... everything was working properly on Unraid's side, the issue was the DNS server the Windows clients were using. We changed the clients to use Google's 126.96.36.199 server:
and now they are able to use the Remote Access link on the My Servers Dashboard.
ljm42's post in Can I edit the resulting URL after generating new certificate? was marked as the answer
Setting up SSL is actually a feature of Unraid itself, not the My Servers plugin. The plugin builds on this feature to provide Remote Access if you desire.
Getting an actual legit SSL certificate like this requires a Fully Qualified Domain Name that is unique across all our users, so we assign each system a "hash" and use that for the hostname part of the url. It is not changeable. You should never have to type it though, some options are:
* Bookmark the My Servers Dashboard ( https://forums.unraid.net/my-servers/ ) and click the "Local Access" link from it
* Bookmark the https://yourpersonalhash.unraid.net url
* Type http://[servername].[localTLD] ( i.e. http://tower.local ) and it will redirect (note: type http not https)
* Type http://[ipaddress] and it will redirect
For more information about setting up SSL (this has been updated for Unraid 6.10, but most of it applies to 6.9 as well) see:
For more information about setting up My Servers Remote Access, see:
ljm42's post in my servers 带的ddns多久更新一次ip was marked as the answer
The system detects when the local IP changes and updates DDNS for yourpersonalhash.unraid.net immediately.
If Remote Access is enabled, the system checks the WAN IP every 10 minutes. If it detects a change then DDNS for www.yourpersonalhash.unraid.net is updated immediately.
If you are not seeing the updates, it is likely the DNS server you are using is caching the results. Try using one of the big public DNS providers, like Google at 188.8.131.52
ljm42's post in Router does not support forwarding one external port to a different internal port was marked as the answer
If your router does not support the ability to have one external port point to a different internal port, there isn't really anything we can do on the Unraid side to make that work.
But as mentioned in the docs we do not recommend exposing the webgui on port 443 externally:
If you need remote access through this router, I'd recommend changing your local access port (see Settings -> Management Access -> HTTPS port) to something random (14793, 21093, etc) and then configuring the router to pass that port through unchanged.
ljm42's post in Upgraded from Stable to 6.10 RC2, can't login to web GUI but SSH works fine was marked as the answer
Just to level set... On the login screen there is a "password recovery" link that takes you here:
It says to delete all three of these files from the flash drive and then reboot:
Are you deleting all three or just config/shadow?