Google CDN 502 Bad Gateway Errors - google-compute-engine

I am experiencing a problem again with the Google CDN.
I have checked the incidents reports but do not see anything related to the CDN or the Google Compute Engine.
How do I figure out what is going on here? Or if this is already being looked at?
Here is a thread I posted on this before: Google Load Balancer CDN 502 Errors
The message I am seeing is "Error: Server Error The server encountered a temporary error and could not complete your request. Please try again in 30 seconds."
Here are my 3 VM Instances
http://104.154.79.149/round.gif
http://104.198.106.79/round.gif
http://104.196.138.170/round.gif
And here is the CDN Ip address
http://130.211.31.236/round.gif
The VM Instances load fine but there is a problem with the CDN.
When I click through to the Cloud CDN, go into my instance and look in the monitoring for HTTP. It says
cdn-west-1-group us-west1-a 0 of 1 instance healthy
cdn-central-1-group us-central1-b 0 of 1 instance healthy
cdn-east-1-group us-east1-b 0 of 1 instance healthy
Here are my firewall rules for the CDN
IP ranges
130.211.0.0/22
35.191.0.0/16
209.85.204.0/22
209.85.152.0/22
With allowed ports 1-5000
Here is the default-allow-internal rule
10.128.0.0/9
tcp:0-65535 udp:0-65535 icmp
Can anybody please help? I did not change anything recently and it just stopped working overnight.

Related

Deploying a .NET application to Google Cloud Platform worked on initial deploy, now getting 502 Error: Server Error

To give some background, I'm an (unpaid) intern, and I'm unrelated to dealing with this kind of stuff. My employers wanted to update some pictures, and they did locally but didn't know how to upload the new version to the server.
I used the publish settings that were saved in Visual Studio from when the previous intern deployed the server (he was specialized in web site stuff) and it worked on deploy ... then I refreshed the page and I'm getting 502 server error.
Steps I have taken:
Connect to the VM and restart it - didn't solve it. it's using Microsoft server 2016.
Open the VM trough RDP, check if there are errors. There were 3 services not running, and I start them manually. One still isn't running, Downloaded Maps Manager. Ok... I google it and it's not a necessary service so I disable it. Now there are no errors and all services are running but I still am getting this error.
I tried pinging the IP of the server, and the URL itself and it works.
I believe it might be something to do with the load balancer, but I had one HTML class and nothing dealing with actually publishing stuff. If you could point me in the right direction I would appreciate it. The only reason why I'm trying to fix this myself is that I didn't make some kind of backup, and I feel so stupid having taken the site down.
Edit: I've gone to "load balancing" and it says service unhealthy. I tried going to the IPs there and it brings me to the same 502 server error page. From what I've gathered this is a configuration error, it's impossible they messed something with the site itself, right? It did work that first time, and if I run it from Visual Studio it works on the local machine ...

ssl and chrome: err_ssl_protocol_error from time to time fixed with f5

We're having some issues on some machines related with ssl when connecting to our sites through https. sometimes, some of the users get the err_ssl_protocol_error when they try to load one of the sites. now, the weird thing is that hitting f5 solves the issue and the page that was returning the ssl error gets miraculous loaded. we've already tried most online suggestions (checking date and time, cleaning the browser/ssl cache, etc).
we have changed the ssl certificate recently (a month ago), but the issues have only started now. btw, all our requests go through our firewall (forti adc) which is responsible for enforcing the https to all our clients.
any clues on why we're getting this error?
edit: adding more info
sites are hosted in iis (windows server 2016)
our firewall is running forti adc
the requests go through a load balancer before hitting firewall
the firewall has the wildcard certificate used for ssl (all. sites)
sites are built with aspnet
it only happens on some pcs, and only with chrome (Firefox is working without any problems)
edit 2: More info from wireshark
So, I've used wireshark to capture the traffic and when I get the ERR_SSL_PROTOCOL_ERROR on chrome, I've noticed that wireshark is showing me an alert with a decrypt error in response to the server hello message:
Any clues on what's going on here?
After lots of digging and testing, it seems like there's an issue with openssl and ECDHE algorithms. Changing the algorithm to a non ECDHE seems to have solved the issue for our chrome users...

"Route not admitted by a router" on Openshift Online v3

I have an application deployed on Openshift Online v3 starter plan which (used to) run well until yesterday. Yesterday I had to publish a new version of my application. Apparently, the platform encountered some problems redeploying it, I had to cancel some processes which seemed locked or continually restarting.
Finally I managed to have my pod running with the new version, the logs look fine.
The issue now is that my app is no longer exposed. When hitting the URL which was assigned to me, I got the infamous "not available" OO page:
Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
Possible reasons you are seeing this page:
The host doesn't exist. Make sure the hostname was typed correctly and that a route matching this hostname exists.
The host exists, but doesn't have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path.
Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.
I checked these 3 suggestions, and got sure that my host existed, that the path was correct, and that my pods where up. So, not understanding what the real issue was, I dropped the existing route and created a new one.
It's been 2 hours now, and the route UI keeps displaying this message:
The route is not accepting traffic yet because it has not been admitted by a router.
My understanding is that the router which should admit my route is not part of my project, it is managed by Openshift Online, am I right ?
So what could I do now to unlock my new route ?
Thanks for your suggestions
There it is ! My application is reachable again at last : It took 2 days for the router to setup my route. No action required from my part.
But the starter platform is still experiencing difficulties, so I will avoid any redeployment until the status turns green again.

HTML Video tag in Chrome fails to play intermittently against AWS ELB

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

google hangout microphone is not working with network error and firewall setting issue

From last 1 week i am facing strange issue in google hangout. as i join a meeting first a message pops up
Your microphone is not working or is hardware-muted!
then after few seconds i see message
Couldn't start the video call because of a network error.
Please check your firewall settings and try again.
with button to try again. and it keeps going on in this way.
I have checked firewall settings
I have tried with different networks
I have tried with different computers
I have tested microphone and speakers they are correct
I inspected ajax calls in firebug and i see this
NetworkError: 404 Not Found - https://plus.google.com/u/0/talkgadget/_/ping?id=1
NetworkError: 404 Not Found - https://plus.google.com/u/0/talkgadget/_/ping?id=2
POST https://plus.google.com/hangouts/_/channel/bind?...200F2A8A372&RID=67018&AID=84&zx=2a53yvv7e45w&t=1 Aborted
At google Community somebody answered like this:
I have found the culprit. I use Spybot Search & Destroy's Anti-Beacon software to block telemetry data that Windows 10 constantly sends to Microsoft. This is why trying multiple Windows 10 machines that I have configured did not alleviate the problem. Somehow one of the IP block entries it adds to the Windows Firewall now conflicts with Google Hangouts. I will report this to the software vendor.
Source: https://support.google.com/hangouts/forum/AAAAfpFnBZ8mdNNg8LNvNg/