# Ssl for experience **URL:** \ **Category:** Help\ **Tags:** experience, ssl\ **Created:** [February 24, 2019, 7:47pm UTC](https://forums.losant.com/t/ssl-for-experience/1553 "2019-02-24T19:47:05Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Lars\_Andersson](https://avatars.discourse-cdn.com/v4/letter/l/f05b48/32.png) [@Lars\_Andersson](https://forums.losant.com/u/Lars_Andersson)\ **Post date:** [February 24, 2019, 7:47pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/1 "2019-02-24T19:47:05Z")
When requesting a ssl cert to use for a domain experience, do I enter the “[subdomain.mydomain.com](http://subdomain.mydomain.com)” or the “[Losantslug.onlosant.com](http://Losantslug.onlosant.com)” value? I attempted using a PositiveSSL from Namecheap, but not having any luck activating it. ---
**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\ **Post date:** [February 24, 2019, 7:49pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/2 "2019-02-24T19:49:54Z")
Hi @Lars_Andersson, You’ll be configuring it for your domain ( `subdomain.mydomain.com` ). Here is where the info is on that: [https://docs.losant.com/experiences/domains/#securing-your-domain](https://docs.losant.com/experiences/domains/#securing-your-domain) ---
**Author:** ![Lars\_Andersson](https://avatars.discourse-cdn.com/v4/letter/l/f05b48/32.png) [@Lars\_Andersson](https://forums.losant.com/u/Lars_Andersson)\ **Post date:** [February 24, 2019, 7:58pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/3 "2019-02-24T19:58:14Z")
ok, that’s what I did but, but when generating the CSR I wasn’t sure what platform to specify so I used [https://decoder.link/csr\_generator](https://decoder.link/csr_generator) ---
**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\ **Post date:** [February 25, 2019, 3:43pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/4 "2019-02-25T15:43:31Z")
@Lars_Andersson Thanks for the info. Just confirming that you were able to get this working? ---
**Author:** ![Lars\_Andersson](https://avatars.discourse-cdn.com/v4/letter/l/f05b48/32.png) [@Lars\_Andersson](https://forums.losant.com/u/Lars_Andersson)\ **Post date:** [February 25, 2019, 4:42pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/5 "2019-02-25T16:42:04Z")
No I have not. Do I need to specify platform when creating my CSR? ---
**Author:** ![Alexander\_Kondrov](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/alexander_kondrov/32/1392_2.png) [@Alexander\_Kondrov](https://forums.losant.com/u/Alexander_Kondrov)\ **Post date:** [March 18, 2019, 4:00pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/6 "2019-03-18T16:00:44Z")
Hi Guys, the same question. I bought a Possitive SSL subscription from [namecheap.com](http://namecheap.com) as it was adviced in losant docs. Which platform should I specify when getting CSR. The suggested list looks like that: ![namecheap](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/f/f96fd0bfdae1d13e599738ac583c7c46c69a5172.png) Thanks ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [March 18, 2019, 4:27pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/7 "2019-03-18T16:27:03Z")
Hello! The correct web server is the Nginx option. I will add this to our documentation to make it more clear for other users. 😀 Thanks, Julia ---
**Author:** ![Alexander\_Kondrov](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/alexander_kondrov/32/1392_2.png) [@Alexander\_Kondrov](https://forums.losant.com/u/Alexander_Kondrov)\ **Post date:** [March 18, 2019, 4:37pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/8 "2019-03-18T16:37:02Z")
Hi Julia, thank you for the promt reply. I moved one step forward and there is an instruction to generate CSR from the server using openssl: [https://www.namecheap.com/support/knowledgebase/article.aspx/9446/14/generating-csr-on-apache–opensslmodsslnginx–heroku](https://www.namecheap.com/support/knowledgebase/article.aspx/9446/14/generating-csr-on-apache--opensslmodsslnginx--heroku) Sorry for a dummy question, but Losant Domains and Slugs section just has fields for entering SSL key, SSL Certificate, SSL Bundle inside of a domain name form. I don’t see a service/button/section to generate this request. Should I contact Losant to get this code? ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [March 19, 2019, 8:03pm UTC](https://forums.losant.com/t/ssl-for-experience/1553/9 "2019-03-19T20:03:53Z")
Hi @Alexander_Kondrov! Generating the CSR will happen in your terminal on the command line, and the key will be saved to your local computer. The [walkthrough](https://www.namecheap.com/support/knowledgebase/article.aspx/9446/14/generating-csr-on-apache--opensslmodsslnginx--heroku) on NameCheap has steps and terminal commands for generating the CSR and key. Once those are generated from the terminal commands, you can return to your Losant experience domain and insert the Key and Certificate values. Hopefully this helps, Julia ---
**Author:** ![Helly\_Nusinya](https://avatars.discourse-cdn.com/v4/letter/h/ecb155/32.png) [@Helly\_Nusinya](https://forums.losant.com/u/Helly_Nusinya)\ **Post date:** [May 20, 2025, 8:53am UTC](https://forums.losant.com/t/ssl-for-experience/1553/10 "2025-05-20T08:53:33Z")
When setting up SSL for a Losant Experience, request the [PositiveSSL certificate](https://certera.com/ssl/comodo/comodo-positive-ssl) for your custom domain (e.g., [subdomain.mydomain.com](http://subdomain.mydomain.com)), not the [onlosant.com](http://onlosant.com) URL. Upload the PositiveSSL cert, private key, and CA bundle in the Experience Domain settings to activate it properly.