리뷰 VPC 흐름 로그를 사용하여 네트워크 트래픽 분석하기개
리뷰 55419개
Wenbo Y. · 대략 2개월 전에 리뷰됨
Jason L. · 대략 2개월 전에 리뷰됨
Good job!
Hải N. · 대략 2개월 전에 리뷰됨
good
Mahesh A. · 대략 2개월 전에 리뷰됨
Olmo R. · 대략 2개월 전에 리뷰됨
Step 2 (Create an Apache web server), completly bug
Lukas O. · 대략 2개월 전에 리뷰됨
I still get pass the check mark for the apache being installed on the VM. from gemini (inside console.cloud.google.com): I have thoroughly investigated your web-server VM instance, network configuration, and system logs to see why your progress check might be failing. Investigation Findings All of your Google Cloud resource configurations are 100% correct and perfectly match the instructions: VM Name: web-server (Running) Zone: us-east4-a Machine Type: e2-micro Network / Subnetwork: vpc-net / vpc-subnet (IP 10.1.3.3) Network Tag: http-server is correctly assigned to the VM. Firewall Rules: There are active ingress firewall rules on vpc-net (vpc-net-allow-http and allow-http-ssh) allowing TCP port 80 traffic to instances tagged with http-server. Apache Service Status: VM system boot and application logs confirm that the Apache service (apache2.service) successfully installed and started running. also, how could I have completed all other steps if the first one failed. This is just sad checking progress :)
Mikael F. · 대략 2개월 전에 리뷰됨
The Labs Web server step check fails.
David C. · 대략 2개월 전에 리뷰됨
Step 2 (Create an Apache web server), completly bug
Lukas O. · 대략 2개월 전에 리뷰됨
i had a vm named web-server with e2 micro us-region1-a on the specific subnet with apache2 installed and the custom landing page loaded. i could load it in the browser still it didn't like it. restarting the lab to see what I did wrong perhaps. sigh. second time same problem, maybe i'm utterly blind today.
Olmo R. · 대략 2개월 전에 리뷰됨
akash y. · 대략 2개월 전에 리뷰됨
Francisco N. · 대략 2개월 전에 리뷰됨
the set up the apache2 server is messed up.
Daryl M. · 대략 2개월 전에 리뷰됨
It does not detect the Apache server.
ALEXIS B. · 대략 2개월 전에 리뷰됨
First goal was not showing as completed.
Karam A. · 대략 2개월 전에 리뷰됨
Step 2, completly bug
Lukas O. · 대략 2개월 전에 리뷰됨
from gemini (inside console.cloud.google.com): I have thoroughly investigated your web-server VM instance, network configuration, and system logs to see why your progress check might be failing. Investigation Findings All of your Google Cloud resource configurations are 100% correct and perfectly match the instructions: VM Name: web-server (Running) Zone: us-east4-a Machine Type: e2-micro Network / Subnetwork: vpc-net / vpc-subnet (IP 10.1.3.3) Network Tag: http-server is correctly assigned to the VM. Firewall Rules: There are active ingress firewall rules on vpc-net (vpc-net-allow-http and allow-http-ssh) allowing TCP port 80 traffic to instances tagged with http-server. Apache Service Status: VM system boot and application logs confirm that the Apache service (apache2.service) successfully installed and started running. also, how could I have completed all other steps if the first one failed. This is just sad checking progress :)
Mikael F. · 대략 2개월 전에 리뷰됨
The Labs Web server step check fails.
David C. · 대략 2개월 전에 리뷰됨
Kunderu T. · 대략 2개월 전에 리뷰됨
Tim H. · 대략 2개월 전에 리뷰됨
אסנת כ. · 대략 2개월 전에 리뷰됨
Akari F. · 대략 2개월 전에 리뷰됨
Alexander S. · 대략 2개월 전에 리뷰됨
Aiqun W. · 대략 2개월 전에 리뷰됨
Sabrina C. · 대략 2개월 전에 리뷰됨
Google은 게시된 리뷰가 제품을 구매 또는 사용한 소비자에 의해 작성되었음을 보증하지 않습니다. 리뷰는 Google의 인증을 거치지 않습니다.