> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/basespace/microarray/troubleshoot-iscan.md).

# Troubleshoot iScan Integration

The firewall protects the iScan control computer by filtering incoming traffic to remove potential threats. The firewall is enabled by default to block all inbound connections. Keep the firewall enabled and allow outbound connections.

For the instrument to connect to BaseSpace Sequence Hub, you will need to add regional platform endpoints and instrument specific endpoints to the allow list on your firewall. Regional endpoints and further detail can be found in [Security and Networking for Illumina instrument control computers](https://support-docs.illumina.com/SHARE/NetworkSecurity/Content/SHARE/FrontPages/NetworkingSecurity.htm).

The following table shows the applicable endpoints for the iScan.

<table><thead><tr><th width="290.3333333333333">Endpoint</th><th width="165">Category</th><th>Purpose</th></tr></thead><tbody><tr><td>ica.illumina.com</td><td>Required</td><td>Send IDAT files to ICA</td></tr><tr><td>o.ss2.us</td><td>Required</td><td>Certificate authorization</td></tr><tr><td>ocsp.digicert.com</td><td>Required</td><td>Certificate authorization</td></tr><tr><td>ocsp.pki.goog/gsr2</td><td>Required</td><td>Certificate authorization</td></tr><tr><td>ocsp.rootca1.amazontrust.com</td><td>Required</td><td>Certificate authorization</td></tr><tr><td>ocsp.rootg2.amazontrust.com</td><td>Required</td><td>Certificate authorization</td></tr><tr><td>ocsp.sca1b.amazontrust.com</td><td>Required</td><td>Certificate authorization</td></tr><tr><td>fonts.gstatic.com</td><td>Required</td><td>Display fonts</td></tr><tr><td>fonts.googleapis.com</td><td>Recommended</td><td>Display fonts</td></tr><tr><td>cdn.walkme.com</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>cdn3.userzoom.com</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>dpm.demdex.net</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>illuminainc.demdex.net</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>illuminainc.tt.omtrdc.net</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>smetrics.illumina.com</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>google.com</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>google-analytics.com</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>stats.g.doubleclick.net</td><td>Recommended</td><td>Telemetry</td></tr><tr><td>illumina.com</td><td>Optional</td><td>Access Illumina support material</td></tr></tbody></table>

## IDAT Fail Status

iScan will mark certain samples with a FAIL status if the registration quality is too poor for that particular section. Selected samples that are marked with FAIL status will be excluded from analysis and there would be no results for that sample, even though IDATs are generated. These samples will not be available for selection through beadChip table or samplesheet upload when launching analysis.

The registration quality can be found in the `metrics.txt` file. More information on that file can be found in the [iScan documentation](https://support-docs.illumina.com/ARR/iScan/Content/ARR/iScan/ScanMetrics_fIS.htm).


---

# 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://help.bioinsight.illumina.com/basespace/microarray/troubleshoot-iscan.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.