The Trying to connect... error means Blissbook is having trouble retaining a connection to your computer. This connection is important as we do not want you to make edits that we cannot save.

If you are not having any other internet connection issues, the issue may be caused by something on your internal corporate network.

Blissbook uses something called Websocket to ping our users' connections to ensure that the actions they take in their browser (clicking things, typing, etc.) are actually trafficked to our servers and databases. If you make edits to a document without being connected, you will lose all those edits if you refresh or browse away from the page. That is super annoying, so Blissbook is constantly ensuring you are connected. Then, if you are not connected, Blissbook prevents you from making edits that won't be saved, thus preventing the super annoying situations where edits are lost or you click around and weird things happen.
​

The root cause of the issue here is that the Websocket connection from your browser(s) to the Blissbook server are constantly disconnecting & reconnecting. This is causing Blissbook to think that your browser is not connected to the Blissbook server. Blissbook shows the above error when the Websocket connection is broken.

The most likely culprit is a new/changed VPN setting or a firewall rule on the customer side that is blocking or disrupting Websocket traffic.

If this is a new issue, it's possible your IT group made a security update to your internal network that is blocking Websocket traffic.

To resolve the issue, contact your IT group and send them this help article. They will likely need to put Blissbook on an allow-list to fix the problem. Here is how one other customer solved it, with an explanation:

We use a proxy in our corporate network and generally proxy does not support web socket connection. Hence we had to disable SSL inspection on our proxy for this particular WebSocket URL.