I have an elastic beanstalk application that I"m trying to add https/ssl to. I added a listener, selected port 443 and https, selected my certificate, and then hit save.
I scroll down to the bottom of the page and make sure I hit apply, the server then rebuilds... but when I go back to look the https listener is gone!!
I never get an errors or anything weird, any ideas what I'm missing or doing wrong?
Same issue. I believe it was an incompatible SSL security policy switching to ELBSecurityPolicy-2016-08 fixed it. Found the answer here:
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html
Related
When I'm developing using Node's http2 library (which only supports HTTPS, not HTTP), when I open localhost in Chrome, I get a warning screen:
Your connection is not private
Attackers might be trying to steal your information from localhost (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
You have to click "Advanced" then "Proceed to localhost (unsafe)". It gets annoying having to do this during development.
I generated a cert and key for localhost use according to the instructions for Node's http2 module. Is there any way to generate them in such a way that Chrome would actually accept them for localhost? Or is there another easy way to get rid of this warning?
(I'm aware of the option of launching Chrome with --ignore-certificate-errors but I'd prefer not to do this for all websites.)
Try the following:
In Chrome, put in chrome://flags/#allow-insecure-localhost in the address bar.
Enable the option that says "Allow invalid certificates for resources loaded from localhost".
Restart Chrome, and it should allow the site.
You can also type thisisunsafe once you put focus on the website
There are two options you can use to get rid of this annoying thing, which are:
Temporarily Disable SSL Warning
You can go to Google Chrome, input chrome://flags in the address bar and press the Enter key to access advanced settings.
In the next step, find the "Allow invalid certificates for resources loaded from localhost" option and enable it. This method is the same as using --ignore-certificate-errors attribute on your Google Chrome shortcut. It disables the SSL warning for all sites.
It's just a temporary solution and I wouldn't suggest to use this frequently.
(I'm aware of the option of launching Chrome with
--ignore-certificate-errors but I'd prefer not to do this for all websites.)
Install SSL On Your Localhost with OpenSSL
You can install SSL on your localhost with OpenSSL. By using this method, your localhost can run HTTPS without any issue at all. The tutorial is quite long with detailed instructions, you can read it at here.
Source: Fix Your Connection Is Not Private Error In Your Browser - ByteBiteBit.com
I tried too many techniques but nothing works at last i find it while i was learning Webapi.
i was unable to visit to any side beacuse of showing the Error "Your Connection is not Private"......
THE REASON IS You have to enable SSL on your Browser and how you can do it let me share the link..
Just follow the steps
https://www.youtube.com/watch?v=4hb6iD3nP6g&list=PL6n9fhu94yhW7yoUOGNOfHurUE6bpOO2b&index=16
chrome://flags/#allow-insecure-localhost in the address bar.
set it to Enabled
relaunch chrome
result
I'm debugging a local site.
I'm getting the following message in chrome.
Your connection is not private
Attackers might be trying to steal your information from t.buyamerica.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
This is not new, and normally I just click ADVANCED and Procced ...
but lately it just stuck in a loop and display the error message again.
This is a local site therefore the key-pair is indeed invalid, but is there a way to by-pass this issue without installing a proper https for all my local (vagrant based) servers?
NOTE:
The current by-pass for me is to use the same domain as the original site, so that the local site is www.somesite.com, and the actual site is somesite.com
I solved this issue as follow:
In
System Preference -> Network -> WiFi -> Advanced -> Proxies I saw that Secure Http Proxy (HTTPS) is checked and the value for the proxy is localhost:8888
I unchecked the Secure Http Proxy (HTTPS) and it seems to solve the issue.
NOTE: this is a specific MAC issue that apparently caused by a system upgrade (my current version is 10.10.5 (14F2511) Yosemite, MacBook Air (13-inch, Mid 2012))
I never set a proxy server or run any proxy on localhost:8888
You change your local domain something like http://yourdomain.test.
Don't forget the 'http'. And if you're using .dev, change it to .test
Our system uses an AWS Elastic Load Balancer.
We are encountering a maddening issue where our HTML video tags are failing to play randomly. I can't reliably reproduce the issue unless I bypass the ELB, which makes me suspect it, naturally.
I've verified that the same files are on both of our IIS servers, and I have verified that the MIME types are the same on both.
The video files are H.264 MP4s, but they will sometimes work, so I don't think it has anything to do with Chrome's support of the codec.
Anybody have an idea on what I can do, or where to look next?
This is a session issue on the AWS ELB. Enable the Sticky Sessions on the ELB and this issue will be resolved. Here is the developers guide.
http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-sticky-sessions.html
I would enable full logging on both IIS and the ELBs, and carefully check the access logs on each to confirm.
You would expect to see a 200 http response code on the ELB and the IIS server for each request made. Check for any requests that result in a 400 or 500 error. You need to pair each individual request from the ELB to the IIS server and review.
See Monitor Your Load Balancer Using Elastic Load Balancing Access Logs
I've just auto-deployed a LAMP stack on Google Compute. Before when I did this successfully I had to enable HTTP and HTTPS. Now it seems like they've changed the interface totally again.
And this time I find the options to enable are greyed out.
I tried accessing my phpmyadmin at [ip address]/phpmyadmin and it timed out...so clearly http and https are not being allowed in....
How do I enable HTTP and HTTPS access?
This is what it looks like right now. Not sure where to go from here as the option is totally greyed out.
Ok, the answer is to hit the EDIT button at the top.
I do express the opinion though that this is the most un-intuitive (yet glossy) interface I've ever used.
I suffer no shame!
You can do the following:
Your instance is associated with the default network. Click on the default link.
This will bring to the default network settings where you should review all the Firewall Rules
Check if there are any firewall rules with tcp:80 or tcp:443 present for traffic. This will allow access from outside via http, https. If not, click on Add Firewall Rule and then provide access to those ports.
Alternately, you can also use gcloud to manage your firewall. Refer to gcloud firewall command example here.
My Chrome browser is in a weird state. It claims that it's configured to use a proxy server and that it can't connect to that server. Problem is, when I go to the LAN settings, the option to use a proxy server is deselected. Toggling this setting has no effect.
I've tried reinstalling Chrome but the problem persists.
Any idea on how I can get it to stop trying to use whatever proxy it thinks it's configured for?
try selecting no proxy in network settings of chrome. i'm not sure whether this going to work but it is worth trying. its not going to do any harm.
hope you find a solution