This site can't be reached

I’ve been using Cosmos for months and today when I click on the icon the browser opens and I get a message saying the site can’t be reached. Is there a problem with the server, I haven’t changed anything that would account for this.

Hi devin,
It might have been a temporary glitch in your connection.
If that is not the case and the problem persists, please to our support the Cosmos log file (cb.log), which can be seen here: C:\Program Files\Common Files\ChaosGroup\ChaosCosmos
Here is how to reach support: https://www.chaosgroup.com/help/contact

Regards,

Today, after installing update, Cosmos Browser stopped working. This is EXTREMELY ANNOYING.
I can’t see Chaos Cosmos Browser service so I can’t restart it.
Maybe name of this service was changed?

I can’t reinstall Cosmos Browser because “There is a newer or equal version already installed”.
I can’t unistall existing version because I get message that system can’t find “C:\Program Files\Chaos Group\Chaos Cosmos/uninstall/installer.exe.”
What should I do?
Why Cosmos updates make it unusable?

Hi Mnietek2707,
I am sorry to hear that you experience problems with the latest update.
Please, try to start Cosmos by going to the Windows Start Menu and typing in “Start Chaos Cosmos Browser” (screenshot attached)

If the above doesn’t work, we will need your help to diagnose the problem. Please, send us the cb.log file. It can be found in directory: C:\Program Files\Common Files\ChaosGroup\ChaosCosmos

Send it to our support here: https://www.chaosgroup.com/help/contact
And provide reference to this forum thread.

Thanks and sorry for the inconvenience.

I realised that antivirus doesn’t like some files from this update.

But why???

Couldn’t get it to start either.

  1. go to C:\Program Files\Common Files\ChaosGroup\
  2. Set the ChaosChosmos folder permissions to Everyone Read\Write
  3. Then go to Services \ Chaos Cosmos Browser Service and set it to Automatic Start and start it.

Not sure why the permissions on that folder were extremely restrictive but nobody could write to it and the logs were failing.