Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automator Can't Connect to VM After Restarting. Needs Updating the instance's IP. #24

Open
hazimian opened this issue Jan 11, 2025 · 0 comments

Comments

@hazimian
Copy link

Hi there
At least on GCP, The VM's IP changes after restarting (stopping and then starting). I am doing the start/stop from the GCP mobile app. Clearly Automator does not know about the new IP and keeps failing when trying to interact with the instance. Any suggestions on how to inform Automator about the new IP?

Thank you!

@hazimian hazimian changed the title Can't Connect to VM After Starting. Updating the instance's IP. Automator Can't Connect to VM After Restarting. Needs Updating the instance's IP. Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant