> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-troubleshooting-list/000007471.md).

# Troubleshooting a blank BaseSpace screen or The request timestamp is in the future during run setup

**Background**

To connect successfully to [BaseSpace Sequencing Hub](http://www.basespace.illumina.com/) (BSSH) during run setup, the date and time on the instrument computer need to match the local date and time. For Illumina Windows-based instruments (eg, iSeq 100, MiSeq, NextSeq 500/550, MiniSeq, and NovaSeq 6000), if the time reported on the instrument differs from the local time, a **"The request timestamp is in the future"** error or a **blank screen** might occur when trying to log into a BSSH account via the instrument control software (Figure 1). This article describes the step-by-step process for correcting the date/time on an instrument.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-3dd4a3439ea3edc61509817ad1bba0a34f152a19%2Fimage1.jpg?alt=media\&token=5f34341d-fec2-47d1-b626-07c3aeeb99f0)

Figure 1. A blank screen when trying to log into BSSH may occur is the local date and time on the instrument is incorrect.

**Correct the instrument date and time by following these steps:**

1. Log in as **sbsadmin** or any other account with administrator privileges.
2. Exit the instrument control software and navigate to the desktop.
3. Navigate to the Windows button on the bottom-left side of the desktop.
4. Start typing to search **Time** and select **Change the date and time** under the system settings.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-ea6bbaa86aef3c5d48a41e7a6b66318625519f63%2Fimage2.jpg?alt=media\&token=d0af41f0-b93f-43e9-9463-af114a7d7bdf)
5. Under **Current date and time**, navigate to **Set time zone automatically** and toggle this option to the **On** position.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-3aa58ed86befac471248a8996afb3a447336ba39%2Fimage3.jpg?alt=media\&token=c8607417-ae1a-4a01-9786-697809cb39ed)
6. Confirm that the instrument computer time is correct.
7. Open the control software again and repeat run setup.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-b841217d63570f450a6cd49e4b0f9ebe39b4d3fa%2Fimage4.jpg?alt=media\&token=cf096c9a-cf69-4d72-b613-f6022d6ea006)

**Note:** The instrument computer date/time can be corrected manually. This is not recommended as a long-term solution, because it does not account for daylight-savings.

If issues logging into BSSH through the control software persist, this might indicate that communication ports are blocked, or Illumina services are not running as expected. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7471), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007471%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/instrumentation/general/instrumentation-general-troubleshooting-list/000007471.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
