ljm42

I would say yes Looks like your cache disk is full Nov 18 09:11:41 Tower shfs: cache disk full ### [PREVIOUS LINE REPEATED 13658 TIMES] ###

Edit the config/network.cfg file on your flash drive and make the deletions/changes noted below. Then reboot and you should be good. # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DHCP6_KEEPRESOLV="no" BRNAME[0]="br0" BRNICS[0]="eth0" BRSTP[0]="no" BRFD[0]="0" DESCRIPTION[0]="1GB " PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" USE_DHCP6[0]="yes" IFNAME[1]="br1" BRNAME[1]="br1" BRNICS[1]="eth1" BRSTP[1]="no" BRFD[1]="0" DESCRIPTION[1]="10GB Ethernet" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.11.10" NETMASK[1]="255.255.255.0" IFNAME[2]="eth2" <<< delete this line PROTOCOL[2]="ipv4" <<< delete this line USE_DHCP[2]="no" <<< delete this line IPADDR[2]="192.168.11.10" <<< delete this line NETMASK[2]="255.255.255.0" <<< delete this line SYSNICS="3" <<< change this from "3" to "2"

Pressing keys on the keyboard may wake it up? Otherwise I think you'll need to reboot and figure out where to plug in the monitor until it lights up during boot. Or you can wait for someone else to chime in

Just guessing, but the monitor probably needs to be connected before you turn on the server, otherwise your motherboard won't initialize the hdmi port

So the problem was this multibyte UTF-8 character: ˆ (which is not the same as ^) This was fixed in 6.11.4, you can now use multibyte characters in passwords if desired: https://forums.unraid.net/topic/131122-unraid-os-version-6114-available/

Thanks for confirming, this will be fixed in the next release of the My Servers plugin

Hi folks, Regarding the original topic of this thread, the five DNS lookups originally had a one minute timeout, in the latest My Servers plugin release they each have a 10 second timeout, meaning this particular issue would add a max of 50 seconds to your boot time instead of 5 minutes (assuming your plugins are up to date). I am still thinking through my options for reducing that further for people who have setup their network such that DNS and/or Internet are not available at boot. In general though, Unraid is not optimized for this configuration. For the most trouble-free operation, if you run a PiHole I recommend having Unraid use a public DNS like 8.8.8.8 so there is no chance of the PiHole blocking it and DNS will be available even when the array is stopped. And for the most trouble-free operation I would recommend against running your router in a VM. It can work, but it makes your life very difficult if something goes wrong with your hardware and the array can't start, then Internet for your whole network is offline while you troubleshoot it. Not to mention regular reboots take longer while network requests timeout. I do not think there are changes in 6.11 that would affect boot times. But if you want to dig into this further, go to Tools -> System Log and look at the timestamps. If you find a large gap in the timestamps while booting then there might be something to investigate, in which case please post your current diagnostics.zip (from Tools -> Diagnostics) and a snippet showing where you think there might be something that could be optimized. Also describe your network situation. For troubleshooting DNS specifically, you should also boot using 8.8.8.8 as your only DNS provider, then you can find the same area in the syslog and compare the gaps. Post these diagnostics too.

Sorry for the trouble. This should be resolved by the work we are doing in the next plugin release.

Can you clarify what the issue is? If there is an error message, maybe provide a screenshot?

Thanks, the double start wasn't a major problem, but it will be resolved in the next release. The NAN will also be resolved in the next release. Until then please run `unraid-api restart` after a reboot to resolve it. Thanks for reporting these!

Would you please open a web terminal and run: unraid-api restart Does that fill in the blanks after a few minutes? We are looking into an issue that happens when the system first boots Also, please wait a few minutes and then give me the output of this so I can confirm what version you are running: unraid-api report

Sorry you're having trouble. There are several error messages discussed in this thread, can you please show a screenshot of the one you are currently getting along with a description of how long you've been seeing it, whether it is intermittent, etc? Please upload your diagnostics.zip as well (from Tools -> Diagnostics) Note that we were having some issues yesterday which could have resulted in some error messages, but those have been resolved: https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1189788

Hi Everyone! We're aware of some performance issues with the My Servers Servers, we're doing our best to fix the problems and get it back up to optimal performance as quickly as possible. You may notice that if you just created a My Servers account you may have difficulty connecting. This is due to an internal issue we're working to resolve. Most user accounts should be unaffected otherwise. EDIT: The issues have been resolved. Thanks for your patience!

No, as long as you've assigned unique ports to each service it should be fine

There are a couple of different things mentioned in this thread. If you are seeing the message that says "JSON.parse: unexpected character..." then I'm guessing you are using a reverse proxy to access the webgui? Those are not currently supported. If you run: unraid-api report -vv the section titled ALLOWED_ORIGINS will list the URLs that will work with your My Servers installation.

@chronkus Can you tell me approximately how long you waited before deciding the system had hung? When My Servers installs it does a DNS check for 5 hostnames. If your DNS is unavailable this will add a delay. On the previous version of the plugin it would potentially add one minute per check (so 5 minutes) on the current version it is down to 10 seconds per check (so 50 seconds). Although I'm considering further changes. If you are open to trying it again, please just let the system do its thing and see if it eventually does bring up the login prompt and start the webgui (in which case please grab diagnostics). Thanks!

That password does seem to cause problems, thanks for reporting! Oof, sorry you've got some bad luck there :~ If you need to get those drives going right now, you can easily downgrade to 6.11.1 by grabbing the zip from here https://unraid.net/download , opening it up, and copying the bz* files and changelog.txt over the same files in the root of your flash drive. Then reboot. 6.11.3 will be released soon to resolve this.

Thanks! Can you clarify what would happen if you install the My Servers plugin now... would there be an immediate issue (what would happen?) or would it be fine until you reboot? Unrelated to this, you need to make a small change and hit save to update your WireGuard tunnel

Interesting. Would you please provide your diagnostics.zip (from Tools -> Diagnostics) after booting normally without the My Servers plugin? I want to look for settings to try and reproduce this. And to clarify, what happens if you have a working system and then install the plugin? Are there immediate issues or is it fine until a reboot? Thanks Edit - moved this conversation here https://forums.unraid.net/topic/130696-my-servers-plugin-causes-boot-hang-after-updating-to-6112/

Hmm, I can't reproduce this. Using the webgui, I set the root password to: test;{]test and I had no problems logging back in with that same password. If you have another variant you'd like me to try, let me know.

The fix is in 6.11.2, so you'll need to manually update to that version and then hopefully from there you'll be able to check for plugin updates, etc without having to edit any files. See my earlier comment on how to manually update: https://forums.unraid.net/topic/128922-6101-6102-problems-downloadingupdating-pluginsos-from-a-cdn-url-location/#comment-1177573

Glad to hear you can recover without having to do a full reboot! I'm working on other projects at the moment, would appreciate if someone can help identify differences between these two diagnostics that would explain how enabling/disabling Docker resolves this

I'm guessing that on Settings -> Docker, you have "Host access to custom networks" enabled? Go to Tools -> Diagnostics and download your diagnostics. Then go to Settings -> Docker and disable Docker, Apply then enable Docker, Apply. Hopefully that solves it? If so, grab a second set of diagnostics and upload both here. I am trying to track down what changes when disabling/enabling Docker that resolves this.

woohoo! When you are ready to start setting up My Servers Remote Access, see https://wiki.unraid.net/My_Servers#Configuring_Remote_Access_.28optional.29

Feel free to delete the one with the old server name, it is not going to be used