Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


whatsmyname last won the day on November 8 2019

whatsmyname had the most liked content!

Community Reputation

1 Neutral

About whatsmyname

  • Rank
  1. SOLUTION: In order for the client to work over SSL you need to set the server certificate and private key and start a secure server as follows. Please see here: https://github.com/ratchetphp/Ratchet/issues/609#issuecomment-363743604
  2. Yup, echoed out any messages on the deployed version. I have nothing. https://github.com/ratchetphp/Ratchet/issues/764
  3. As soon as anything is posted: HTTP/1.1 500 Internal Server Error X-Powered-By: Ratchet/0.4.1
  4. On the deployment server Centos 7, telnet connects "Connected to"
  5. Just a quick update! telnet is working and does connect to both deployment and local. - I didn't write the host name and port correctly. HOWEVER both of which eventually times out also: HTTP/1.1 500 Internal Server Error X-Powered-By: Ratchet/0.4.1 Connection to host lost. - Will check logs now.
  6. The browser shows "pending" at which point eventually times out with "WebSocket opening handshake timed out"
  7. Thanks for sticking around @requinix Running post.php does trigger (onBlogEntry) which outputs "Hello!" Tried to telnet into the remote deployed version and telnet outputted "Connecting To host...Could not open connection to the host, on port x.x.x.x:8443: Connect failed" I then tried it locally (Windows): Connecting To host...Could not open connection to the host, on port Connect failed I then tried to telnet into their basic hello world example as follows: Connecting To host...Could not open connection to the host, on port Connect failed.
  8. I've ran this on XAMPP locally and on Centos 7 remotely deployed both of which the javascript will timeout on handshake. The remote has a valid SSL certificate and domain name. I've also gone as far as disabling the firewall to make sure this was not an issue. I take it you have experience in websockets?
  9. Sorry, just to touch up. The client.html is the issue.
  10. Your not misreading it indeed is. I'm using a library called ZMQ which posts to the server side ZMQ this then sends the data to the actual socket server. It allows for things like subscribe to notifications. If you stripped all this back and used the most basic "Hello World" located here "http://socketo.me/docs/hello-world" - This is what it looks like without ZMQ. This also does not like to run over TLS/SSL. My scripts above are from here: "http://socketo.me/docs/push" I'm so stumbled right now, I really am. "WebSocket opening handshake timed out" I've even posted on stack
  11. Hello. Yes, the server is started via command line e.g. 'php server.php' The server is working as 'post.php' is sending messages but the client.html JavaScript is not.
  12. I've finally got the time to learn web sockets and have choosen to use: http://socketo.me/docs/push to do so. It all works perfectly fine without SSL. The moment it's enabled the client javascript will not connect and will output "WebSocket opening handshake timed out". I've tried the server with and without the TLS options. client.html, post.php, server.php <script type="text/javascript" src="autobahn.js"></script> <script> var conn = new ab.Session('wss://domain.com:8443', function() { console.log('Connected'); conn.subscribe('kittensCate
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.