Wiki source code of Announcements

Version 72.1 by hbpadmin on 2021/07/09 17:33
Show last authors
1 (% class="wikigeneratedid" %)
2 === **Openshift issues (09-07-2021)** ===
3
4 The openshift service has gone down. As the Collaboratory Lab and the Image service both rely on this service, they are currently investigating. We will resolve this as soon as possible. We apologise for any inconvenience caused.
5
6 === **Collaboratory Lab restart ( 15-06-2021)** ===
7
8 The Collaboratory lab will be restarted for the purpose of changing a few background configurations.
9
10 === **Collaboratory User Group (UG) meeting** ===
11
12 The UG meeting is a great way to stay informed about recent and upcoming changes to the Collaboratory as well as making your voice and ideas heard directly by the developers. If you are interested in attending this meeting, or know someone who is interested, please feel free[[ to join these meetings>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-user-group/Joining%20the%20group/]]
13
14 If you would like to see new features or feel certain functionality is required to improve the Collaboratory, please [[join the Collaboratory user group>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-user-group/Joining%20the%20group/]], once joined, please do not hesitate to [[make your suggestions>>https://drive.ebrains.eu/lib/aac38e36-4bd9-48ee-9ae6-b876a65028aa/file/Collaboratory%20User%20Group%20-%20Suggestion%20box.docx]].
15
16
17 === **Drive issue (Resolved 14-06-2021)** ===
18
19 There is currently an issue that prevents the Drive option from appearing in new collabs. Although you can still create new collabs and can access all of the other functionality provided, you will not have access to the Drive by default. You can request a Drive be manually added to your collab via support.
20 \\We apologise for any inconvenience this causes. 
21
22
23 === **Drive issue (Solved)** ===
24
25 Users have reported issues trying to access the drive. This is something we are aware of and trying to fix as soon as possible. This issue seems to be an Openshift problem.
26
27 Until this is resolved, users will have issues accessing any functionality that requires Drive access. This mainly concerns the Lab and to a less extant, any service that requires access to the drive.
28
29 **Potential fix: **We believe we have identified the issue and will be bringing the Lab service down for up to an hour at 10pm CEST on April 28th as we attempt to deploy this fix. All current Notebooks will be killed during this downtime. - Unfortunately this fix has not worked and we are looking at other solutions at the moment.
30
31 **Potential fix 2: **We have another small release that should fix the issue at 13:30 CEST Today. All currently running notebooks will be killed during this downtime.
32
33 This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding.
34
35 We apologise for any inconvenience this has caused
36
37 === OnlyOffice license issue (Resolved) ===
38
39 We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~:
40
41 [[image:1613726704318-340.png]].
42
43 We are working on this issue and will have it fixed as soon as possible, thank you for your patience and we apologise for any inconvenience caused.
44
45
46 === SSL certificates (2020-12-04) (Resolved) ===
47
48 Our SSL Certificate provider (Let's Encrypt) has been using new certificates to sign our SSL certificates as described on their [[website>>https://letsencrypt.org/certificates]]. This requires updates on our servers and on your web browsers. The updates on your web browsers often go unnoticed by the user but in some cases your browser may inform you that it needs to fetch a new certificate. You can accept this safely; most browsers don't even mention it to the user.
49
50 Note that this is not the same as accepting an exception in your browser because of a bad certificate. Accepting such exceptions can put your data and credentials at risk of a person-in-the-middle attack.
51
52 We believe we have addressed all the issues that may arise from this change in SSL certificates. If you experience any issue, especially when accessing EBRAINS APIs, don't hesitate to contact [[support>>https://ebrains.eu/support]].
53
54
55 === Files locked in the Drive (2020-09-30) (Resolved) ===
56
57 A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.
58
59 We are looking into this. At the time being, it seems that a small number of files are locked by the Drive which prevents OnlyOffice to update these files when they are edited online.
60
61 We are actively trying to correct the problem as promptly as possible.
62
63 ==== The temporary workaround ====
64
65 When you open a file in OnlyOffice:
66
67 1. check if other users are editing the same file. The count appears at the top right corner.
68 1. perform a trivial edit and save
69 1. if you are the only user with that file open, you can trust the presence/absence of a warning message from OnlyOffice
70 1. if multiple users have the file open simultaneously, you can:
71 11. choose to trust the first user who opened it to have checked, or
72 11. check in the Drive the timestamp of the file that you just saved
73
74 OnlyOffice will notify you when you try to save a file and the save fails. If that happens:
75
76 1. read the message
77 1. use File > Download as ... > docx or pptx or xlsx to save the file to your computer
78 1. close OnlyOffice. (% style="color:#e74c3c" %)**DO NOT KEEP LOCKED FILES OPEN IN ONLYOFFICE.**(%%) It would mislead others.
79 1. rename the file by adding (% style="color:#3498db" %)//**_UNLOCKED**//(%%) at the end of the filename, before the extension
80 1. upload the file with its new name
81 1. work on this new file
82
83 We apologize for the inconvenience and thank you for your understanding.
84
85 The Collaboratory team