Subject: Support Request - TLS Verification Issue for Authlink
Hi, I am the owner of Authlink. I’ve been working on implementing a product whitelist for Roblox product that am working on.
I have encountered an issue related to TLS verification when integrating my API with my main URL. Specifically, after adding the required code to the page redirection, I am facing a TLS verification failed error. I must admit that I am not familiar with TLS, and I’m seeking your assistance to resolve this matter.
Here are my specific concerns and questions:
TLS Verification Error:
I am encountering a TLS verification failed error when connecting my API with my main URL. Could you please guide me on how to address this issue?
CSR (Certificate Signing Request):
I’ve heard about CSR (Certificate Signing Request), but I’m not sure how to generate one. Could you provide instructions on how to generate a CSR for my website?
Website Verification with TLS:
I would like to understand the process of making my website TLS-verified. What steps do I need to take to ensure that my website is properly verified with TLS?
I appreciate your assistance in helping me resolve these concerns.
While AI has its uses, please don’t use it here, or on any other support forum. It can (and does) hide your real message, and add in information that you don’t care about, giving the people who want to help you a harder job.
AI has its uses, but not here.
IF is not an API hosting providers, so that request is probably blocked by the server.
The free SSL tool does not require CSR as far as I’m aware (nor do I see it anywhere mentioned in the guide I linked you to), but yes, the company name you enter there is irrelevant.
If you use our Free SSL Certificates tool, you don’t need a CSR. A CSR is only used to obtain the SSL certificate, it’s not used to have SSL on your site. And our system generates all the necessary things for you and only gives you the data you need.
Also, the identification data in the CSR is mostly useless. Theoretically it can be used in the SSL certificate, but Domain Validated certificates discard the information, and Extended Validation do additional checks before using the data, and will probably ask you to submit those manually. So nobody really cares about what you put in the CSR.