Hello everyone–
Summary
New user invite links give a ERR_SSL_PROTOCOL_ERROR even though the rest of the site works fine.
Context
I’ve been running a completely stock Discourse Docker image for about 5 years with no troubles. About a year ago I moved to https with Let’s Encrypt using this guide.
Since then the site has performed well, and existing users can log in and out.
Problem and troubleshooting
As described, new user invite links give a ERR_SSL_PROTOCOL_ERROR even though the rest of the site works fine.
I have run all of the debugging steps in the Debugging section of the Discourse Let’s Encrypt setup guide. Everything ran fine, and the problem persists.
The logs don’t look perfect, though:
warning: nginx: unable to open supervise/ok: file does not exist
[Wed Dec 5 20:41:53 UTC 2018] Reload error for :
Started runsvdir, PID is 1086
ok: run: redis: (pid 1101) 0s
ok: run: postgres: (pid 1096) 0s
rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Server listening on 0.0.0.0 port 22.
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ]
Server listening on :: port 22.
rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
supervisor pid: 1099 unicorn pid: 1125
For the first error, I found this post but I am not using a proxy.
Has anyone else run into this problem? I run another site, started a little later, which does not show this problem.
Thank you!
Erick