Faye.js not working on Heroku with https - ruby-on-rails

I am developing rails 4 application with private_pub for chatting apps. Its work perfect in local. But when move code from local to Heroku chatting not working due to below error:
https://XXXXXX-XXXXXXX-8XXX6.herokuapp.com/faye.js Failed to load resource: the server responded with a status of 404 (Not Found)
Actually in local working with http:// and on Heroku with https:// so may be issue but not found. Any one have a idea on it.
Thanks

Have you created a separated faye app on heroku? If not it's described here: http://www.thegreatcodeadventure.com/hello-or-building-a-chatting-app-with-rails/. Btw I changed from faye to pusher in which case I don't have to deploy a second app on heroku.

Related

Heroku - how to reconnect Mailgun to my app

Im working on a project with Ruby on Rails language, deployed to Heroku everything is working fine
I had Mailgun addon installed in my Heroku app
at one point I tried to change it to another mailing Addon
so I unlinked the Mailgun addon and connected another Addon
after a little research, I wanted to connect back the Mailgun addon.
when I tried to connect Mailgun again, it said that my app has an account and I cant reconnect it
I cant access my account by the email written in the Heroku's error notification.
what should I do at this point?
In that link below, there is an image of the error I get in my terminal.
Heroku Error for command: " heroku addons:create mailgun:starter"
Another link for an image of the error I get when trying to add Mailgun addon through my heroku app dashboard.
Heroku Error from Heroku dashboard
If you think I should use another mailer addon, I would love to hear about it.
Thank you in advance

Rails 5 action cable not working on aws elastic beanstalk

Im working with Rails 5 and integrate Action cable for chat system, its working fine on local, also working fine in production mode but not working on AWS elastic Beanstalk, please help me to resolve this problem, many thanks.
Following errors has coming:
WebSocket connection to 'ws://dreamermade-staging.qdmpcqqmnw.us-west-2.elasticbeanstalk.com/cable' failed: Error during WebSocket handshake: Unexpected response code: 404

websocket-rails standalone mode running heroku

I'm trying to run websocket app using rails module "websocket-rails" by standalone
mode on heroku. I ran the app in my local env but it seems not working on heroku.
It seems my app cannot reach websocket server.
I use redis for the websocket backend and the redis config does not show any errors.
Is there anything else I can check to investigate the fault? Or heroku does not
support standalone mode websocket?
If there is any document, I'll appreciate that.
thanks in advance.
It was just the setting of websocket server. I'm not sure this is the legit answer, but just specify the app uri for websocket server, it worked. I wrote the details here

Deployed Rails3 but not showing up outside of server

I just deployed my Rails3 app to a linux server with Capistrano and Unicorn using mysql2. I keep getting the error "Oops! Google Chrome could not connect to 172.16.128.125" when trying to access the app in a browser.
What is weird is that I see no errors in the ./log/production.log file and if I use lynx on the server, I can render all pages of the app.
What am I missing? It works locally on the server but not outside the server.
Sounds like you might not have Apache running, or port 80 may not be reachable on that machine due to firewalling or routing issues.

Rails Dev Server not visible on network

Trying to do something very basic and test my Rails app on my phone.
Starting the server with:
rails s
But when accessing mymachinename.local:3000, Mobile Safari says that the server stopped responding after about 30 seconds.
I do this all the time on other machines, but I have no idea what could be causing it here. Any suggestions?
I've had a similar issue before trying to access the server from a virtual machine, I had to use the following format for the rails server command:
rails s -b your.dev.ip.address
Whoops. Firewall. Don't know why I even had it turned on.

Resources