Skip to content

Commit 736c5b9

Browse files
joshtrichardskesselb
authored andcommitted
refactor: Move contacts troubleshooting entry to existing section
Moved the lone Contacts entry in the general troubleshooting chapter over to the existing Troubleshooting section that already exists within the Groupware chapter. Minor correcting of phrasing, formatting, and grammar. Signed-off-by: Josh <josh.t.richards@gmail.com>
1 parent 02268f7 commit 736c5b9

1 file changed

Lines changed: 32 additions & 21 deletions

File tree

admin_manual/groupware/troubleshooting.rst

Lines changed: 32 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -5,60 +5,72 @@ Troubleshooting
55
===============
66

77
Calendar
8-
########
8+
--------
99

1010
Missing Shared Calendars
11-
************************
11+
^^^^^^^^^^^^^^^^^^^^^^^^
1212

1313
**Problem:**
14-
User should have access to a shared calendar, but the calendar is not displayed in Nextcloud Calendar or other CalDAV clients (e.g., DAVx⁵ or Thunderbird).
14+
A user should have access to a shared calendar, but the calendar is not displayed in Nextcloud Calendar or other CalDAV clients (e.g., DAVx⁵ or Thunderbird).
1515

1616
**Affected Versions:**
1717
- Nextcloud Server 31.0.5 and below
1818
- Nextcloud Server 30.0.11 and below
1919

2020
**Possible Reason:**
21-
A bug in previous versions of Nextcloud Server could mistakenly add a calendar unshare instead of removing the share permission. For example, a user has read access through a group membership, and the owner grants permission to a single user to modify a calendar. When removing the modify permission again, the unshare record was created.
21+
A bug in previous versions of Nextcloud Server could mistakenly add a calendar unshare instead of removing the share permission. For example, a user has read access through a group membership, and the owner grants permission to a single user to modify a calendar. When the modify permission is removed, an unshare record is incorrectly created.
2222

2323
**Troubleshooting Steps:**
2424

2525
1. **Check for Hidden Calendars:**
26-
It's possible for a user to hide a calendar. Please check in Nextcloud Calendar if the missing calendar is listed in the "hidden" section. If the missing calendar is listed there, check the box in front of the calendar to enable it again.
26+
Its possible for a user to hide a calendar. Please check in Nextcloud Calendar if the missing calendar is listed in the "hidden" section. If it is, check the box in front of the calendar to enable it again.
2727

2828
2. **List Calendar Shares:**
29-
Run the command ``occ dav:list-calendar-shares <uid>`` to list all shares for a user. Look for lines with the Calendar URI/Calendar Name of the missing calendar and Permissions = Unshare. If there's such a line, but the user should have access, you have three options:
29+
Run the command ``occ dav:list-calendar-shares <uid>`` to list all shares for a user. Look for lines with the Calendar URI/Calendar Name of the missing calendar and Permissions = Unshare. If such a line exists, but the user should have access, you have three options:
3030

3131
A. **Create a User Share and Remove It Again:**
3232
In most cases, sharing the calendar with the user again (as an individual/user share) will correct the state in the database.
3333

3434
B. **Remove All Calendar Unshares for a User:**
35-
``occ dav:clear-calendar-unshares <uid>``.
35+
Run ``occ dav:clear-calendar-unshares <uid>``.
3636

3737
C. **Delete Specific Unshares:**
38-
Some users may have many calendar unshares, so it might be easier to delete only the unwanted unshare. The ``Share Id`` references the id of a row in the ``oc_dav_shares`` database table. Delete the row with the matching id to remove the unshare.
38+
Some users may have many calendar unshares, so it might be easier to delete only the unwanted unshare. The ``Share Id`` refers to the ID of a row in the ``oc_dav_shares`` database table. Delete the row with the matching ID to remove the unshare.
3939

