Topic: websocket port in conf

[mwawrzyniec]

I am attempting to get a basic javascript example to work with mosquitto. Where in the conf files does it specify what port apache uses for websockets?

Apache 2.4.29
Ubuntu

[mraddi]

Hi,

don't know if I got your question right, so if this is not the answer you are expecting please try to do your question in other words

Apache and Mosquitto are two different services running on two different ports. So there is no need to configure a websocket port in Apache. Your client's javascript can connect directly to the mosquitto's websocket port.
Tested and is working fine - as long as your client can reach both the Apache- and the Mosquitto-websocket-service (port 80/443 and port 1884 in my case). If your client connects to the Apache encrypted the connection to the Mosquitto has to be encrypted, too.

I've read some documentation about mod_proxy_wstunnel and it seems that Apache can act as a reverse proxy for websocket-connections, too.
In fact websockets start as a normal HTTP-connection with a "Connection: Upgrade" to become a websocket (if the destination-server supports this) - see https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake
So if your Mosquitto is not directly reachable from your client using mod_proxy_wstunnel might be an interesting approach.
You can specify a vhost running on a different port containing the configuration for proxying everything to the backend-Mosquitto or maybe it is possible to put the Mosquitto-websocket-proxy-thing into a virtual directory (as they did in https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html with the paths /ws2/ and /wss2/)
I would also point to https://stackoverflow.com/questions/27526281/websockets-and-apache-proxy-how-to-configure-mod-proxy-wstunnel with the answer from "cdauth" proxying all websocket-requests to a backend-service and serving the normal http-requests with the apache itself.