No protocol handler valid for the URL

Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>>

Recently, the company’s websocket chat project suddenly hung up, requiring a new set of deployment, and the whole environment was set up. However, websocket was unable to start the WS link, prompting “no protocol handler valid for the URL” with httpd mod_ proxy_ Balancer, now record the process

First of all, whether the server-side startup code of websocket has any problem is excluded. After the exclusion test, the server can be started with the same set of server-side code

2 exclude whether the proxy module of Apache is not started

Using Apache CTL – t – D dump_ The modules command checks whether Apache has started the proxy module, which contains

3. If there is no error in starting the server, netstat – tunlp can see the starting port number to prove that the server is started

4. If no protocol handler valid for the URL appears when the client cannot connect, it is mostly the server’s problem

One is to check whether the firewall has blocked the port

2. Before installing socket related services, such as node.js, you must restart the machine or sysctrl – P to reload the machine configuration

Similar Posts: