Reply
New Member
Posts: 19
Registered: ‎09-18-2017

I need to know how to get this working again.

I've read submax is discontinued. I've read that the online access is discontinued. I've read things that seem contrary to that as well.

 

I have one client who has asked me to FIX there installation. I could not access the info from the phone app (it had stopped working). I upgraded the firmware on the gateway. I couldnt see any panels or semm to get this working.

 

Is there a way to know exactly the current procedures that  I should do next?

 

What the customer whould expect (ie phone app or some other way to determine his unit is working or not)

 

Who is the support authority on this?

What company is responsable or liable for this equipment? By that I mean , this is not low voltage equipment and there are serious legal requirements for an installation like this that I do not think are met if there is no way to determine the status of the equipment. So what is this deal? should this equipment be uninstalled and returned? is iot supported or not? Where are the docs ?  Any help would be appreciated.

 

 

Ubiquiti Employee
Posts: 139
Registered: ‎09-05-2017
Kudos: 115
Solutions: 4

Re: I need to know how to get this working again.

Hi Tim, 

 

The cloud for sunmax is up again and running. Please refer to Carlos post in community: https://community.ubnt.com/t5/SunMAX/On-Cloud-Monitoring-Service-back-online/m-p/2059045#M2869

 

Regarding documentation, you can find it following this link: https://help.ubnt.com/hc/en-us/categories/201589638-sunMAX

 

If you have a different troubleshooting questions, please feel free to contact  here Carlos, I am sure he will be able to provide answers. I will send him link to your post. 

 

BR,

Andrejs

Ubiquiti Employee
Posts: 140
Registered: ‎01-10-2016
Kudos: 59
Solutions: 5

Re: I need to know how to get this working again.

[ Edited ]

@timbeasley:

 

Thank you for reaching out. To provide you a better support please answer these questions:

 

(1) In what country did you install this equipment? 

Every country has its own regulations, and may comply to different industry standards. For the case of US, it even goes one step further where each State has its own regulation

 

For your reference here we share datasheets of SunMax where you can see our compliance per region:

        US, Canada and Latinamerica:

        https://www.ubnt.com/download/sunmax/default/default/sunmax-datasheet

 

        Europe:

        https://www.ubnt.com/download/sunmax/default/default/sunmax-datasheet-eu-european-version

 

(2) Have you installed a monitoring solar-gateway in this site? 

If so, is it running cloud monitoring or local monitoring. At the moment both flavors of monitoring are working. What is under maintenance and offline for security issues is the sundesing cloud-service.

 

If your site had been monitoring with the cloud service, and you never installed the local fw, it means that you can use your sunmax.ubnt.com account to log into your site, and see its status now. This service was down twice for a couple of weeks in recent months, so can you please check now at your site.

 

(3) Can you describe the behavior your site is experiencing? 

 

Once you provide the above information, you can send me a private message with your site name, no need user, no need password, so I can check from the cloud server on what is the status of your site, and start debugging from that.

 

Best regards,

UBNT-Carlos

 

New Member
Posts: 6
Registered: ‎01-11-2016
Kudos: 1

Re: I need to know how to get this working again.

Ubiquiti Employee
Posts: 139
Registered: ‎09-05-2017
Kudos: 115
Solutions: 4

Re: I need to know how to get this working again.

Hi @jjpermenter @UBNT-Carlos will reply as soon as possible. 

 

 

Best Regards,

Andrejs

Ubiquiti Employee
Posts: 140
Registered: ‎01-10-2016
Kudos: 59
Solutions: 5

Re: I need to know how to get this working again.


Andrejs wrote:

Hi @jjpermenter @UBNT-Carlos will reply as soon as possible. 

 

 

Best Regards,

Andrejs


@jjpermenter:

 

Have you tried to toggle power of your solargateway?.

If not, you may do this in the night time when there is no power production to be stopped,

by simply turnning off  your Solar-Plant 240V AC breaker for some seconds, and then turn it on.

Check after five minutes if your system reporting is back online.

 

