Disable HTTPS on Discourse Clone?

(Keith Guerrette) #1

I have an absolute newbie question here - I’m currently running a successful discourse community using Digital Ocean. I’d like to clone my discourse community on digital ocean and setup a testing server so that I can fiddle with all of the new features and settings in discourse without concerning the live service. All of that is fine, where I’m getting stuck is the SSL (and I know very very little about ssl certification).

After I clone the site, entering it’s new ip in my browser causes me to go to the primary domain, which causes me to connect to the real server, not the testing clone. Do I just need to disable HTTPS on discourse so that I can browse my cloned server without concern? If so, how would I even get there to disable it?

Apologies in advance if this question is way off target. Is there a better way for me to approach this entirely?

(Jay Pfaffman) #2

Yeah. It’s complicated. The best thing to do is create a second domain name (e.g., testing.you.com) and install https for it too. And make sure that you have the new domain in the app.yml on the testing site.