diy solar

diy solar

conext gateway online but inaccessible

sondroyo

New Member
Joined
Sep 13, 2023
Messages
16
Location
USA
I have a Conext Gateway on 1.07 (latest should be 1.17). It was disconnected from its usual grid for some testing. It doesn't seem that we can access the device anymore, but it is definitely on the network with a DHCP assignment and it is connecting to InsightCloud according to both InsightCloud and the C-> light on the box.

I've tried:

Holding down the power button for ~12seconds/4beeps - no sign of reset or ad-hoc wifi network

USB stick in, beeps, but no config file

Paper clip in reset hole while off, power on, keep holding, appears to go through a reset process but no sign of reset or ad-hoc wifi network

Loading up the latest firmware on a USB stick - appear to copy config but does not update, even after restart

It is responsive to ping queries and, strangely enough, to telnet (but not sure what the password for this might be).

Is there some sort of memory issue manifesting itself here? Appreciate any advice.
 
Do by chance you have an AC adapter to try doing those things using, rather than using Xanbus power?
I recall mine not coming back after a Xanbus reset and having to do a factory reset. In my case, it worked with the only difference being I was using an AC adapter to power it.
 
Do by chance you have an AC adapter to try doing those things using, rather than using Xanbus power?
I recall mine not coming back after a Xanbus reset and having to do a factory reset. In my case, it worked with the only difference being I was using an AC adapter to power it.
Yes, it's actually only receiving AC power right now as I have it on the shop bench. Tried the power off, paperclip in reset button, power on and hold, wait for cycle maneuver again but no dice.
 
Have you tried a private browsing / incognito window and again in a different browser than you normally use?
I tried all the browsers just for fun. The only open ports appear to be 21 (ftp) and 23 (telnet).
 
Not to be annoying, but just to continue my own normal troubleshooting, have you tried manually typing in the https:// to make sure it starts the attempt on 443?
 
Not to be annoying, but just to continue my own normal troubleshooting, have you tried manually typing in the https:// to make sure it starts the attempt on 443?
I tried a manual https:// and a manual http:// too just for kicks. The connection is refused, I double checked it using unix curl's verbose tool. It's sitting on a router that has only my test laptop and the gateway, so no question that the right IP address is being contacted. The router assigns an IP address and lists the correct MAC address.
 
Had the same bug ... And found the fix! Unless someone confirms otherwise, I bet this is limited to the Conext Gateway, with its unique hardware setting it apart from the InsightHome & Facility. I also bet schneider knows about this bug but doesn't want to admit to a design defect with users wanting a replacement. ;)

Yes, we were getting bizarre symptoms over the last 6 months... Like logging into the GUI just fine, and seeing devices under that tab, but after picking one, finding that it would just spin its wheel and never populate selections like Configuration or Events. A reboot of the Gateway fixed that in the past, but now, on US time change day from Daylight to Standard time, the reboot quit fixing it. What's worse, after 2 more reboot attempts, the GUI login screen would no longer come up. Just like you, I started to feel it was a degrading memory problem.

In our case, we were additionally lucky that we had enabled Modbus for ports 502 & 503. Since I was developing a program to force charging to only occur from solar sources, I had tools to let me access the (in this case 2 x XW-Pro) devices. But after a while that started not responding as well.

****Big note: Any changes that you make take from this point on are totally at your own risk, the reader takes all responsibility for any equipment damage, configuration loss, or warranty violation! (Continued in next post...)
 
If you read closely in the Conext Gateway User's Guide, under features, there is a vague reference to an included 8Gbyte MicroSD card ... Used for keeping statistics. There is no other mention of using it. Since our Gateway is in a weather-tight shed, I had to scratch some old brain cells to recall a "Do not remove" label on the side of the box.

Once I removed the Gateway from the shed and temporarily moved its xanbus terminator plug to the end of the cable, a closer look revealed two such labels, on opposite sides of the box. This Gateway had gone out of warranty 4 months ago, so nothing to lose, so peeled off the label tape. Sure enough, one covered a (rather recessed) MicroSD, the other, a set of 6 pins.

I guessed what the pins were, so I went all the way and used a Torx screwdriver to open the box and read the PC board labels for those pins to identify Ground, RX, & TX data. From another project, I had a 3.3v serial to USB cable to attach from these pins to my PC. Powered the Gateway up with its 12vdc power brick, and I could instantly see the "u-boot" code listing off the interfaces and routines to bring it active. Useful info, but in the end, not required for the fix.

