• Email Address: forum@outsourcepath.com
English
  • English
Topics related to aws cloudfront

Cloudflare err_ssl_protocol_error - Fix it Now ?

This article covers methods to resolve Cloudflare ERR_SSL_PROTOCOL_ERROR. Basically, this error happens as a result of a number of reasons that include wrong DNS settings, SSL mode, TLS version or issues with SSL certificate. 


To fix this error,

1. If you are not the site owner, contact the site owner and let them know you are having issues accessing their site.

2. The domain name has not fully been set to use Cloudflare yet. Check to see if there are non-Cloudflare nameservers that are conflicting with the assigned Cloudflare name servers.

3. You are signed up for Cloudflare, but you have set a DNS record to :grey:. If you have a subdomain or hostname and that serves HTTP/HTTPS traffic, we would advise that you :orange: this DNS record to take advantage of Cloudflare’s security and performance features. See What subdomains are appropriate for :orange:/:grey: clouds? 69

4. The Free Universal SSL certificate hasn’t yet been deployed, :grey: (deactivate) Cloudflare so that your website can continue to use your origin’s SSL certificate. Wait 24 hours and :orange: (activate) Cloudflare again to see if your SSL certificate has been successfully deployed.

5. You have some conflict with TLS 1.3, disable it and see if you still encounter the error.

6. You have selected Full SSL (strict) under your SSL/TLS app, but your origin does not have a valid certificate (i.e., it is expired, self-signed, or not issued by a trusted CA). Temporarily select another SSL option until you have a valid origin certificate in place.

7. Try to look at developer web console (firefox Ctrl+Shift+K) - anything interesting under Security tab.

8. Also, Try to run the command curl -vk on the affected domain.

Cloudflare 502 error - Fix it Now ?

This article covers methods to resolve Cloudflare 502 error. Basically, the Cloudflare 502 error triggers when the origin web server responds with a standard HTTP 502 bad gateway or 504 gateway timeout error. 

This happens due to firewall restrictions and server resource issues.


Cause of 502 Bad Gateway Errors:

1. Domain name not resolvable

The domain name is not pointing to the correct IP or it does not point to any IP this problem may happen. Also, DNS propagation could take some time to make changes in DNS setting. It may take 24 to 48 hours to make reflect which is dependent upon the TTL defined per record on the DNS.

2. server down

The origin server is not reachable, this may due to the server is down for some reason or there is no communication to the server given.

3. Firewall blocks

A firewall interrupts the communication between the edge servers and the origin server. This may be caused by security plugins of your CMS.

As a part of DDOS protection and mitigation process or due to some strict firewall rules servers can be blocked from accessing the original server.

Set up Amazon CloudFront with WordPress site - Do it now

This article covers how to set up Amazon CloudFront with WordPress site. WordPress performs reasonably well out of the box, but there is room for improvement—the number of WordPress plugins that address performance is evidence of this.  However, the easiest way to improve the user experience is to accelerate one's entire WordPress website by using CloudFront. 

Doing this will not only improve your site's responsiveness, but it may also reduce the overall cost of operating your WordPress infrastructure, as reducing the load on your web servers may help you scale down the required infrastructure. 

In fact, CloudFront can significantly help your site cope with an unexpected load when your site gets popular.


How does CloudFront help?

Many AWS customers have users spread across the globe that they want to reach. However, what once required an immense engineering effort can now be easily built using AWS Regions and Edge locations, which allow you to serve content from the locations closest to those users.

Data transfers on the internet depend largely on global networks of fiber optic cables, allowing very high bandwidth data transfers. 


As the speed of light is proving a difficult challenge to overcome, Amazon CloudFront improves the experience for users accessing your websites in several other ways, including:

1. Anycast DNS ensures your customers are routed to the nearest edge location.

2. Cached content, when available, is delivered to your users from the edge location.

3. When data needs to be fetched from your site CloudFront optimizes network throughput by managing the transfers between Edge Locations and your website.  This traffic runs over the Amazon Global Backbone, where optimized TCP configuration ensures more bytes are in-flight on the network, improving throughput, while TCP connection re-use eliminates much of the latency associated with establishing connections.   In this way, whether content is cached or not, it will be accelerated by delivery over optimized network paths.

4. Finally, negotiating and offloading Transport Layer Security (TLS) at the CloudFront Edge further improves performance, reducing connection setup latency, and further supporting back-end connection re-use.

How to setup AWS CloudFront and how it delivers content

This article covers how to setup AWS CloudFront. Basically, CloudFront retrieves data from the Amazon S3 bucket and distributes it to multiple datacenter locations.

Amazon CloudFront works seamlessly with Amazon Simple Storage Service (S3) to accelerate the delivery of your web content and reduce the load on your origin servers. 


Amazon CloudFront is a web service that speeds up distribution of your static and dynamic web content, such as . html, . css, . js, and image files, to your users.


Benefit of CloudFront?

Great Performance. The AWS CloudFront content delivery network optimizes for low latency and high information transfer speeds. 

CloudFront's intelligent routing predicate on real-world latency measurements incessantly gathered from standard websites, as well as Amazon.com.


Step by step process on getting started in the AWS Console, configuring your origin, and beginning testing your CloudFront distribution:

1. Go to the AWS Console

2. Create an Amazon S3 bucket

3. Create an Amazon CloudFront distribution

4. Specify your distribution settings

5. Configure your origin

6. Configure Origin Access Identity

7. Configure default cache behavior

8. Configure your TTLs

9. Configure additional features

10. Test your CloudFront distribution

Recent Post