-
Notifications
You must be signed in to change notification settings - Fork 53
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
[BUG] Server doesn't start automatically #81
Comments
Hi, sorry for the inconvenience. This seems rather odd... building the network config should not affect the server creation whatsoever. The network IDs to be added are gathered beforehand and then given to the Could you maybe try creating a server connected to an existing net with the official |
Very strange indeed. I just tried with a fresh test project and for me everything works as expected (though I had to specify at least one network via command line argument instead of the environment variable due to an unrelated bug #37). It worked with both a single network provided via command line, as well as two -- one of which was provided via environment variable. The only thing I could see in the cloud panel was that the server sometimes did take a little more time after creation, before it actually spun up... but still, it was like under a minute between creation and automatic start. Anyways, as I'm currently out of ideas, I have just released 3.7.1 with updated dependencies. I was unable to reproduce the problem with neither a 3.7.0 build downloaded from GitHub nor my local 3.7.1 build. But maybe you can give it a shot so we can strike outdated library versions from the list of possible causes. |
Thank you so much |
Glad you were able to figure it out. If it is indeed the same network being specified more than once that causes the issue, I think that is a bug on the API side of things. I'll do a few experiments tomorrow and if that indeed causes the issue and perhaps file a ticket with Hetzner. |
@zek Just to let you know, your suffering was not pointless; the underlying issue is fixed now. hetznercloud/hcloud-go#196 |
Hello,
When I set networks by
HETZNER_NETWORKS
env variable, after the server created it doesn't start automatically.I had to start it manually throught hetzner panel.
The text was updated successfully, but these errors were encountered: