carefreepastor

I am able to use my unRAID server as I did before I installed my new router, thanks to the posted advice of itimpi!

Thanks so much! I was hoping that it might be this simple but was worrying that it would not be. I have already pulled the flash drive and found the config/network file. I will use Notepad++ to edit the file and return it to the unRAID server. I will post here if I am successful in getting to the GUI and will change the status of this post to solved.

I purchased an Amazon Eero Pro 6 mesh router to replace a failed Linksys Velop mesh router. Installation of the new Eero was without problem until I tried to boot my unRAID server. I was not able to get to the GUI. In thinking things through, I realized that the old Velop, with a tcp/ip address of 192.168.1.1, handed out tcp/ip addresses in the range of 192.168.1.2 through 192.168.1.250. My unRAID server from the GUI had an assigned static address of 192.168.1.95. The new Eero router, address 192.168.4.1, hands out address in the 192.168.4.x range. I believe that this is the reason I cannot get to the GUI. I was also using the newer remote access feature as well. I also change the default name of the server. What should I do so that the unRAID server can receive a new address in the 192.168.4.x range?

I still need help with this

Thank you for the excellent second video about using Cloudflare to workaround a closed port 80, which is the case with Cox. After purchasing a domain name from GoDaddy, I have Let's Encrypt running as a docker now using dns and the log shows that it started properly (log image enclosed). My current problem, however, relates to Home Assistant docker accessing the cert file so that it will open in https. I have mucked around for more than two weeks without coming up with a solution. And, yes, I did watch the first video about setting up Let's Encrypt with dockers other than Home Assistant. i have read many, many postings and videos about how to use Let's Encrypt with Home Assistant; nothing I have attempted as a result of these how-to's has allowed me to use Let's Encrypt to successfully access Home Assistant with https. I am at a total loss and obviously need careful guidance to straighten things out. I would be happy to uninstall the version of Home Assistant which I now have installed and start over.

WOW! Now I feel like an even bigger idiot. After running an unRAID server for all these years, I have never used the simple http://tower command; I have only ever used \\tower. Thank you again! And I apologize for wasting your time. I so should have known better.

So, I received my new flash drive, a 32GB Kingston DataTraveler SE9. I downloaded a zipped copy of version 6.6.6 from the Lime-Technology site. I used Control Panel/Administrative Tools/Computer Management/Disk Management to find the flash drive; I formatted it to FAT32 with the drive name as UNRAID. I unzipped the downloaded copy of 6.6.6 on my local Windows 10 PC where it had been downloaded. I copied all of the unzipped files from my PC to the flash drive. I right clicked the make_bootable.bat file and chose the run as administrator command. After the bat file ran, I went back to the flash drive and renamed the config file to config.OLD. I copied the config file from the old flash drive, saved on my PC, to the new flash drive. I used the safely remove usb device sequence in Windows 10 and removed the new flash drive when told that it was safe to do so. I plugged the new flash drive into my unRAID server. I booted the server. However, all that was visible from my Windows 10 computer's Network screen was the flash drive. Though I did know that the unRAID server must have assigned a TCP/IP address, I wanted to know what that specific address was. I opened the router's web interface and found not only that a TCP/IP address had been assigned but that it was the same TCP/IP address as it had previously when the old flash drive was in service. I have attached 3 screen shots of the flash drive. I have no idea what else to do.

Again, Thank you! When the new flash drive arrives, I will get after things and, hopefully, mark this thread as solved.

Thanks to both of you with your quick responses. I have not changed any hardware since I backed up the original flash drive, and also I have a screen shot of the current hard drive array. I will wait until the new flash drive arrives in the next several days before I proceed. In this way, I can maintain the integrity of the second flash drive as mated to its GUID which has the second of the two Pro licenses purchased long ago. When the new flash drive arrives, I will load it with a fresh copy of 6.6.6. I will use the make bootable app which is part of the unRAID download. Then I will rename the config folder to config_old. Next I will copy the config folder from the now dead flash drive which I saved on my PC to the new flash drive. I will boot unRAID and do those things which the license manager prompts me to do. Does it seem to you that I understand the proper process? I did notice that the now dead flash drive, contents of which I have a copy, has a Pro1.key file. However, the flash drive which ought to have the second Pro license and which was updated as far as version 4.7 has only a super.dat file in the config folder. Is this because it was never used in actual running an unRAID server? I have copies of the config folder from both flash drives backed-up in 4 places: on a local SSD and a local external HDD and two off-site cloud locations, One Drive and Amazon Drive.

A long time ago, so long ago that I cannot even remember when, I purchased two unRAID Pro licenses. I cannot find the original licenses which came with the purchase. I installed whatever was the then current unRAID version on each of 2 Lexar flash drives. I know that somehow each flash drive's GUID is mated to one of the Pro licenses. I used one of them for my everyday unRAID server, updating it to new releases as they came along. The hardware of that server has been upgrade periodically up to its current version which matches the hardware in Lime-Technology's then current for-sale server of 18 monhts ago. The flash drive, which had been in service from the beginning, died this past week; it was on version 6.6.6 when it died. I do have a backup copy of the contents of that flash drive, though not a copy taken from within unRAID itself but, instead, a simple copy and paste version stored on a Windows 10 PC. At some unknown point, I must have updated the second flash drive to unRAID 4.7 and stored it away. When the flash drive in everyday use died, I went looking for the other flash drive and found it this morning. I also have a new flash drive on order which could be pressed into service to return my unRAID server to activity. So, now, what is the best path forward? I realize that the configuration file on the stored-away flash drive does not represent what I need for my current setup since it has never been used for an actual unRAID server; all I have ever done with it was to update it from whatever was the original version when I first began to versions up to 4.7. Still, is there some way to use it to get my server running again? Or should I wait for the new flash drive to arrive and then configure it to be the new OS for the server? If so, how do I do this? I have already begun to read about how to accomplish this, but I would appreciate a detailed description which would fit my specific situation. Or is there another method for getting my server up and running that I have not even envisioned?

Thank you for your help. After shutting down the unRAID server from the Management Utility and removing the flash drive and plugging it into another computer and running CHKDSK with "automatically fix file system errors" checked and removing flash drive from other computer after "ejecting" it and putting flash drive back in unRAID server and starting server up, all is well. All of the other boxes in the house connect to unRAID server with no problems. Again, thank you!

Thank you. I will shut down the server and run checkdisk. Way back when I purchased unRAID Pro, I did buy two keys. I have the other flash drive, with the other key, somewhere. I could dig that out and update it to the current version and plug it in, as well, to see if the the flash drive in the unit now is the problem. And it is TOWER and not TOWSER. Clumbsy old fingers sometimes do not type so well. When TOWER is used in the browser, I am able to access the Management Utility with no problem.

Back on August 1, I posted the above message. I must not have posted it in such a way as to have elicited help. I have free time again and am trying to get my server back online. I am experiencing exactly the same problem as before. The server has been off now for aobut five weeks. Since I am able to get to the browser interface with the server, I was able to shut it down from the Server Management Utility. The notepad file includes a syslog and an approximation of the message which windows gives me when I try to diagnose the reason why the contents of the tower are not available to the other computers on the network. I do not know what else to say other than please help . syslog9-20-2012.txt

192.168.0.111 is the address of the Windows box from which I ran PuTTY telnet program to access the unRAID console.

I cannot. I receive the same error message when inputtting \\192.168.0.110 as when imputting \\tower or duble clicking tower from the Network category of the Computer page. In rereading my original post, I see that I failed to mention that all of the other boxes in my network, other than the unRAID box are, Windows 7.