Since it will be during the night, you will see a clear outcome until next morning. But to check the outcome asap, please PM me your solar-site name, so we can search your solar gateway reported to the backend after the toggling regardless it is night.

 

Regards,

UBNT-Carlos

Ubiquiti Employee
Posts: 140
Registered: ‎01-10-2016
Kudos: 59
Solutions: 5

Re: I need to know how to get this working again.

@timbeasley

 

Thank you for reaching out, and trying the toggling AC power.

 

Regarding the site name you provided in PM, the backend check I did shows that

the last heartbeat provided by your solar gateway to the cloud server was on August 15, 2017, 3pm.

 

Before going any further please access your solargw ui to confirm that you have the cloud-based fw 9.41 running.

The sunmax install app will only show cloud connected installation.

 

@jjpermenter I will gladly check your site once I receive solar site name in PM.

 

Thank you very much,

UBNT-Carlos

New Member
Posts: 19
Registered: ‎09-18-2017

Re: I need to know how to get this working again.

Hi i uploaded the firmware and restarted . I am onsite now.

 

 

1970-01-01 00:00:19 (none) syslog-ng[593]: syslog-ng starting up; version='3.0.5'
1970-01-01 00:00:19 (none) syslog: /etc/rc.common: line 143: log: not found
1970-01-01 00:00:19 (none) uboot-autoupdate: U-Boot image hashes match. No upgrade necessary.
1970-01-01 00:00:19 (none) syslog: uboot-autoupdate: U-Boot image hashes match. No upgrade necessary.
1970-01-01 00:00:19 (none) syslog: /etc/rc.common: line 143: log: not found
1970-01-01 00:00:19 (none) kernel: [   19.330000] UBI: scanning is finished
1970-01-01 00:00:19 (none) kernel: [   19.380000] UBI: attached mtd5 (name "overlayfs", size 14 MiB) to ubi0
1970-01-01 00:00:19 (none) kernel: [   19.390000] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
1970-01-01 00:00:19 (none) kernel: [   19.480000] UBI: available PEBs: 0, total reserved PEBs: 118, PEBs reserved for bad PEB handling: 62
1970-01-01 00:00:19 (none) kernel: [   19.500000] UBI: background thread "ubi_bgt0d" started, PID 606
1970-01-01 00:00:19 (none) kernel: [   19.560000] UBIFS: background thread "ubifs_bgt0_0" started, PID 610
1970-01-01 00:00:19 (none) kernel: [   19.610000] UBIFS: recovery needed
1970-01-01 00:00:19 (none) kernel: [   19.800000] UBIFS: recovery completed
1970-01-01 00:00:19 (none) kernel: [   19.810000] UBIFS: mounted UBI device 0, volume 0, name "ubi_volume"
1970-01-01 00:00:19 (none) kernel: [   19.860000] UBIFS: reserved for root: 0 bytes (0 KiB)
1970-01-01 00:00:19 (none) ubiconnect: Successfully connected to overlayfs
1970-01-01 00:00:19 (none) syslog: ubiconnect: Successfully connected to overlayfs
1970-01-01 00:00:29 (none) kernel: [   29.960000] UBI: scanning is finished
1970-01-01 00:00:30 (none) kernel: [   30.000000] UBI: attached mtd6 (name "stash", size 911 MiB) to ubi1
1970-01-01 00:00:30 (none) kernel: [   30.020000] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
1970-01-01 00:00:30 (none) kernel: [   30.080000] UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1074986148
1970-01-01 00:00:30 (none) kernel: [   30.120000] UBI: background thread "ubi_bgt1d" started, PID 620
1970-01-01 00:00:30 (none) kernel: [   30.190000] UBIFS: background thread "ubifs_bgt1_0" started, PID 624
1970-01-01 00:00:30 (none) kernel: [   30.390000] UBIFS: FS size: 887816192 bytes (846 MiB, 6992 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
1970-01-01 00:00:30 (none) syslog: ubiconnect: Successfully connected to stash
1970-01-01 00:00:30 (none) ubiconnect: Successfully connected to stash
1970-01-01 00:00:31 (none) syslog: rc.common
1970-01-01 00:00:31 (none) rc.common[637]: ubnt-post-fw-upgr running
1970-01-01 00:00:31 (none) syslog: rc.common
1970-01-01 00:00:31 (none) rc.common[637]: ubnt-post-fw-upgr upgrade network config
1970-01-01 00:00:31 (none) syslog: rc.common
1970-01-01 00:00:31 (none) rc.common[637]: Restore default network config
1970-01-01 00:00:31 (none) syslog: rc.common
1970-01-01 00:00:31 (none) rc.common[637]: ubnt-post-fw-upgr done
1969-12-31 19:00:32 (none) syslog: /etc/rc.common: eval: line 1: procd_add_mdns: not found
1969-12-31 19:00:32 (none) dropbear[761]: Not backgrounding
1969-12-31 19:00:32 (none) kernel: [   32.470000] 8021q: adding VLAN 0 to HW filter on device eth0
1969-12-31 19:00:32 (none) netifd: Interface 'lan' is enabled
1969-12-31 19:00:32 (none) netifd: Interface 'loopback' is enabled
1969-12-31 19:00:32 (none) netifd: Interface 'loopback' is setting up now
1969-12-31 19:00:32 (none) netifd: Interface 'loopback' is now up
1969-12-31 19:00:32 (none) netifd: Network device 'eth0' link is up
1969-12-31 19:00:32 (none) netifd: Interface 'lan' has link connectivity
1969-12-31 19:00:32 (none) netifd: Interface 'lan' is setting up now
1969-12-31 19:00:32 (none) netifd: Network device 'lo' link is up
1969-12-31 19:00:32 (none) netifd: Interface 'loopback' has link connectivity
1969-12-31 19:00:32 (none) netifd: lan (804): udhcpc (v1.22.1) started
1969-12-31 19:00:32 (none) syslog: ubnt-waitclock: start
1969-12-31 19:00:32 (none) ubnt-waitclock: start
1969-12-31 19:00:32 (none) syslog: ubnt-waitclock: spawned
1969-12-31 19:00:32 (none) ubnt-waitclock: spawned
1969-12-31 19:00:32 (none) netifd: lan (804): dhcp.script
1969-12-31 19:00:32 (none) dhcp.script[805]: [FALLBACK] Interface: eth0, IP: 192.168.10.20, Netmask: 255.255.255.0
1969-12-31 19:00:32 (none) syslog: ubntbox: start
1969-12-31 19:00:32 (none) ubntbox: start
1969-12-31 19:00:32 (none) ubnt-waitclock: waiting 268 more seconds for clock
1969-12-31 19:00:32 (none) syslog: ubntbox: spawned
1969-12-31 19:00:32 (none) netifd: Interface 'lan' is now up
1969-12-31 19:00:32 (none) ubntbox: spawned
1969-12-31 19:00:32 (none) netifd: lan (804): Sending discover...
1969-12-31 19:00:33 (none) firewall: Reloading firewall due to ifup of lan (eth0)
1969-12-31 19:00:33 (none) ubnt-init: ubnt-init running
1969-12-31 19:00:33 (none) syslog: ubnt-init: ubnt-init running
1969-12-31 19:00:33 (none) syslog: module is already loaded - ubnt-platform
1969-12-31 19:00:33 (none) syslog: kmod: module is already loaded - ubnt-platform
1969-12-31 19:00:33 (none) syslog: op: 00600e01 val: 000a8580
1969-12-31 19:00:33 (none) syslog: op: 06000e01 val: fffeffff
1969-12-31 19:00:33 (none) syslog: op: 06400e01 val: fff7ffff
1969-12-31 19:00:33 (none) syslog: op: 06300e01 val: 00004000
1969-12-31 19:00:33 (none) syslog: ubnt-init: Indicating firmware image stable
1969-12-31 19:00:33 (none) ubnt-init: Indicating firmware image stable
1969-12-31 19:00:33 (none) syslog: op: 01200e01 val: 00000000
1969-12-31 19:00:33 (none) syslog: op: 01240e01 val: 00002710
1969-12-31 19:00:33 (none) syslog: op: 01200e01 val: 75300090
1969-12-31 19:00:33 (none) syslog: {
1969-12-31 19:00:33 (none) syslog:  "gateway_led": "ok"
1969-12-31 19:00:33 (none) syslog: }
1969-12-31 19:00:33 (none) syslog: {
1969-12-31 19:00:33 (none) syslog:  "lan_led": "ok"
1969-12-31 19:00:33 (none) syslog: }
1969-12-31 19:00:33 (none) syslog: ubnt-init: ubnt-init done
1969-12-31 19:00:33 (none) ubnt-init: ubnt-init done
1969-12-31 19:00:33 (none) syslog: solar_agent-bootloader: start
1969-12-31 19:00:33 (none) solar_agent-bootloader: start
1969-12-31 19:00:33 (none) netifd: lan (804): Sending select for 192.168.108.26...
1969-12-31 19:00:33 (none) solar_agent: start
1969-12-31 19:00:33 (none) syslog: sunstatsd: spawning sunstatsd
1969-12-31 19:00:33 (none) sunstatsd: spawning sunstatsd
1969-12-31 19:00:33 (none) solar_agent: spawning solar_agent
1969-12-31 19:00:33 (none) solar_agent: spawned
1969-12-31 19:00:33 (none) syslog: sunstatsd: spawned
1969-12-31 19:00:33 (none) sunstatsd: spawned
1969-12-31 19:00:34 (none) netifd: lan (804): Lease of 192.168.108.26 obtained, lease time 6739
1969-12-31 19:00:34 (none) syslog: mknod: /dev/flash0: File exists
1969-12-31 19:00:34 (none) syslog: kmod: module is already loaded - ubnt-platform
1969-12-31 19:00:34 (none) syslog: module is already loaded - ubnt-platform
1969-12-31 19:00:34 (none) netifd: Interface 'lan' has lost the connection
1969-12-31 19:00:34 (none) syslog: - init complete -
1969-12-31 19:00:34 (none) netifd: Interface 'lan' is now up
1969-12-31 19:00:34 (none) netifd: lan (804): dhcp.script
1969-12-31 19:00:34 (none) dhcp.script[979]: [DHCP] Interface: eth0, IP: 192.168.108.26, Netmask: 255.255.255.0, Gateway: 192.168.108.1, DNS: 8.8.4.4
1969-12-31 19:00:34 (none) netifd: lan (804): udhcpc.user: kick solar_agent
1969-12-31 19:00:34 (none) firewall: Reloading firewall due to ifup of lan (eth0)
1969-12-31 19:00:36 localhost INFO] sunstatsd: not configured to run. sleeping forever.
1969-12-31 19:00:38 (none) ubnt-waitclock: waiting 263 more seconds for clock
1969-12-31 19:00:44 (none) ubnt-waitclock: waiting 257 more seconds for clock
1969-12-31 19:00:44 localhost INFO] logging to syslog
1969-12-31 19:00:44 localhost INFO] Wed Dec 31 19:00:44 1969: solar_agent starting, cwd="/"
1969-12-31 19:00:45 localhost INFO] new CloudSupervisor(): gateway_fw_version 0.9.41
2017-12-08 10:43:44 (none) -- MARK --
2017-12-08 10:43:44 localhost INFO] connecting to ble_daemon ws://127.0.0.1:11111/
2017-12-08 10:43:44 localhost INFO] connected to ble_daemon.
2017-12-08 10:43:45 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:43:45 localhost INFO] EthernetLinkMonitor: link is UP
2017-12-08 10:43:47 localhost INFO] disable_during_update=0
2017-12-08 10:43:47 (none) ubnt-waitclock: time is set
2017-12-08 10:43:48 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:43:52 localhost INFO] disable_during_update=0
2017-12-08 10:43:52 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:43:54 localhost INFO] disable_during_update=0
2017-12-08 10:43:59 localhost INFO] disable_during_update=0
2017-12-08 10:44:00 (none) crond[742]: time disparity of 25212463 minutes detected
2017-12-08 10:44:01 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:44:03 localhost INFO] disable_during_update=0
2017-12-08 10:44:15 localhost INFO] disable_during_update=0
2017-12-08 10:44:17 localhost INFO] disable_during_update=0
2017-12-08 10:44:18 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:44:24 localhost INFO] disable_during_update=0
2017-12-08 10:44:44 localhost INFO] disable_during_update=0
2017-12-08 10:44:51 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:45:55 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-08 10:46:06 (none) kernel: [  187.180000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
2017-12-08 10:46:28 (none) user[8225]: using_default_creds
2017-12-08 10:46:32 (none) user[8428]: using_default_creds
2017-12-08 10:46:50 (none) user[9265]: using_default_creds

Ubiquiti Employee
Posts: 140
Registered: ‎01-10-2016
Kudos: 59
Solutions: 5

Re: I need to know how to get this working again.

@timbeasley

For your convenience, I am getting all the required information for your site to come back to monitoring system. 

Will be reaching you in a couple of hours.

 

Regards,

UBNT-Carlos

New Member
Posts: 19
Registered: ‎09-18-2017

Re: I need to know how to get this working again.

Hello, thank you for that. I went onsite today and I could ping google from ssh.

I also added the corrected 9th panel that you provided.

I browsed to the gateway as well and I re uploaded the firmware and rebooted.

 

 

New Member
Posts: 19
Registered: ‎09-18-2017

Re: I need to know how to get this working again.

does this mean the solar gateway is broken?

 

can you tell from the logs if it is in fact actually connecting in any way to the server?

 

I suppose I could go tether it to my phone and see if it can connect.

 

rather than pinging google is there something I can connect to  using my computer

or pinging ssh from the gateway that would confirm that a connection attempt from the network to the

"correct" server / port could succeed.

 

New Member
Posts: 19
Registered: ‎09-18-2017

Re: I need to know how to get this working again.

Please help . There must be a next step form the technical perspective before the client starts seeking steps from the legal one. This is a cogeneratro product and there is no indication as to its status for th customer and it is connected to his home where his family sleeeps.

 

There must be a next step here.

Senior Member
Posts: 3,723
Registered: ‎12-21-2013
Kudos: 1033
Solutions: 83

Re: I need to know how to get this working again.

[ Edited ]

@UBNT-Carlos@Andrejsnot quite sure what to think of this project/product anymore...

 

@timbeasleyno, your gateway is not broken. Their cloud is broken (again).

I'm also affected btw.

 

2017-12-30 14:39:31 localhost INFO] got hangup signal 1
2017-12-30 14:39:31 localhost INFO] solar_agent: restarting cloud connection...
2017-12-30 14:39:31 (none) firewall: Reloading firewall due to ifup of lan (eth0)
2017-12-30 14:39:32 localhost INFO] EthernetLinkMonitor: link is UP
2017-12-30 14:39:32 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:39:35 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:39:40 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:39:50 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:40:07 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:40:40 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:41:45 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:43:55 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:48:12 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:56:45 localhost ERROR] Cloud connect failed: 'http_x_ubnt_device_id'
2017-12-30 14:59:30 localhost INFO] No samples in 1200 seconds -- rotating stash K_J_V= log

