"TLS (SSL) is not set up..." message still appears after setting up SSL

9 views
Skip to first unread message

Lupe Silva

unread,
Aug 27, 2017, 8:36:34 PM8/27/17
to Church.IO
Thanks for the instructions on setting SSL using Certbot and Let's Encrypt.  It made it simple, fast and free!!!!
After setting it up on my Digital Ocean drop, the https is working, but in the admin configuration screen, the message still appears saying it is not setup.  Did I miss something or can you direct me to shut off the message?  I can ignore it but when I have others use it, they will point it out.

Tim Morgan

unread,
Aug 27, 2017, 10:31:46 PM8/27/17
to Church.IO
Does your URL for OneBody say https:// on the front or just http:// ?



On Sun, Aug 27, 2017 at 7:36 PM Lupe Silva <lupe....@gmail.com> wrote:
Thanks for the instructions on setting SSL using Certbot and Let's Encrypt.  It made it simple, fast and free!!!!
After setting it up on my Digital Ocean drop, the https is working, but in the admin configuration screen, the message still appears saying it is not setup.  Did I miss something or can you direct me to shut off the message?  I can ignore it but when I have others use it, they will point it out.

--
https://church.io
https://github.com/churchio
http://chat.church.io
---
You received this message because you are subscribed to the Google Groups "Church.IO" group.
To unsubscribe from this group and stop receiving emails from it, send an email to churchio+u...@googlegroups.com.
To post to this group, send email to chur...@googlegroups.com.
Visit this group at https://groups.google.com/group/churchio.
For more options, visit https://groups.google.com/d/optout.

Lupe Silva

unread,
Aug 27, 2017, 10:56:17 PM8/27/17
to Church.IO
https://...    

Tim Morgan

unread,
Aug 28, 2017, 9:45:01 AM8/28/17
to Church.IO
Check your nginx config... it should have this line: https://github.com/churchio/onebody/blob/master/build/deb/vhost/nginx.conf#L23

proxy_set_header X-Forwarded-Proto $scheme;

Lupe Silva

unread,
Aug 28, 2017, 10:10:01 AM8/28/17
to Church.IO
Thanks.  None of the proxy_set_header entries were in the nginx confg file.  I put them in and it resolved the issue.

Lupe

Tim Morgan

unread,
Aug 28, 2017, 10:27:06 AM8/28/17
to Church.IO
Great!
Reply all
Reply to author
Forward
0 new messages