I am trying to deploy my reaction to a shared hosted server. The deployment itself was successful but I have to proxy the external traffic to the internal port the reaction node is running on.
This I have to do via htaccess
RewriteRule (.*) http://localhost:PORTNUMBER/$1 [P]
So far so good. The problem is that my provider does not accept the websocket traffic through the proxy. And as far I understand reaction relies on it, right?
So my provider suggested to figure out if reaction does all communication through websockets or just a little part of it. In this case he suggests that it might be possible to separate the websocket traffic from the regular http traffics that runs over port 80 or 443. In this case I could proxy traffic correctly and open a separate port just for the few modules that use websocket traffic.
I’m not a dev ops pro so I am not sure if something like this could work or does make sense in general.
I would appreciate if somebody would share their thoughts on this.