Site id: 70e8f7ad-2ef4-4a32-b5fa-6b66fcfd66d3

When you receive a solution to your question/issue, don't forget to mark your thread as solved and to give kudos to the people who have helped you out!

Senior Member
Posts: 3,723
Registered: ‎12-21-2013
Kudos: 1033
Solutions: 83

Re: I need to know how to get this working again.


timbeasley wrote:

Please help . There must be a next step form the technical perspective before the client starts seeking steps from the legal one. This is a cogeneratro product and there is no indication as to its status for th customer and it is connected to his home where his family sleeeps.


What? The monitoring does not work, I assume that's all. Power generation should be working just fine, as long as it has been configured initially, which it seems like you managed to do.

 

I would however not rely on SunMAX Cloud anymore. I had high hopes when Robert (UBNT CEO) said the team got a new team leader (Andrejs), but as of right now I can not see that anything changed since then. It can't be all that hard though and if it really is all that hard, a little transparency would be very much appreciated. Maybe there are even things some of us could help the team with.

 

So, I would switch to local monitoring instead, by simply upgrading the SolarGW to a 1.X.X+ firmware (1.0.7 is the most recent one at the moment IMHO). There you do not depend on the cloud connection, because everything is on the gateway itself. Everything below 1.0.0 (like 0.9.X) is still using the cloud infrastructure.

 

