-
Notifications
You must be signed in to change notification settings - Fork 208
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
Loosing network on OVH VPS #18
Comments
The network detection part of the script is not very robust and assumes digitalocean's idiosyncrasies. Likely , it didn't grab the right settings for your host. I'll probably improve it sometime in the future, but for now, try the following to manually provision your hosts: (if you have console access to an already-provisioned host, do only step 5, instead using the ip info provided in the OVH web UI, and then
Post me the networking.nix contents, if you still can't get it working. |
Yeah, for OVH, don't even bother with the networking, just rip it out completely. Change this:
to this:
I just successfully installed doing that. Debian 9 |
I should probably add a |
Is this still an issue, since we do this? |
I'll try to check it out, then tell you if it's okay now. |
@asymmetric Yes, this is still an issue. |
I have big issues to make it run on master, does any of you (@asymmetric, @charlycoste, @kniteli ) would have a functioning version ? I could take care of piggy-backing on it to set up a PR for master to function on OVH. |
Don't use OVH, sorry. |
@TheSirC if you still need help, attach a .log here with the output after you |
@elitak Yes, of course. Here is the error-log : Error log
The problem lies in the fact that even with |
Run |
I actually added it to the script itself without further output.
And immediately returning to the interactive prompt. |
After further testing (and multiple reinstalls of the VPS to make sure to work on a clean system each time) I found that :
Fun fact :
|
Fix both issues cited in this [comment](elitak#18 (comment))
Fix both issues cited in this [comment](elitak#18 (comment))
So after applying patches for the above-cited issues I opened a pull-request that worked for me on OVH. |
Fix both issues cited in this [comment](#18 (comment))
Resolved since 3 years.... Anyway i've similar problem on different budget provider. It's kinda weird -> vps does respond to ping but seems that it have all ports closed. Any ideas what's the problem? Anyway if i've enought time, i'll try do step by step what this script does and play a little with config. Maybe #61 is the solution? |
I tried on a VPS 2016 SSD 3 from OVH, each of these :
And each time I run the script, then installation + reboot are going well. But after that, I can't connect to the VPS anymore. I accessed it by KVM to debug and it seems that the VPS just get disconnected from network.
The text was updated successfully, but these errors were encountered: