BeagleIM tries to connected every X seconds (ie. delaying next retry if previous attempt fails). Due to that there is no point to notify user of an error which does not require user interaction, ie. failed TCP connection or the XMPP error that is possible to be fixed after another reconnection (this information is reported by XMPP protocol).

If there would be an error requiring user interaction, user would be notified.

If you wish to check XMPP protocol exchange for the account, please open Window menu while holding Option key and then and select XML Console and proper account. In newly opened window you will see the XML exchange for this account which happened since the window was opened (just wait to see new entries).

If no entries are visible, then most likely there is an issue with TCP connection or DNS SRV resolution.

The XML console is empty, because the client cannot establish a connection in the first place. The user is sitting in front of the client for a few days now, not knowing why it won't connect. Both the local network as well as the server are perfectly fine for XMPP connections, as other clients do not have issues with connecting.

If no entries are visible, then most likely there is an issue with TCP connection or DNS SRV resolution.

Yes, and I'm sure it's possible to enable and access debug logs for the connection, as e.g. seen in https://github.com/tigase/beagle-im/issues/40. (Please note, I am not an Apple user myself, just trying to help a person for whom Beagle suddenly stopped working. As the docs are silent on logging, and the log directory is empty, I mostly just need to know how to debug this.)

Logs gathered in issue #531 are printed to the standard output (terminal) when BeagleIM is launched from command line