I do it this way too, or I have both to be precise (on two independent gateways obviously). The cloud interface does look a lot more beautiful, but the local version show's all the data there is, that is not shown when using the cloud (like temperature etc.) and is a lot more stable.

When you receive a solution to your question/issue, don't forget to mark your thread as solved and to give kudos to the people who have helped you out!

New Member
Posts: 19
Registered: ‎09-18-2017

Re: I need to know how to get this working again.

I appreciate the input. I am old school prior military. All of our chemical and rotoray generators had indicators of their status and all were considered dangerous. So i'm just accustomed to that.

 

This also isn't really something I'm involved in much anywmore.

 

However concerning the local monitoring. I wonder if you would share your expertise with me.

 

 In the interest of just knowing what to expect (in the event my stuff is broken)

 

With the newer formware, what are the basic steps after upgrading the firmware. do I register panels etc. and what should I expect to do or see if mine is working correctly.

New Member
Posts: 19
Registered: ‎09-18-2017

Re: I need to know how to get this working again.

I appreciate the input. I am old school prior military. All of our chemical and rotoray generators had indicators of their status and all were considered dangerous. So i'm just accustomed to that.

 

This also isn't really something I'm involved in much anywmore.

 

However concerning the local monitoring. I wonder if you would share your expertise with me.

 

 In the interest of just knowing what to expect (in the event my stuff is broken)

 

