Announcement

Collapse
No announcement yet.

Outage on Comodo ONE, Comodo Dragon and Dragon Enterprise Platforms

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • pag347
    replied
    Same here. Is it me or am I just going crazy. Seems like I have a handful online and lots offline!

    Leave a comment:


  • Factor1123
    replied
    Same here. Things were back up and now offline again.

    Leave a comment:


  • kbovee
    replied
    Well guys I just lost all devices, all offline. Everything was back up and working. Now I'm hosed again.

    Comodo, when will this be resolved?!

    Leave a comment:


  • vsb2211
    replied
    About half of mine weren't showing online in Remote control. Bumping the ITSMService or a reboot fixed them all.

    Leave a comment:


  • Factor1123
    replied
    Similar boat for me. Only about 25% are showing online. Has anyone received an update on when this will be fully resolved?

    Leave a comment:


  • SCS-MR
    replied
    For the record, I have exited and re-logged into the Itarian Remote Control system. Only 25% are online. Weirdly, 3 have come online in the past few hours. I would expect closer to 75% to be online even accounting for the weekend. I have server nodes that are showing as offline and yet client nodes (for that server running the network and Internet Service) for those same clients are showing as online.

    What should be our protocol to get these resolved ASAP?

    I appreciate the status and updates, but I'm going to need better assurances and a clearer line of communication from Itarian support going forward. This CANNOT happen again.

    Leave a comment:


  • iBaum
    replied
    As of Sunday evening at 6:17pm, the majority of my endpoints are still offline. The ones that show online, are severely bouncing. I can only stay connected to them for a minute or two. What's the deal? Post #36 suggests that all endpoints should be properly connected as the day progresses. That was yesterday and we're still dealing with this tonight.


    ***EDIT UPDATE***

    It appears, at least so far, that a PC reboot is required in order to get the endpoints registered with ITarian again. Maybe this will help others.
    Last edited by iBaum; 02-28-2022, 02:02 AM.

    Leave a comment:


  • terrystuart
    replied
    Per the previous Comodo post (#32), we would like to provide additional information to this forum. As indicated in post #32, to correct the Endpoint Management (EM) issues we decided to move Availability Zones and this was completed late last evening. However, the set of servers we moved is a cluster of EM hosts and even though the move was completed as we mentioned, all the hosts in the cluster had not fully been configured, thus some users were still experiencing loss of connectivity late last evening. It took additional time to complete the cluster configurations and this lasted into early today (2/26).

    As of 9am US ET, all servers in the new cluster (new AZ) are up, running and servicing requests. We have performed internal and select customer testing confirming that systems previous inaccessible are now fully accessible. However, we should note that some environments may be still find access issues on select endpoints due to latency in connection timings . We do expect all tenants to be are properly connected as the day progresses.

    In addition, the move of availability zones within AWS resulted in additional server IP addresses which may need to be added to any firewall rule your environment currently has in place. Per the link below which covers FW rules for US customers:
    https://help.comodo.com/topic-399-1-786-12452-Appendix-1b---Endpoint-Manager-Services---IP-Nos,-Host-Names-and-Port-Details---US-Customers.html?af=3D9967


    If you have a FW rule in place allowing access to Windows push service (XMPP), the following IP addresses will need to be added to that access rule.
    54.86.128.208
    34.202.225.237

    Thank you

    Leave a comment:


  • airgap
    replied
    Please retry. I rechecked my devices and they connect just fine.
    Thank you

    Leave a comment:


  • eis
    replied
    Yah I've restarted it and still not all clients are up

    Leave a comment:


  • pag347
    replied
    This is not resolved. Still not working. About half of the agents that are online launch the connection screen then sit there in limbo between connecting and disconnecting.

    Leave a comment:


  • airgap
    replied
    Hello Everyone,
    While we have been working with AWS to resolve this issue, we in parallel opted to move to a different AWS availability zone in order to speed up the resolution process. This move has been completed and we now see the ITSM functions working. There will be some latency for some endpoints until all the tenants get caught up. This is to be expected while they are all connecting back in.
    You'll also recall that, all before, during and after this time, endpoints are still fully protected under the profile that is applied.
    As additional updates are available, you'll see them here.
    Thank you

    Leave a comment:


  • kbovee
    commented on 's reply
    Try closing Remote Control completely and open and sign back in

  • SCS-MR
    replied
    For the record, I'm still at majority of my endpoints offline. (Same number for the last few hours..)

    Leave a comment:


  • Rudym12
    replied
    We are back online.

    WE STILL NEED TO KNOW WHAT HAPPENED

    Leave a comment:

Working...
X