I cannot connect through local access to my Cerbo GX running v3.60~46. Tried direct WiFi connection to device own access point, as well as through Cerbo connected to my WiFi network using 192.168.8.128 or http://venus.local/. This used to work fine before. Tried multiple computers and tablets. VRM access works fine. Cerbo shows in my network with the assigned 192.168.8.128 IP., it’s just that remote console is not opening.
Which user interface and Cerbo firmware version are you using? The new UI can cause some problems if there are some network port restrictions or firewall options.
Thanks Mike. Using v3.60~46. The problem happens even when connected directly to the Cerbo’s access point, so no network nor firewall restrictions there. Connecting through https://vrm.victronenergy.com/remote-console-2/###### works fine.
How about a screen plugged into the Cerbo’s HDMI port? - doesn’t have to be a touch screen to see what’s going on…
Have you tried reverting to 3.60~25 (or whichever previous version you have stored?)?
Yes, the HDMI shows the console right. Whatever the issue is, only happens with a remote console access over LAN. I reverted to the latest official release (not beta), and same issue. It looks like when I installed the latest beta, something got screwed up that not even reverting to another version fixes it. I’m puzzled by it. Probably best to do a factory reset, just trying to avoid that and having to reconfigure my entire system. I’m waiting for a new beta release hoping that this gets fixed. It’s worked flawless for a year and half since I installed this Cerbo unit, and through multiple betas.
What I just did was to switch to the classic UI and that works fine, accessible through 192.168.8.128 as always. Back to new UI now and console doesn’t load.
What device are you trying to access the rconsole on and how old is it? Also, after switching to the new GUI, power cycling the Cerbo may do the trick. I don’t have the issue currently, but did find some unexplained similar glitches on the beta, but all is quite stable on the latest for me.
Thanks. It was one of the first things I did, that is, to try multiple computers, tablets, and phones, even browsers, to disregard the device used to access the remote console on. I power cycled the Cerbo as well. What’s interesting as I mentioned in a previous post, is that switching the Cerbo to classic UI works fine. The glitch is with the new UI.
Good news, just took the latest 3.60~47 beta released today and everything is back to working fine. Will keep testing, but first attempt to connecting to the remote console thought the typical 192.168.8.128 IP worked fine.