I can't log in to my workspace
The page Log in to your workspace takes you through the details of logging in to workspaces. Be it with TOTP (time-based-password) or using SSH.
How can I scale up my storage or my workspace's cores?
Sorry - you can't. You cannot extend storage or increase the number of cores on an existing workspace.
Instead, follow the best practices and make sure that you can re-create your working environment easily, whenever you need.
You can, however, attach and detach storage of a paused workspace. This way you could add a new, bigger disk, resume the workspace, copy the data, verify the copy, pause again and remove the older disk.
My workspace got deleted. Can you restore my workspace?
Research Cloud does not keep images of your workspace.
To be resilient in the case of unexpected events, follow the best practices.
That way, you make sure that your code and your configuration can be re-installed swiftly.
I accidentally deleted [...]. Can you restore it?
Research Cloud does not provide an automatic backup service. If something got deleted from storage, it is gone.
Make sure that your data is stored in more than one place. That way, you can respond to human and technical error.
How can I open (or close) ports?
Please refer to this documentation page to read up on networking ports.
Can I use the Research Cloud portal with any browser?
We test our portal with Firefox and Chrome. You may encounter unexpected behavior with other browsers.
SANE - Frequently Asked Questions
The following section covers the Frequently Asked Questions in regards to SANE
Why is there a 'SANE Service Account' in my SANE Collaboration in SRAM?
To simplify the onboarding process for Data Providers, SANE automatically creates the initial project setup in Research Cloud. This includes the required base workspaces and services, such as the Data Server and Data Provider Portal.
These resources are created by the “SANE Service Account”, a dedicated automation account used by SANE to perform setup and configuration tasks in Research Cloud. In order to create and manage these resources within your SRAM Collaboration, the service account must temporarily have the Developer role in the Collaboration.
The service account is only used for automated project provisioning tasks. After claiming the ownership (step 3.2) the SANE Service Account will be automatically removed within one day.
Why do I need to Claim Ownership of certain workspaces as a Data Provider?
The initial SANE project workspaces are automatically created by the SANE Service Account to reduce manual setup work for the Data Provider.
In Research Cloud, the account that creates a workspace automatically becomes its owner. As a result, the initially created SANE workspaces are owned by the SANE Service Account until ownership is transferred.
By using the “Claim Ownership” action, you transfer workspace ownership from the SANE Service Account to your own account. This ensures that the workspaces remain fully under your control and continue to function independently of the service account.
It is important to claim ownership of these workspaces. If the SANE Service Account is later removed from the Collaboration, Research Cloud may eventually delete workspaces that are still owned by that account, because their owner is no longer a member of the Collaboration. Research Cloud provides warnings before such deletion takes place.
Why can't I see the data folder in my Tinker SANE environment?
Try running through the following steps to resolve this issue:
- Check if the data server is running in the Research Cloud dashboard. If it's not, ask the data provider to resume it if you don't have the right to do so.
- Inside your Tinker SANE environment try to reconnect the data server. On the Desktop, you will find a "Reconnect SMB" icon. Double-click it to perform this action.
- Try to pause and resume your Tinker SANE environment, which results in a soft reboot of the machine.
- Contact the SURF Servicedesk for further help. Please include (a screenshot of) the contents of the file at location: C:\logs\windows-samba-client.log