Ah, that makes sense. If there's supposed to be a second network connection from the browser to the server, it too will have to be forwarded.
To make the main web-page connection happen via HTTPS, I have Apache handle the authentication and pass incoming port 443 to internal port 8088. If Bob needs another connection for automatic communication, not only does it have to be forwarded, it has to pass through authentication. I see that if the main web server is listening on port 8080, Bob will listen on 8081. How does that work out on the browser when the main connection is on port 443? Is it going to try to reach the websocket listener on 444 or on 8081? And if it is running on a different connection, how is it going to negotiate HTTPS authentication? If there is anyone who has successfully set up Bob behind a web server which handles the HTTPS auth, please share how you did it. Otherwise, I may have to give up on Bob and go back to plain Tiddlywiki. On Saturday, September 14, 2019 at 6:45:53 PM UTC-4, Jed Carty wrote: > > If I remember correctly you have to tell Apache to forward websockets, so > if you are having trouble that may be why. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0493c3d7-4662-45dd-96d3-5a01c3e95602%40googlegroups.com.
