Erudika / scoold-pro

Cloud-ready Q&A platform for the enterprise (self-hosted, on premise)
https://scoold.com
Other
7 stars 0 forks source link

Setup SSL #24

Closed jpascor-intellective closed 4 years ago

jpascor-intellective commented 4 years ago

How do I setup scoold to use my own wildcard ssl certificate?

albogdano commented 4 years ago

This is explained in the README

The easiest way is to setup a proxy like nginx or Apache.

On Tue, 11 Feb 2020, 02:55 jpascor, notifications@github.com wrote:

How do I setup scoold to use my own wildcard ssl certificate?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Erudika/scoold-pro/issues/24?email_source=notifications&email_token=AACUV6L72VRG2UHSK3JYRBTRCHZRDA5CNFSM4KSYLKZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IMNOF3A, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACUV6PCPDW2K2T4JPNQ5CLRCHZRDANCNFSM4KSYLKZQ .

albogdano commented 4 years ago

Follow this guide

jpascor-intellective commented 4 years ago

just getting back to this, I've followed the guide but the redirect just lands me back to the default nginx page, it fails to redirect it to scold instance on port 8000

albogdano commented 4 years ago

@jpascor Check you nginx configuration and remove all lines containing root /var/www/html; I recommend you don't edit /etc/nginx/nginx.conf but edit the file /etc/nginx/sites-available/default and replace all its content with the example configuration. You must modify that configuration to match your domain and certificate locations - don't expect it to just work!

jpascor-intellective commented 4 years ago

I've attached the file in /var/www/html/index.nginx-debian.html, you're saying to delete the contents of this file? index.nginx-debian.txt

I've also attached the nginx.conf and default file, can you tell me what I'm mising? default.txt

albogdano commented 4 years ago

I wasn't talking about any HTML files. After you edit the nginx configuration, reload it with systemctl reload nginx and watch the system logs for errors. This line is wrong: proxy_pass http://scoold.intellective.com:8000; it should be proxy_pass http://127.0.0.1:8000;

jpascor-intellective commented 4 years ago

I made the corrections, my site still does not load on port 443 with the following message: "Error code: SSL_ERROR_RX_RECORD_TOO_LONG"

albogdano commented 4 years ago

I can't help you with that error - try searching Stack Overflow for a solution.

jpascor-intellective commented 4 years ago

I'm also getting this warning message, any suggestions? 2020/02/19 16:34:59 [warn] 4421#4421: conflicting server name "scoold.intellective.com" on 0.0.0.0:80, ignored

albogdano commented 4 years ago

Have a look at the example configuration here and notice the differences: https://github.com/Erudika/scoold#self-hosting-para-and-scoold-through-ssl

You can't combine port 80 rules with port 443 rules under the same server {} section. This is the last comment from me on this issue.