So my Rails (3.2.1) app was working fine on Heroku. Then I set config.force_ssl = true in my production config file, upon opening the file, I now got the "SSL is not enabled" error. I thought Heroku allows you to piggyback their SSL certs, but it is not working for me.
What I've tried:
using heroku addons:add piggyback_ssl (fails, as the add-on is now standard..)
validating my account (shouldn't be necessary, but I tried it anyway)
changing my config.force_ssl = false, but my app still tries to use SSL...
I may a bit late, but the reason that your browser still redirects you to https even if you have that option turned off in Rails has to do with the "Strict-Transport-Security" header (HSTS).
Try installing the Piggyback SSL addon as follows:
heroku addons:add ssl:piggyback
Once that's installed and your app has been restarted, it should be accessible at both of the following addresses:
http://your-app.heroku.com
https://your-app.heroku.com
Looks like you might have caught Heroku in the middle of a rollout. As of a few weeks ago, Piggyback SSL is now enabled for all users/apps by default. If you're still seeing the "SSL is not enabled" error, you should contact Support.
http://devcenter.heroku.com/changelog/10
Related
I installed a new fresh Bigbluebutton server on VMware without domain and SSL, after installing bbb-demo when I logged in, it showed an empty blue screen. In the browser console this exception was written:
Uncaught TypeError: Cannot set property 'ondevicechange' of undefined
The last time when I face a similar situation, I try to set a self-signed SSL but it just makes lots of problems and it didn't work.
How I could solve this error?
Finally, I've solved the problem. In this address ffdixon(product manager for BigBlueButton) said:
We need to update the docs -- you must setup an SSL certificate for BigBlueButton or it won't load. If you see "Not Secure" on your browser URL, BigBlueButton will not load.
I didn't have any valid IP or domain for my VM, So I created a valid SSL with one other domain(not belong to my VMware) and setup bbb to use SSL based on this article.Then set /etc/host to redirect SSL domain name to my local IP.
I have an ASP.NET Core 2.2 application. I have recently started getting the above error when we deploy our app to our test server. This is an IIS server with a valid HTTPS certificate. We navigate to the app using the HTTPS authority. I can't understand why I am now getting this error. What could have changed to cause this error.
I know I can set RequireHttpsMetadata = false and this will fix the issue, but I would prefer to understand why this is happening. What would have caused it to suddenly start happening.
Everything works fine in Development.
I faced the same issue after installing new fresh XP1 instance, and I found the problem is coming from Owin configuration.
Once disabled the Owin authentication by enabling this config file "\App_Config\Include\Examples\Sitecore.Owin.Authentication.Disabler.config.example" everything worked as expected!
This has to be done on CM & CD, unless you have the correct configurations for Owin Authentication.
I have been at this for days and I can't seem to find the solution for this. I have a live website, and I recently installed the ssl certificate and made the website available on https.
What's really strange is that at first the website worked well on https. For about a day or so it was live and working well. But then the next day I checked and the site is now giving me this error:
WebSocket connection to 'wss://domain.com/sockjs/421/dto72qfy/websocket' failed: WebSocket is closed before the connection is established.
The navigation bar loads and the sidebar loads, but the content doesn't, it's just stuck in the 'loading' template. If I check the domain in http the website is working fine.
I am using meteor up (mup) to upload the site and digital ocean. One of the few things I have changed was the mup.json
...
// Configure environment
"env": {
"ROOT_URL": "https://website.com/"
//"PORT": 80
},
"ssl": {
"pem": "./ssl.pem"
//"backendPort": 80
},
...
I'm not sure how to deal with websockets and why they only have problems in https. If anyone has gotten their meteor app to work with mup and ssh I would really appreciate some help.
You can disable websockets by adding the following environmental variable in your mup.json
"DISABLE_WEBSOCKETS"=1
If you don't want to disable websockets, you can try option 2 from here.
We have websockets disabled on https://saturnapi.com; you can see yourself if it is usable. Others have also reported that disabling websockets still allow for a usable app, albeit a bit slower. It should depend on how your app is configured, so I recommend giving it a try and reverting to the other solutions if it doesn't work.
Im building my first Rails app server on a Ubuntu server machine. I came to the point where i am testing a simple add located on the server. When I hit the root page, default rails message
"Welcome on board, You’re riding Ruby on Rails!"
Thats good i suspect. But when I hit server/todos i just get this error message
"We're sorry, but something went wrong."
How can I see full error message? I am completely new to Apache and Passenger. I suspect I could get full messages if i run from the server but there is no GUI or browser installed.
Ok found out this was all connected to the Rails app and not a Apache or Passenger setting.
# environments/production.rb
config.consider_all_requests_local = true
I set force_ssl to true by accident and then when reverting to false and running server I get the following error:
ERROR bad Request-Line
WEBrick 1.3.1
INFO ruby 1.9.3 (2012-02-16) [x86_64-darwin11.4.0]
WEBrick::HTTPServer#start: pid=472 port=3000
ERROR bad Request-Line `\x16\x03\x01\x00?\x01\x00\x00?\x03\x02P?Mf\x00??C?'.
How can I fix this?
When I hit http url on local host it redirects to https and gives me this error:
SSL connection error
Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have.
Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.
Answer can be found here: How to use deactivate Webrick's SSL
you can fix it by clearing the browser cookies and it works again. It seems the authentication information is saved in the cookie and keeps reverting our requests to HTTPS but does not authenticate correctly so you get that error.
Maybe you can try:
1) stop rails server
2) rake tmp:clear on the command line
Then start again and see if the problem persists.
UPDATE:
Maybe you can try to clean any cache content / history content on your browser too.
I usually end up using a different explorer, i.e.: Safari, Firefox, etc. As clearing the cookies do not solve the problem for me (while using Chrome at least)