mod_proxy_wstunnel issues

ChrisjV

• February 21, 2018 05:12

I"m currently running the latest version of Cpanel and receiving the following when connecting to a websocket with socket.io to a NodeJS server. This appears in /usr/local/apache/logs/error_log H01144: No protocol handler was valid for the URL /example.com/ (scheme 'wss'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule This is indicating

• 

  cPanelMichael

  • February 21, 2018 14:00

  Hello, Could you open a support ticket using the link in my signature so we can take a closer look at your server's configuration? Thank you.

  0
• 

  siim

  • August 15, 2018 12:10

  have the same issue. any solution to it? or I'd also have to open support ticket?

  0
• 

  cPanelMichael

  • August 15, 2018 15:18

  Hello @siim, Here's a quote from one of our Technical Analysts in the support ticket that was opened by the original poster (note that references to real domain names and usernames have been replaced with examples): [QUOTE] After some investigation, I found the following resource: [R"solu] Apache 2.4 et ProxyPass Socket.IO (node.js) - Comment proxyfier uniquement du socket.io ? par Harmo801 - OpenClassrooms I had to use Google Chrome to translate the page so that I could understand what was happening. Upon reviewing the information there, I saw that this issue was resolved by adding an upgrade header. I went ahead and took a shot at modifying this configuration to suite your situation, and it appears to have worked. I added the following to your configuration: ===================== # cat /etc/apache2/conf.d/userdata/ssl/2_4/username/domain.com/proxypass.conf #Proxy Stuff RewriteEngine On SSLProxyEngine On ProxyRequests Off ProxyPreserveHost On ProxyPreserveHost On ProxyPass "/socket.io/" "ws://localhost:3000/socket.io/" ProxyPassReverse "/socket.io/" "ws://localhost:3000/socket.io/" ProxyPass "/" "
  The ticket submitter then sent a response with an additional note: [QUOTE] Thank you very much - it has been made aware that the upgrade did work. I had to remove the following: ProxyPass "/socket.io/" "ws://localhost:3000/socket.io/" ProxyPassReverse "/socket.io/" "ws://localhost:3000/socket.io/" And that has allowed it operate now that the connection was upgraded.
  Let me know if this information helps. Thank you.

  0
• 

  siim

  • August 15, 2018 19:17

  helpful, not really.. still get the same error about invalid protocol handler.. so I just replaced wss:// part with http:// and from the first look of it, works fine..

  0
• 

  cPanelMichael

  • August 16, 2018 15:28

  helpful, not really.. still get the same error about invalid protocol handler.. so I just replaced wss:// part with http:// and from the first look of it, works fine..

  
  I'm glad to see you were able to get it working. Do you mind confirming the full step-by-step instructions of how you solved the issue in-case anyone else encounters the same error? Thanks!

  0

Please sign in to leave a comment.