So then turned my attention to the MicroSD. You know the stuff you read that SD card memory bits can only function 10s of thousands of time before they fail? That means you should never use them for logging a couple of dozen register values every minute of every day, because even if the SD controller chip is reallocating good mem blocks in place of bad ones, it's gonna run out in a couple of years.

To remove the 8GB SD, you push it in with your fingertip till it clicks, then it pops out further so you can grab it.

I first figured I would try to recover/copy it to a new MicroSD with Linux disk tools. Well although Linux "sees" the sdx device there, the clowns at schneider decided to make it unreadable as any filesystem partition supported by my linux.

I went back and tried booting the Gateway with no card. But u-boot showed several messages about missing pieces. It was on one of these that I used the DHCP assigned IP to first try https, no luck. Then telnet, yes, but as mentioned before in this thread no user / pw would work.

Well, then found the fix. Inserted a new, Sandisk 32GB card into the Gateway and fired it up again... It spent a looong time at the "access the SD card" in the U-boot step... Reformatting?? Yes, I think so!

Low and behold, the GUI came up on Ethernet DHCP assigned IP. But you have to go back and use the default new user/pw and reconfigure the Gateway.

I used a 32GB MicroSD because that was all I had handy. Does that mean it will last 4x as long as the 8GB? I have no idea. I would however not try using larger than 32GB because there might be something like the old FAT 32 partition support limit. And just to take the research one step further... I tried mounting that "reformatted" 32GB drive in several OS's and again, they would not recognize it. :(

I have the feeling, everyone with the Conext Gateway model is going to run into this over time... Why couldn't the Insight Local app warn you? My guess is schneider would be happy to sell you a $700US+ InsightFacility box.

Unfortunately, I have been very busy trying to help a cousin recover her home after severe flooding in her area over the summer months, and haven't participated in this forum the way I would like. But I will try to reply to any questions as soon as I can.
 
Last edited:
I tried a manual https:// and a manual http:// too just for kicks. The connection is refused, I double checked it using unix curl's verbose tool. It's sitting on a router that has only my test laptop and the gateway, so no question that the right IP address is being contacted. The router assigns an IP address and lists the correct MAC address.
For some reason, the forum tool wouldn't let me do this as a reply on Friday. I know it's been almost two months since your OP, but just wanted to make sure you got a notification about my fix in the previous post ... Hopefully you haven't tossed your gateway already. :)
 
For some reason, the forum tool wouldn't let me do this as a reply on Friday. I know it's been almost two months since your OP, but just wanted to make sure you got a notification about my fix in the previous post ... Hopefully you haven't tossed your gateway already. :)
Thanks for reaching out through my website! Major research work. The old gateway is out at a remote site but there are guys working out there today. I will have them bring it in so we can give the fix a try after Thanksgiving. I will report back.

I should have thought about this angle a little bit. It is oddly similar to how a Ubiquiti NVR fails.
 
Thanks for reaching out through my website! Major research work. The old gateway is out at a remote site but there are guys working out there today. I will have them bring it in so we can give the fix a try after Thanksgiving. I will report back.

I should have thought about this angle a little bit. It is oddly similar to how a Ubiquiti NVR fails.
Hello, just wondering if you had a chance to test? If the remote site has a router doing DHCP on the CG's LAN, one of the guys could swap in a new microSD while it's temporarily disconnected / powered off (preferably in the cab of his truck). I would give it 5 to 10 minutes to reformat the new one and finish power-on booting. Then a remote https login should open that uses the temp new user/PW. Once in, if you're lucky to have a CG config backup, you can just load that, otherwise config from scratch. Although using wifi to get into the CG access point from a smart phone to do the new config should also work, that might be challenging for the guys onsite.

If it's a different problem (like some bizarre unintended network firewall / filtering that began blocking https), then replacing the original SDcard **should** put things back in the limited function like they were.

I understand that you are having some functionality the way it is, and with winter weather, remote access might be challenging. But I'm just thinking this fix could save some fellow sunshiners lots of bucks and wasted time waiting on schneider support lines if they find a problem marked with a successful solution.

Best regards ... Joe
 
Hello, just wondering if you had a chance to test? If the remote site has a router doing DHCP on the CG's LAN, one of the guys could swap in a new microSD while it's temporarily disconnected / powered off (preferably in the cab of his truck). I would give it 5 to 10 minutes to reformat the new one and finish power-on booting. Then a remote https login should open that uses the temp new user/PW. Once in, if you're lucky to have a CG config backup, you can just load that, otherwise config from scratch. Although using wifi to get into the CG access point from a smart phone to do the new config should also work, that might be challenging for the guys onsite.

