Greg Molnar

Your whole setup is wrong. In your private_pub.ru file put this: ``` ruby require "bundler/setup" require "yaml" require "faye" require "private_pub" Faye::WebSocket.load_adapter('thin') PrivatePub.load_config(File.expand_path("../config/private_pub.yml", __FILE__), ENV["RAILS_ENV"] || "development") run PrivatePub.faye_app ```...

I haven't checked it but I guess there is some hard coded reference for the faye url so it has to be like in the config file below. ``` yaml...

The current version of private pub won't play nicely with https unfortunately. Ryan seems to have a time off from development so the project is a bit abandoned. I will...

You can give a try to this fork at the `ssl` branch https://github.com/BinaryMuse/private_pub/tree/ssl. I had a quick look and it should work ok.

It should pick it up if directly accessible: https://github.com/ryanb/private_pub/blob/master/lib/generators/private_pub/templates/private_pub.yml#L9 Not sure why it doesn't work for you. What do you get in rails console for `defined?(SecureRandom)` ?

I see. That fork made before the refactor. The quickest route for now is to skip the use of the generator and just create the config file by hand.

You should setup apache to forward domain.tld/faye request to the port you are starting thin on. I am not using apache for a long time so not sure how to...

Ok, I just had some time to look into this and realized that Ryan already added the https support. At the bottom of the readme (https://github.com/ryanb/private_pub/commit/41a614c3b7b2bf8cd8e3e855b628e13a52f0428f) an example of how...

@chrise86 Is you certificate working in a browser? It looks like it is more of a certificate issue than anything with private_pub

This looks good to me. I will do some tests and will come back to you.