0

I have recently been using the free trial 90 days of Google Compute Engine (the payment configuration I already have it defined). But since this trial is finished the instance was paused, and I already ran it again, but now I cannot access my instance, not even SSH and when I ping the external IP (which I previously set to static) no response, and apparently this IP is down. What could be happening?

Instance is on but IP is down:

enter image description here

IP static is ok (don't worry if you see it):

enter image description here

SSH not responding:

enter image description here

Ping response:

enter image description here

Firewall rules:

enter image description here

Serial Port 1:

Serial port 1

Improve this question
4
  • 1
    I think the default firewall rules restrict incoming (Ingress) ICMP traffic and ... unless you have changed those rules, ping never works without changing rules for Compute Engines. Commented Oct 2, 2021 at 4:15
  • I just saw this article, do you think it would help me? Should I create a VPC network?. Although this did not happen to me before, the instance ran without problems, this happened after the trial period expired and I started the instance again. Commented Oct 2, 2021 at 5:36
  • 1
    What are your firewall rules? Commented Oct 2, 2021 at 18:47
  • @guillaume blaquiere I uploaded my current rules Commented Oct 4, 2021 at 17:54

2 Answers 2

Reset to default
1

This issue could be caused for several reasons:

  • You don't have billing enabled.

According to the official documentation if the 90 days after the Free-Trial period started has finished you need to activate billing in order to continue to use CE.

  • You have an issue with firewall rules. In this situation, as suggested the post, I recommend you to try the following things:
  1. Create a ingress firewall rule for port 22 and make sure it's applied to the proper instance.
  2. If the firewall rules are properly applied, you may have blocked port 22 in your instance. In order to unblock it you could use a startup script in order to unable port 22 by runnig ufw allow 22.
Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Account billing is activated, and I start the instance again. All firewall rules is ok, the problem is that the IP does not respond, so there would be no reason to open a port if the IP does not want to respond
1

As it seems that the VM config wasn't changed and the Firewall seems correct.

I suggest you to go to the instance details and click in the Serial Port 1 (Console) to inspect the serial console logs. With those logs you can investigate further as the OS may no be able to boot properly.

If you are unable to run the instance properly you can still use the disk in another instance to recover the data, reference.

Improve this answer

4 Comments

I followed the step of the reference and I am already running it as a new instance but the problem persists, cannot access compute ssh, Putty returns Time out. Also attach the Serial port log in the main question, I suppose something is happening there?
Have you checked the Serial Port logs? There you could gather info about the OS, check if is able to run. Regarding new instance, you can create one and use this disk as a secondary disk (not boot disk) to recover the data.
I put the capture in the first post
It seems that the instance is not able to boot. You could use the disk as a secondary disk to recover the data or you could investigate that specific message, related [1] [2]. [1]:github.com/utmapp/UTM/issues/2333#issuecomment-786129411 [2]: serverfault.com/a/1068357/535728

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.