# Troubleshoot ## Invalid CSR - certificate with such Subject name already exists If you are getting the error below, that means, you need to use another "CN" variable when you order certificate. Each "CN" must be different from the previous ones you used. One suggestion is to add a unique numeric at the end of "CN." ``` ERROR (src/main.c:837) Order failed - {"type":"urn:ietf:params:acme:error:badCSR","detail":"Invalid CSR - certificate with such Subject name already exists"} ``` ## Invalid SPC - Failed to download certificate This error means that the IP you are using now to interact with iConnectiv API, either by calling iConnectiv API directly or by using Peeringhub's ACME client, is not whitelisted in iConnectiv. You need to check if your IP is specified in Access Request Form. ``` ERROR (src/main.c:805) Challenge submission failed - {"type":"urn:ietf:params:acme:error:incorrectResponse","detail":"Invalid SPC - Failed to download certificate from 'https://authenticate-api.iconnectiv.com/download/v1/certificae/certificateId_161324.crt'"} ``` The Access Request Form looks like the following: ![](/files/9QynLHqGdfMCOEzJHjfy) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://doc.peeringhub.io/guides/troubleshoot.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.