With the newer firmware, what are the basic steps after upgrading the firmware. do I register panels etc. and what should I expect to do or see if mine is working correctly.

Ubiquiti Employee
Posts: 140
Registered: ‎01-10-2016
Kudos: 59
Solutions: 5

Re: I need to know how to get this working again.

Hi @timbeasley:

 

My apologies, I returned from vacation, you may know that I was actively helping with debuging before taking the days-off providing you with steps, re-sharing qr-codes in the PMs. Please allow me to analyze the data you provided last week to work on the issue.

 

In case you want to use the local monitoring instead of cloud, here is my previous post regarding it:

https://community.ubnt.com/t5/SunMAX/Local-SolarGateway-Change-Log-and-download-link/m-p/2059902#M28...

 

Thank you,

UBNT-Carlos

Ubiquiti Employee
Posts: 139
Registered: ‎09-05-2017
Kudos: 115
Solutions: 4

Re: I need to know how to get this working again.

Hi all, 

 

our  apologies, seems that SunMax cloud is suffering some issues again. 

Our team is working on restoring it, at this exact moment.

 

 

BR,

Andrejs

Ubiquiti Employee
Posts: 139
Registered: ‎09-05-2017
Kudos: 115
Solutions: 4

Re: I need to know how to get this working again.

Hi all, 

 

the cloud service has been restored and it is online. 

 

Sorry for inconvenience!

 

 

BR,

Andrejs

Ubiquiti Employee
Posts: 140
Registered: ‎01-10-2016
Kudos: 59
Solutions: 5

Re: I need to know how to get this working again.

@timbeasley:

 

After some work the cloud system is restored, I checked your site and the gateway reports heartbeat already.

 

All: 

Sorry for the inconvenience, please let us know if your site experiences any other issues.

 

Thank you for your patience.

UBNT-Carlos

 

Reply