If it's a different problem (like some bizarre unintended network firewall / filtering that began blocking https), then replacing the original SDcard **should** put things back in the limited function like they were.

I understand that you are having some functionality the way it is, and with winter weather, remote access might be challenging. But I'm just thinking this fix could save some fellow sunshiners lots of bucks and wasted time waiting on schneider support lines if they find a problem marked with a successful solution.

Best regards ... Joe
I wish this site would send a few notification e-mails...I would be better replying to you! I'll DM you my e-mail. Onsite guys opened up the microSD slot sticker and put in a "different" SD card, which didn't work out, I suspect we need a fully reformatted SD card to try anything so I asked them to bring it in. It's not in my hands yet.
 
Everyone should know that @JustJoe deserves major, major props, not just for problem solving but for persistence. Here's how the recovery worked:

existing microSD card was totally fried and non-responsive

microSD remote tech tried onsite was unformattable (hung up on formatting and got very hot)

I went with a 32gb card previously formatted fat32 - erased it, left existing drive name "NO NAME"

unplugged conext gateway from power

put in new microSD

plugged in ethernet for easy assessment, then powered up

all lights on, then off, then flashing power light for approximately 3 minutes, then power, cloud comms, wifi comms lights on.

I could tell it was working because it was broadcasting wifi, but since it was on my shop network I pulled the IP using the MAC address and all was good!

Other notes:

telnet password did not work as admin/admin123 and other variations like Admin/Admin123, password, etc. telnet confirmed only available during this issue, not when functioning regularly. Since I definitely did a full reset as part of earlier experiments by holding the power button until 4 beeps, when everything came back the default Admin/Admin123 was what worked for regular web based login.

CG was on ~1.07 during this process, now easily upgraded to 1.18. Awesome!

If anybody else ends up in this boat (incredibly likely) please drop a note here.
 
Everyone should know that @JustJoe deserves major, major props, not just for problem solving but for persistence. Here's how the recovery worked:

existing microSD card was totally fried and non-responsive

microSD remote tech tried onsite was unformattable (hung up on formatting and got very hot)

I went with a 32gb card previously formatted fat32 - erased it, left existing drive name "NO NAME"

unplugged conext gateway from power

put in new microSD

plugged in ethernet for easy assessment, then powered up

all lights on, then off, then flashing power light for approximately 3 minutes, then power, cloud comms, wifi comms lights on.

I could tell it was working because it was broadcasting wifi, but since it was on my shop network I pulled the IP using the MAC address and all was good!

Other notes:

telnet password did not work as admin/admin123 and other variations like Admin/Admin123, password, etc. telnet confirmed only available during this issue, not when functioning regularly. Since I definitely did a full reset as part of earlier experiments by holding the power button until 4 beeps, when everything came back the default Admin/Admin123 was what worked for regular web based login.

CG was on ~1.07 during this process, now easily upgraded to 1.18. Awesome!

If anybody else ends up in this boat (incredibly likely) please drop a note here.
Hey, very happy to hear the SD card replacement worked for you. ? I also think the additional detail you provided regarding the LED activity and timing will help reassure anyone else that gets stuck with CG SD card failing and trying this fix.

I'll add that even though I did not use the reset-to-defaults button, my CG user config and months of collected solar telemetry data were gone when starting with the new SD card, so that must be where that data is stored. Therefore, I'd suggest anyone following our example should review the Conext Gateway Quickstart Guide so they can decide whether they have the correct tools with them to do a brand new config over Ethernet or WiFi, especially before going out to a remote location. ?

And thanks for your kind words of appreciation! Heck, anytime I can keep schneider from earning $500-700 off of someone for a whole new replacement box they didn't earn, it's my pleasure, lol !
 
Last edited:
For those using InsightHome / InsightFacility ...
First of all, disclaimer, you should assume that opening one of these boxes could void an existing warranty. Also, the circuits inside are delicate PC board components, so only proceed if you have had adequate training and experience working with such components. So proceed only at your own risk...

The problems we experienced of failed microSD were after several hundred hours of operation. The Insight boxes which are designed to replace the CG have not been out in the field that long. Additionally, all 3 box models use the exact same firmware file, which makes me say hmmm...

As time passes, if the "Insight" box versions start seeing the same bug, do you suppose schneider didn't really want to totally redesign the PC boards, but instead redesigned the case so that an equivalent microSD + socket still exist *inside* without protruding to the outside for easy access? (Just think, they could save the money from training the assembly line worker to apply the "Do not remove" sticker.)

So what I'm suggesting, in the coming months, if someone with one of the Insight
boxes gets this bug and accepts the risk of opening it, please share whether you find a socketed microSD inside. ?
 
