Ok so now after hitting a wall with SSL I thought lets see how Confluence handles it which his very interesting:
Running Confluence behind NGINX with SSL | Confluence Data Center and Server 8.6 | Atlassian Documentation
Their nginx configuration is nearly the same with the proxy headers for http 1.1 and connection upgrade.
However Confluence cleanly seperate their Realtime Colaborative Editing engine (Synchrony) into another port aswell as another location so that reverse proxys can handle things without too difficult configurations.
@mflorea could you possibly provide an configuration example for an reverse proxy with XWiki WYSIWYG and SSL enabled - like Apache or anything you are familiar something? That would be super helpfull.
Im not really settled to nginx, I simply want things to work and right now I can’t find any configuration Documentation to get the the Realtime WYSIWYG Editor running with SSL.
NEVERMIND:
When Enabling SSL you HAVE TO edit the xwiki.cfg and tell XWiki that it is running on SSL as well as the server name, otherwise the Websockets are still sent on http (port 80) from XWiki. Actually this makes quite sense.
xwiki.home=https://yourservername.yourdomain.yourTLD/
xwiki.url.protocol=https
I will later on post an full baseline https nginx configuration so that other people don’t run into the same issue as I did.