Introduction :Describing Carbonio.

The entirely private digital workspace, Zextras Carbonio, includes the following:

Shareable across a domain include email, contacts, and calendaring essentials.
a full-featured mail server with antivirus and anti-spam software
Video and text conversations
File-management programme with group editing and document sharing

Carbonio’s advantages include:

concentrate on privacy and data sovereignty
simplicity of installation due to Linux packages’ out-of-the-box usability
comprehensive collection of collaboration and communication tools for businesses
Scalability: put up a single server, then quickly add more nodes as the infrastructure and demands of the business change.

Browser compatibility

A browser is required to access any Carbonio feature:

The Web GUI is accessible in these languages, and English is Carbonio’s primary language.

Contribution to the Documentation The documentation for Carbonio is now open source and posted in a public repository on Github.

Any type of documentation that is developed in accordance with the standards and is submitted as a pull request is welcome. Send an email to documentation@zextras.com if you have any ideas for the documentation or if you need help using Python Sphinx, the framework we use to write the documentation.

Seeking Assistance for Carbonio

In addition to this documentation, Zextras offers the following web sources:

How to file a problem report

The first priority is usually to fix any issues that come up when utilising a software so that you may resume your regular daily activities as soon as feasible.

As a result, the best manner to report a Carbonio issue is the one that enables the Technical Support Team and the Reporter to work together to achieve their objectives most quickly and effectively.

To accomplish this, first create a precise and thorough report outlining the problem encountered. Next, open a ticket on the Zextras customer support site and attach the report to the complaint. This enables the Technical Support Team to investigate the problem right away without requesting further details.

It may be necessary to do one or more of the following tasks while creating a thorough report:

to outline the procedures necessary to re-create the issue. This is the most crucial aspect since it would provide the Technical Support Team with a preliminary understanding of the potential source of the problem.
to put CLI commands into action
making screenshots
to do additional activities based on the reported problem, the associated modules, etc.

Prior to Opening a Ticket

To provide the Technical Support Team with the necessary information, you need obtain certain data and configuration variables from Carbonio and its components before opening a support ticket.

The retrieval of this data is the main topic of this section. Existing log files must be provided, as well as the results of several tasks and scripts (see the sections below) that must be run from the command line. Please take note that, unless otherwise stated:

Commands must be run on the node where the component is installed in Multi-Server deployments.
The directory /opt/zextras/log/ contains log files.

Common and general information

Every situation requires the broad and common information since it enables one to comprehend the context in which the problem was encountered. The output of each of the ensuing instructions has to be saved to a text file.
Enabling debug logging and attaching the produced log files to the ticket is another activity that helps the technical support team:
Run to boost the log verbosity on the mailbox server
duplicate the problem
Run to return the log verbosity to normal.

Once completed, attach the following log files:

the mailbox server’s mailbox.log file
The proxy node’s nginx.log and nginx.access.log files

Mobile Devices and Apps

Follow these instructions on a mobile device and email account, then attach the log files that were generated throughout the process.

Chats with Carbonio

Get the output of the following commands if you have issues with Carbonio Chats. Substitute JACK.SMITH@ACME.USE ONE AFFECTED ACCOUNT AS AN EXAMPLE. You may alternatively create a test account without Administrator rights and issue the same instructions from that account.

Add the following files to the ticket as well.

the mailbox.log file following a mailboxd restart with zmmailboxdctl restart

the last two days’ worth of the files mailbox.log, zmmailboxd.out, nginx.log, and nginx.access.log

Carbonio Documents

Provide this script’s output and the files /var/log/carbonio/files/files.log and /var/log/carbonio/docs-connector/docs-connector.log if there are any problems with Carbonio Files.

Advanced Carbonio

For Carbonio Advanced, you must also give details about Carbonio’s storage architecture (volumes, discs).

then, gather details on Carbonio Advanced’s settings.

Backup for Carbonio

Similar to Carbonio Advanced, discover the Backup Path and other setup after gathering a few environmental details:

Customer-side problems

If you encounter a client-side issue, use the steps below to get the necessary data:

Open a fresh Firefox or Chrome window
Open the Javascript Console by using the keys Ctrl + Shift + J on Windows, Linux, or OS X.
From the tab that the Javascript Console is now open, access the webmail.
Wait for the webmail to fully load.
duplicate the problem
Right-click anywhere in the Javascript Console’s Console pane, then choose Save As. to create a text file with the tab’s information in it
To save the contents of the Network tab as a text file, go to the Javascript Console and right-click anywhere. Then, choose Save as HAR with content.
Attach the ticket’s files including both the console export and the network export.