Collaboratory 1 shutdown (2021-09-02)
Collaboratory 1 is shutting down Wednesday September 8th. As such, please ensure you have migrated your data to Collaboratory 2. You can view our handy guide on what data is migrated by our tools, as well as what is not covered by the semi-automated tools.
If you follow the above links, you will also find recorded migrathons, where you can find a lot of information to help you migrate your data. If you encounter any issues or problems while migrating your data, please contact EBRAINS support and we will get back to you as soon as possible.
Openshift issues (2021-07-09) (Resolved)
The Openshift service has gone down. As the Collaboratory Lab and the Image service both rely on this service, they are currently unavailable. We are investigating this issue and it will be resolved as soon as possible. We apologise for any inconvenience caused.
UPDATE 2021-07-12: The issue seems to be with the Openstack servers. It is also affecting a few more VMs aside from the Openshift service. The infrastructure team is looking into it.
UPDATE 2021-07-12: The Openstack issue has been fixed. Services should be back up and running. Thank you for your patience.
Collaboratory Lab restart (2021-06-15)
The Collaboratory lab will be restarted for the purpose of changing a few background configurations.
Collaboratory User Group (UG) meeting
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
If you would like to see new features or feel certain functionality is required to improve the Collaboratory, please join the Collaboratory user group, once joined, please do not hesitate to make your suggestions.
Drive issue (Resolved 2021-06-14)
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.
We apologise for any inconvenience this causes.
Drive issue (Solved)
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.
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.
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.
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.
This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding.
We apologise for any inconvenience this has caused
OnlyOffice license issue (Resolved)
We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image:
.
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.
SSL certificates (2020-12-04) (Resolved)
Our SSL Certificate provider (Let's Encrypt) has been using new certificates to sign our SSL certificates as described on their website. 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.
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.
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.
Files locked in the Drive (2020-09-30) (Resolved)
A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.
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.
We are actively trying to correct the problem as promptly as possible.
The temporary workaround
When you open a file in OnlyOffice:
- check if other users are editing the same file. The count appears at the top right corner.
- perform a trivial edit and save
- if you are the only user with that file open, you can trust the presence/absence of a warning message from OnlyOffice
- if multiple users have the file open simultaneously, you can:
- choose to trust the first user who opened it to have checked, or
- check in the Drive the timestamp of the file that you just saved
OnlyOffice will notify you when you try to save a file and the save fails. If that happens:
- read the message
- use File > Download as ... > docx or pptx or xlsx to save the file to your computer
- close OnlyOffice. DO NOT KEEP LOCKED FILES OPEN IN ONLYOFFICE. It would mislead others.
- rename the file by adding _UNLOCKED at the end of the filename, before the extension
- upload the file with its new name
- work on this new file
We apologize for the inconvenience and thank you for your understanding.
The Collaboratory team