Last edited:
I have a Conext Gateway on 1.07 (latest should be 1.17). It was disconnected from its usual grid for some testing. It doesn't seem that we can access the device anymore, but it is definitely on the network with a DHCP assignment and it is connecting to InsightCloud according to both InsightCloud and the C-> light on the box.

I've tried:

Holding down the power button for ~12seconds/4beeps - no sign of reset or ad-hoc wifi network

USB stick in, beeps, but no config file

Paper clip in reset hole while off, power on, keep holding, appears to go through a reset process but no sign of reset or ad-hoc wifi network

Loading up the latest firmware on a USB stick - appear to copy config but does not update, even after restart

It is responsive to ping queries and, strangely enough, to telnet (but not sure what the password for this might be).

Is there some sort of memory issue manifesting itself here? Appreciate any advice.
To all, I just came across this same issue as a solar installer, as well as, individual user. However, the version of Insight Gateway I have I had to unscrew the 4 screws from the box since, the MicroSD card is not available without opening up the box by removing the 4 screws. once, opened, you can slide inward the top silver metal bracket that holds the 8 GB microsd card in place. Once, removed I was able to put into my laptop using a MicroSD adapter. Once, inserted I was able to go to the Computer Mgt/Disk Mgt and delete ALL partitions, create a single FAT32 8GB partition and pull out the card and re-insert back into the motherboard, slide the metal retaining clip back, towards the inside direction of the motherboard, from the side, and put the box back together. Reconnected the Ethernet and Modbus CAT5 cords and let it sit for a few minutes and it will come back online using your DHCP server. Look at your routers DHCP server to find the IP address assigned and you can log back in with the default Admin/Admin123 password. It will make you change your password at that time. I also, took the effort to change out the CR2032 CMOS battery since, it was down to 3.0 volts and a new battery is around 3.3Volts. It is a good time to change out the battery, as long as, you are in there. This will fix your issue....did mine thank you to the original poster @JustJoe for his guidance. I knew what I was looking for from his post just had to completely take apart the box. NOTE: Schneider uses a T-10 torq bit that is required to open the box/remove the 4 screws. Also, recommend once, you are into the web interface, again, update the firmware to at least version 1.18 and reboot. You should be all set. I was on version 1.17 when this issue happened so, 1.17 does not have a fix for this 8 GB card running out of space and locking you out. As noted previously the InsightCloud did still function as JustJoe stated just not the local IP address web interface. Thanks again @JustJoe
 
For those using InsightHome / InsightFacility ...
First of all, disclaimer, you should assume that opening one of these boxes could void an existing warranty. Also, the circuits inside are delicate PC board components, so only proceed if you have had adequate training and experience working with such components. So proceed only at your own risk...

The problems we experienced of failed microSD were after several hundred hours of operation. The Insight boxes which are designed to replace the CG have not been out in the field that long. Additionally, all 3 box models use the exact same firmware file, which makes me say hmmm...

As time passes, if the "Insight" box versions start seeing the same bug, do you suppose schneider didn't really want to totally redesign the PC boards, but instead redesigned the case so that an equivalent microSD + socket still exist *inside* without protruding to the outside for easy access? (Just think, they could save the money from training the assembly line worker to apply the "Do not remove" sticker.)

So what I'm suggesting, in the coming months, if someone with one of the Insight
boxes gets this bug and accepts the risk of opening it, please share whether you find a socketed microSD inside. ?
I have just had this same issue & resolved thanks to this thread. 3 year old Gateway (13 Nov 2020 manufacture date) for a remote site I manage. Gateway was reporting to the Insight portal but refusing remote login for the last 8 months. During my yearly maintenance visit to this site (22 hrs of driving, ferry, and boat to access) I was unable to log in locally wired or wireless, would not write the .html file, would not update firmware. After rebooting the device it no longer connected to Insight.

Schneider tech support was completely useless, as expected. Back at my shop opened up and saw the SD card (push in / pops out) and suspected it being the issue. Replaced it with a new 32 GB Micro SD card and the Gateway now boots, writes the .html file, accessible hardwire or WiFi. FW 1.12. Initially, I was getting this error:
--------
Secure Connection Failed
An error occurred during a connection to 192.168.100.1. You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number. Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL
-----------

I upgraded to fw 1.16 via USB. Logging on it gave me a similar issue, but this time allowed me to click the button to ignore / exempt from the error and voila - the login screen. All was reset to default, but am able to get this back online, saving my client $800 on a new device with 1hr of billable time for me.
 
Back
Top