Upon recommendation of a member of the stackoverflow forum, I hereby ask the following question in this forum, where it apparently fits better (I'm new to this forum).
What exactly I want:
A specific page of my website should load its content (html structure, representing a chat window) from the web server, but its chat functionality, present as PHP Ratchet script on the server-side (placed on the same web server), should work via a WebSocket connection.
In other words, for this specific page, Web Server and WebSocket connections should work simultaneously, while I have only one Apache (2.4) server, on a shared hosting basis, with no root access. And, as stated, both the chat application programmed in Ratchet and the website's HTML page are present on the web server.
When testing this on my localhost, this worked very nicely. When trying to deploy it on my web server however, I got into trouble, and seemingly need to employ an NGINX reverse proxy in front of my web server, or similar (http://socketo.me/docs/deploy). Is that even possible to deploy given my hosting conditions, or do I need to switch to another hosting type? I started with configuring NGINX, but the problem is that I can't actually modify the port to which my Apache Web Server is listening, given that I have no root access.. I feel that I need to switch my hosting type for this purpose?
One of the aspects of this question may be summed up to: Is it possible to place a reverse proxy in between the client and the browser for websocket purposes, when having a web server on a shared hosting basis, without root access?