pelux

The bitcoind container fails to start with the default settings in the template. Something to do with the txindex parameter. Attempting to starting the container throws this error in the Unraid GUI. The container will start if "-txindex" is removed from the Post Arguments in the template.

I've done this on my currently registered flash drive and everything seems to be working correctly, I can access the GUI. I donm't particularly care about recovering any plugin config but if I could recover my docker configurations that would be fantastic. Should I just try to copy over the old docker.cfg for this or is there more to it?

I've done this and can now access the GUI but cannot start the array due to invalid key. I'm assuming the next step is to replace the key with a new one bound to the new flash GUID but this note has me a bit worried: Note: Replacing a Registration key results in permanently blacklisting the previous USB Flash GUID. Does this mean that if things don't work out with this new flash drive, I won't have the option to fall back on my current, semi working, drive. Even by replacing the key again?

I deleted the contents of the plugin folder from my flash drive but the situation remains unchanged. I used the USB creator on a different flash drive and verified it boots and the GUI can be accessed. Then I copied over the content of the config folder (without plugins) from the old flash to the new one. Afterwards, it doesn't seem to boot properly, I can't access the GUI or terminal. Checking active clients on my router, it doesn't show up on my network at all. Maybe this wasn't the right way to proceed on the new flash.

As requested, here's the content of the config folder. I had to delete the NerdPack folder from the plugins folder as it was ~50MB and exceeded the max attachment size. Here's the config folder including the NerdPack subfolder in case that's also useful https://1drv.ms/u/s!AqjWMUZVGu8bhrQ3jAS4fZVFzCvgtw?e=QGfCkl config.zip

I noticed that too, I was expecting the file to get created during the next boot. Nonetheless I was still able to connect via SSH using either the server's IP or name (tower) without the network.cfg file. I've now manually replaced the network.cfg file with the one you've provided but my issue persist. I've ordered a new stick and will be trying that next. In the meantime, here's a new log if that helps at all. Thanks! tower-diagnostics-20200608-1458.zip

I've tried both suggestions and the results are the same. Here's some new logs if that helps. tower-diagnostics-20200606-1402.zip

I also tried setting USE_SSL to "no" in config/ident.cfg but that didn't work either. Anything else I can try?

Can't connect in safemode (Unraid OS GUI Safe Mode (no plugins)) either.

Is it possible to boot in safemode without connecting a monitor/keyboard to the server?

Server shutdown during extended power failure and after powering back on I can't access the web GUI. I can access the terminal via SSH, the shares are also accessible as well as all dockers running normally and accessible. I've rebooted the server once from the terminal but the result is the same. Not sure where to start troubleshooting. Diagnostics are attached. Thanks! Edit: I can't connect via IP or servername. I get this error in chrome: ERR_CONNECTION_REFUSED tower-diagnostics-20200528-1414.zip

I'm currently experiencing issues similar to those recently described here: http://lime-technology.com/forum/index.php?topic=28736.0 and here: http://lime-technology.com/forum/index.php?topic=28703.0 However the suggested fix in these threads do not yield a resolution. I'm convinced that the issue is related to my usenet addons as the Web UI started being unresponsive when I was changing some settings (everything was working perfectly until then, I don't even know why I was changing settings...) As per the above 2 other threads, it definitely seems that this is addon related so I tried disabling the addons. Without access to the GUI, I used the following method: 1. Rename the /boot(flash)/config/plugins directory. 2. Rename the /boot(flash)/plugins directory. 3. Rename boot(flash)/extra/. 4. Use the stock go file (boot(flash)/config/go). That didn't work. I've since then re-enabled unmenu and that seems to work fine, just can't get the to the default GUI. syslog shows telltale signs of emhttp issues, namely the last 2 lines: Sep 2 09:35:55 Tower emhttp: Plus key detected, GUID: 054C-02A5-3001-211090007936 (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (2): udevadm settle (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (4): :>/etc/samba/smb-shares.conf (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (5): cp /etc/exports- /etc/exports (Other emhttp) Sep 2 09:35:55 Tower emhttp: Start SMB... (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (6): /etc/rc.d/rc.samba start |$stuff$ logger (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (7): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (: ps axc | grep -q rpc.mountd (Other emhttp) Sep 2 09:35:55 Tower emhttp: _shcmd: shcmd (: exit status: 1 (Other emhttp) Sep 2 09:35:55 Tower emhttp: Start NFS... (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (9): /etc/rc.d/rc.nfsd start |$stuff$ logger (Other emhttp) Sep 2 09:35:55 Tower emhttp: Start AVAHI... (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (10): /etc/rc.d/rc.avahidaemon start |$stuff$ logger (Other emhttp) Sep 2 09:35:55 Tower emhttp: shcmd (11): /etc/rc.d/rc.avahidnsconfd start |$stuff$ logger (Other emhttp) Sep 2 09:35:55 Tower emhttp: auto start disabled (Other emhttp) Sep 2 09:37:07 Tower emhttp: emhttp_read_line: emhttp_read_line: input line too long (Other emhttp) Full log attached. Any help you can provide would be greatly appreciated, looking forward to your feedback. Thanks! P.S.: Is there any way to start the array from telnet? It's bad enough that I broke the addons but my wife is also mad at me because she can't watch her shows. If I could get the array started that would solve half of my problems right there. syslog-2013-09-02.txt