Configuring an HTTP Load Balancer with Google Cloud Armor Reviews

For some reason, the "check your work" button to verify if the load balancer was created did report that this step was not done. In fact, everything was already up and running. The LB name was correct. Also, the 'siege' program crashed several times with this error: *** Error in `siege': free(): invalid size: 0x000055dfeb2e73a0 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f6bac861bfb] /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f6bac867fc6] /lib/x86_64-linux-gnu/libc.so.6(+0x7780e)[0x7f6bac86880e] Despite these minor problems, a very interesting lab.

Saverio P. · Reviewed almost 6 years ago

Fahad H. · Reviewed almost 6 years ago

Marvin K. · Reviewed almost 6 years ago

Nick B. · Reviewed almost 6 years ago

Atul S. · Reviewed almost 6 years ago

Atul S. · Reviewed almost 6 years ago

SSH issue with lab

Andrew B. · Reviewed almost 6 years ago

John L. · Reviewed almost 6 years ago

Eric B. · Reviewed almost 6 years ago

The last verification failed to detect that the task was done.

Aguinaldo J. · Reviewed almost 6 years ago

Anthony E. · Reviewed almost 6 years ago

I got some kind of problem with Cloud Armor task validation, I open a request and found out that it is an issue which is OK, but would be clear if Qwilabs have some kind of status page to avoid some waste of time try to determine if I did something wrong.

Helder P. · Reviewed almost 6 years ago

Atul S. · Reviewed almost 6 years ago

Najim J. · Reviewed almost 6 years ago

Anthony E. · Reviewed almost 6 years ago

Joel M. · Reviewed almost 6 years ago

Evgenii M. · Reviewed almost 6 years ago

Clydon R. · Reviewed almost 6 years ago

晨曦 王. · Reviewed almost 6 years ago

hard

erik d. · Reviewed almost 6 years ago

Niteesh K. · Reviewed almost 6 years ago

Peniel I. · Reviewed almost 6 years ago

FISSEHA S. · Reviewed almost 6 years ago

mrrobot m. · Reviewed almost 6 years ago

Good

Yash V. · Reviewed almost 6 years ago