1). Yes, the Pi is connected to the home network via ethernet.

2. I logged in once. I'm assuming I changed it to DCHP (I'm not sure). And I cannot log into the controller anymore after changing things around in the Pi UI (when I initially logged in). I can see its IP Address (however it's different from what it was before).

3. I've found the device, and I see the new IP address, but when I try to log in as before the browser no longer allows me into the Pi. All i get is a "connection timeout" or "connection refused". Controller is still powered on and LED switched from Blue to Green but mainly stays Blue.

4. I did change my desktop network settings initially, and when the controller was given a new IP, I rest to default, and I tried changing the settings again, though this time it did not work.  I did try to access the controller from a laptop and still ran into the same issues.

Thanks for trying to help, nonetheless. I know this is a network issue, as the hardware LEDs are normal. It's just trying to find what small step is missing. I know this issue started after flashing the SD Card with a new firmware, but I'm not getting any error messages or red LEDs.

Thank you for replying! I tried this already and got it to work before, but then did something inside the controller and it no longer allows me to log in. I also re-installed the firmware for the controller and am no longer able to access the controller using the method you stated above.

Correct. The web browser does not allow me to connect. I either get a "timed out" or "connection refused" in the browser. I have yet to set a password so this may be doable. 

https://kb.acronis.com/content/7503 (is this the correct method to access telnet? how do I find out the port [or is this even necessary]?)

Sorry for being so inept. I'm unfortunately basing this off the assumption that I did actually change to DCHP. Not sure if I did or not. What I can say though, is that the pi registers as "unknown" in my router list. I know that this is the pi as no other "unknown device" is active. All other devices are known devices, and "rasp pi" is not one of the active devices on the network.

I'll see if maybe I can force/manually assign another address from the router (would this solve the problem?) When I reset it, I meant to say that I both flashed the SD card, and power cycled the controller. I tried the default address of 192.168.0.100 but this never worked from the beginning.

I'm beginning to think more and more that this is more of a networking issue than hardware. Thanks for your insight!

What are the next steps if you try to connect to the new IP, and still can't access the controller? (getting a cannot connect screen in browser).

I'm curious about this as well.

Thanks for the reply! I feel like I may have switched to DCHP by accident. If I did do this, what would I now have to do in order to log in? My router has given it an address of 192.168.1.100, but when putting that in, I get a could not connect screen on the browser. I'm about 99% sure I didn't delete or change the original password (which was blank), and I can't even get to the log in screen.

I posted previously in the Avalon 741 announcement forum, but figured this was the right place for the post.

I just received my miner yesterday. I got everything up and running, fans working, blue lights, etc. Had some difficulty logging into the controller, but finally after some network tweaking got in. I tried to put in my pool information, and my miner went from being loud, to yellow idle. Then, when I restarted the miner, all pool information was erased from the UI, and the miner went almost silent (fans still running idle). I thought I may have done something wrong to the controller (I'm new to this, so I figured I erased something I shouldn't have in the controller UI), so I flashed the SD with a new instance of the most up to date firmware. After doing so, I could no longer log in to the controller.
I can still see it on the network, and it is connected and on, but cannot not access the UI via IP. So I thought, maybe I can try and assign a new IP for the controller. I tried this via my router, and continued to get a "refused to connect" issue on the browser. original ip was 192.168.1.74, and when that stopped working, forced it to 192.168.1.100. Not sure what I've done wrong but I can no longer access the miner at all.

Any ideas as to what I am doing wrong, or what I can do to start from scratch?

Currently powered by 2x EVGA 750 G2 , LED on miner is yellow, LED on controller changes from blue to green every now and then, but mainly stays blue. Flashed with most up to date firmware off of main Canaan page. Pi I am using is Pi 3 Model B. Connected via Ethernet.

Thank you for all your help!  

Hey guys,

I'm completely new to mining with Avalon 741 hardware. I just received mine yesterday and had the worst time setting up the miner. I finally connected to it after extensively switching around IP addresses, and then after restarting the Pi (its a 3 model b), I could no longer connect. I can still see it on my network, but for some reason can't log in anymore. I flashed the SD card with the most up to date firmware, and still cannot access the controller. Any ideas on what could be going on?

Thank you for all your help!

Edit: The LED on the miner is Yellow, and the LED on the controller switches from Blue and Green every so often, but mostly stays blue.