Losing Connection to APEX

Same way as you did a port forward for port 80, do it for port 23.

Then you should be able to telnet into your router from outside and issue a 'reboot' command.

From a command line:
telnet your.domain.name.com
user
pw
reboot
 
BTW, this is what it looks like from my OSX command line. I assume it works similarly from Windows.
Code:
Josephs-MacBook-Air:org mgi814$ telnet heneryh.homeip.net 1023
Trying 173.62.210.230...
Connected to heneryh.homeip.net.
Escape character is '^]'.

AquaController Login
login: xxxx
xxxx
password: xxxx
****

AquaController> reboot

The only reason I had an opportunity to copy this was the web server failed on me again today and I just had to reboot to get it back.
 
Last edited:
After having the new firmware installed it seems like the issue for is less frequent, instead of every other day or so its now spread otu to maybe every 5-6 days. Last email with curt he logged into my unit and said there were no issue at that time, and i told him yes, because the unit is connecting properly right now. I told him that i will meail him again once it loses connection. Well i lost connection last eventing and i emailed curt. Im going to leave it in the disconnected state that it is right now so when they login hopefully they will come across something. I did however, find that even when not accessible via the ip or the web app or phone app i am still able to telnet into the unit and is giving me realtime data. I will hold of on rebooting it unil i hear back from curt or someone at neptune.
 
I did however, find that even when not accessible via the ip or the web app or phone app i am still able to telnet into the unit and is giving me realtime data. I will hold of on rebooting it unil i hear back from curt or someone at neptune.

This really points to the webserver process crapping out. Since telnet works, that means the whole tcp/ip stack works fine. I am not sure what they are using as their webserver, but I'd gladly play with this if I knew how to get a proper shell on the Apex. I have the problem occasionally too, and it behaves exactly the same (ping, telnet, etc all work, except http).
 
another update...

another update...

Just finished communicating with curt again. I informed him of the info i posted previously. He asked me to save all my configuration settings and email them to him. So i exported the settings and emailed him the .bin file. He also said i can go ahead and reboot, no need to keep it disconnected. So i telnetted again from work, did the reboot command and almost instantly all http access (ip, dyn.dns, android app, etc) refreshed and connected successfully.

For the time being, atleast now i know i can telnet into the unit and reboot it if and when it goes down again.

I will post again once i get a response from curt about my configuration files.
 
I have got same issues with loosing connection and Apex. Recently I had other problems ( resolved, thank Aquamanic :beer:) and I had to try lots of things, and one thing I did, is give Apex a fix reserved iP address ie:192.168.1.9. So whenever I reboot Apex or router or lost electricity, router always give back reserve address to Apex.

Since Monday I did not lose connection one time. I don't know if that could help other.
 
Update, so far so good

Update, so far so good

Well we're now about 600 miles from home. So far so good with being able to connect in remotely.

I also (like another post) found it more convenient to leave the APEX on DHCP and just reserve a DHCP lease for it in the router.

So far I can't repeat the remote connection problems. Maybe it was lost packets (which shouldn't happen with TCP I don't think) but I did make sure to set up and test remote Telnet rebooting before I left town.

I'm loving my APEX, but of course I'm a computer geek anyways. The reason I justified this purchase to my beloved wife was the water top-off needs (somehow I forgot to mention cheaper alternatives, oops). I'm LOVING the logs, data, temp control, networking access, and email/txt alerts.

Frankly I hardly think a device is worth buying if it doesn't have networking availability and commend Neptune Systems for making such a flexible aquarium controller.

I'll continue to try to reproduce my earlier problems, and if I can get a reproducible scenario I'll post again.
 
Lost connection again. As a temp way around the issue, for those of u having the same issue where a simple reboot resolves the issue and have opened up port 23 to be able to telnet into the unit. Next time ur on the road or not next to a computer theres a telnet app in the android market that works like a charm. I just tested it on my own unit. I'm guessing theres also an iphone version as well

Sent from my SGH-T959 using Tapatalk
 
just to add myself to the list, although not frequent, I've had to reboot the unit twice in 6 months. Last night being the second time. I am not on the newest firmware though, so I'll flash and see what happens.
 
Santa brought an Apex Jr. to me.

I've had to reboot it five or six times since the webserver dies constantly. Unfortunately, I didn't open a telnet port on the routers, so I will have to wait until my wife wakes up.

I don't know if it's getting overloaded from requests or if it happens after it turns my lights on and off. It's a two lamp 48" T5 HO, so it shouldn't be EMI.

I'm running 8B11, but for some reason, my wife couldn't telnet in from local network even after a physical reboot. It's up and running now, but for how long is anyone's guess.
 
Last edited:
In my opinion, everyone who is having this issue should definately be sending an email to neptune via their website and not just posting on this thread. According to curt I am only 1 of 2 people that are experiencing this issue that have reported it to him.

Sent from my SGH-T959 using Tapatalk
 
Well I tried reserving the IP within the lan settings of the router and so far I am at 5 days without losing the connection. Prior to this I had the Apex with a static but did not reserve that IP in the LAN setting. I will give it until 15 days before I declair it good.
 
You should place the Apex's static IP address well outside the range of your router's DHCP server as it will not check for any conflicts. DHCP is perfectly happy to assign a second device on your network a duplicate IP address since it doesn't know about the static one that you set.

For example, my DHCP starts at .100, so I assigned mine to .95 and never the two shall meet.
 
By the way, I sent my email at 10:36am and Paul was already investigating fifty minutes later.

That's excellent service, especially during what must be a busy time for them!
 
By the way, I sent my email at 10:36am and Paul was already investigating fifty minutes later.

That's excellent service, especially during what must be a busy time for them!
 
My problems may be (at least partially) with my router. I lost communications overnight (Reeftronics notifications). I could not get in remotely this morning.

I was able to remotely control a computer on the home LAN and it COULD access the Apex leading me to determine the DSL router wasn't properly handling the Apex traffic. A reboot of the DSL router resulted in reestablished communication remotely with the Apex.

NO changes or reboot of the Apex was necessary to reestablish remote connection, just a reboot of my DSL router. Since it did work to allow me to remote connect to a computer on the home LAN I'm guessing it stopped port forwarding the Apex remote port for some reason. I'll post any further updates as I experience them.

For now I'm leaving the original single public port forwarding to the Apex in place and adding another port forward *range* to point at the same internal Apex address. I'm curious if the single port forward fails whether alternate ports will work. That would definitely narrow my situation down to the router as being a/the problem
 
Last edited:
Back
Top