40-
**Why Isn't there an Automated Migration to Correct the Problem?**
41-
Unsharing a calendar is a feature, and with the given information, we cannot determine if a calendar was unshared on purpose or as a result of the bug.
40+
**Why isn't there an automated migration to correct the problem?**
41+
Unsharing a calendar is a feature, and with the given information, we cannot determine if a calendar was unshared intentionally or as a result of the bug.
42+
43+
Contacts
44+
--------
45+
46+
Unable to update contacts or events
47+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
48+
49+
If you get an error like:
50+
51+
``PATCH https://example.com/remote.php/dav HTTP/1.0 501 Not Implemented``
52+
53+
it is likely because of a misconfigured web server. Please refer to :ref:`trouble-webdav-label` for troubleshooting steps.
4254

4355
Mail
44-
####
56+
----
4557

4658
Autoconfig for your mail domain fails
47-
*************************************
59+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4860

4961
If autoconfiguration for your domain fails, you can create an autoconfig file and place it as ``https://autoconfig.yourdomain.tld/mail/config-v1.1.xml``. For more information please refer to `Mozilla's documentation <https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat>`_.
5062

5163

5264
Database insert problems on MySQL
53-
*********************************
65+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5466

5567
If the mail app fails to insert new rows for messages (`oc_mail_messages`), recipients (`oc_mail_recipients`) or similar tables, you are possibly not using the 4 byte support.
5668

5769
See :doc:`../configuration_database/mysql_4byte_support` for how to update your database configuration.
5870

5971

6072
Export threading data
61-
*********************
73+
^^^^^^^^^^^^^^^^^^^^^
6274

6375
If you encounter an issue with threading, e.g. messages that belong to the same conversation thread don't show up as one, you can export the data the algorithm will use to build threads. We are dealing with sensitive data here, but the command will optionally redact the data with the ``--redact`` switch. The exported data will then only keep the original database IDs, the rest of the data is randomized. This format does not the export message details, it still contains metadata about how many messages you have and how they relate. Please consider this before posting the data online.
6476

@@ -118,7 +130,7 @@ It's recommended practice to pipe the export into a file, which you can later sh
118130
.. _mail_get_account_ids_groupware:
119131

120132
Get account IDs
121-
***************
133+
^^^^^^^^^^^^^^^
122134

123135
For many troubleshooting instructions you need to know the `id` of a mail account. You can acquire this through the database, but it's also possible to utilize the account export command of :doc:`occ <../occ_command>` if you know the UID of the user utilizing the mail account::
124136

@@ -138,14 +150,13 @@ In this example, ``1393`` is the `account ID`.
138150

139151

140152
Issues connecting to Outlook.com
141-
********************************
153+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
142154

143155
If you can not access your Outlook.com account try to enable the `Two-Factor Verification <https://account.live.com/proofs/Manage>`_ and set up an `app password <https://account.live.com/proofs/AppPassword>`_, which you then use for the Nextcloud Mail app.
144156

145157

146158
Logging the IMAP/SMTP/Sieve connections
147-
***************************************
148-
159+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
149160
The Nextcloud Mail app offers an extensive logging system to make it easier identifying and tracking down bugs. As this may include sensitive data, be sure to remove or mask them before posting them publicly.
150161

151162
Per mail account
@@ -211,7 +222,7 @@ Once you've collected the necessary data, it's highly recommended to disable the
211222

212223

213224
Timeout and other connectivity issues
214-
*************************************
225+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
215226

216227
You can use OpenSSL to test and benchmark the connection from your nextcloud host to the IMAP/SMTP host.::
217228

@@ -235,7 +246,7 @@ The output should look similar to this::
235246

236247

237248
Manual account synchronization and threading
238-
********************************************
249+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
239250

240251
To troubleshoot synchronization or threading problems it's helpful to run the sync from the command line while the user does not use the web interface (reduces chances of a conflict)::
241252

@@ -278,4 +289,4 @@ The output will look similar to this::
278289
[debug] Threading 19417 messages took 1s
279290
[debug] Account 1393 has 9839 threads
280291
[debug] Account 1393 has 0 messages with a new thread IDs
281-
62MB of memory used
292+
62MB of memory used

0 commit comments

Comments
 (0)