gounlimited.to | BANNED FROM WJ

Status
Not open for further replies.
@GO Unlimited After today it sounds like you need a little bit of a laugh... Here you go.

G3XqO.jpg
 
Finally gounlimited Work again , thank you very much. #hug
:hugging::hugging::hugging::hugging::hugging::hugging::hugging::hugging::hugging::hugging::hugging::hugging:
Don’t thank me. Please accept my apology for the error. We haven’t done the necessary process yet to avoid this from happening again and I will keep working on it until the morning to avoid its happening again in the future.
 
I think I need a therapist after what happened today, because I spent 8 hours on the screen to constantly repeat the same commands all over again and again.

However, what happened today?

Let me first describe how GO Unlimited interface works.

We have a firewall like CloudFlare, which sends the traffic into a dedicated IP address (webserver).

That web server, let we call it A1, is not an actual web server but a proxy server that is dedicated to send the traffic into one of the REAL main servers.

Main servers are many, and they’re dedicated to receive the traffic from A1 and handle it to deliver the concerned page, so basically A1 is like the delivery guy, and the REAL main server which let we call them (B1, B2, B3, B4, B5) are the real handlers for the traffic.

The shitty part, is in case one of the B’s goes down, for example B1, the rest like 2,3,4,5 will go down as well even if they’re fine, and the reason is complicated and it is not necessary to describe it.

But, even that there B’s, there is D’s as well and they’re the databases servers. The B’s are dedicated to get the concerned informations from the D’s in order to display the page data which is stored in the database servers (D’s).

However, back in Wednesday we have updated the whole B’s range, and also the A system to understand that there is new B’s now in order to forward the traffic into the new B’s. Everything went well between the A and the B’s, but the database server (The D’s) was insisting to deal with the older B’s when trying to send the data back into the new B’s. So basically the new B’s were sending their requests D’s to the and the D’s was replying back to the older B’s instead of the new ones.

What action has been taken to solve this problem?
We have created brand new servers in order to use them as D’s and they’re installed from the scratch with the new B’s informations.

I am not sure if I even described what happened accurately.


Anyone also having problem with ZOOM ?
Yes, there is a problem which I am investigating in.
 
Status
Not open for further replies.
Back
Top