> On Oct 3, 2020, at 7:20 AM, Sam Ruby <ru...@intertwingly.net> wrote: > > This is unrelated to the problem I was seeing (the websocket server > was failing). > > The message in the error log: > > [Sat Oct 03 13:52:54.956298 2020] [proxy:error] [pid 1042:tid > 140478557177600] [client 71.204.185.91:59703] AH00898: Error during > SSL Handshake with remote server returned by /board/agenda/websocket/ > > The relevant portion of the Apache configuration: > > SSLProxyEngine On > ProxyPass "/board/agenda/websocket/" "wss://localhost:34234/" > > So it looks like the Apache web server is trying to create a SSL > connection to a localhost websocket, and isn't happy about something, > most likely the certificate as it isn't possible to create a > certificate for localhost. But whimsy-vm4 is set up the same way, and > works. Not sure what the difference is, perhaps the newer libraries > are actually checking the certificate now, or perhaps the base puppet > configuration is different. > > The following seems to have some suggestions worth exploring: > > https://serverfault.com/questions/538086/proxyerror-ah00898-error-during-ssl-handshake-with-remote-server > > - Sam Ruby > > P.S. It does seem odd that the whimsy_error.log is empty and the > errors are going to whimsy_error.log.1.
So, I've been overwhelmed with non-ASF stuff and haven't figured this out, but I have been working around it in a couple ways. First, it only seems to happen after the first request times out. As in, I can quit Firefox, reopen, go to the agenda, and perform one sequence of requests successfully if I am fast enough. That's how I managed to send out the final reminders. But then the websocket times out and I cannot do anything -- a page reload will simply block, even though it isn't going to reload the page via websocket (AFAIK). Second, I don't have this problem on Safari. It works fine. In fact, it doesn't even seem to be using the websocket connection. I haven't tried other browsers yet. ....Roy
