-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Networking issue #83
Comments
im not sure if you understand my issue but during the cloud-init deployment on the VM that was created the (side note server name in images is named what it is |
This has nothing to do with convoy. Convoy just uses default proxmox cloud-init deployment and does not change anything to the vm config. |
Solution 1: dont use ubuntu |
This is a strange issue. I wonder if it is possible if I could remove netplan from the Ubuntu images. As for |
Please be respectful even though that this isn't exactly relevant to Convoy. I don't want to promote a hostile environment. |
hm what isnt respectful there? its just facts i didnt blame anyone here :P |
|
Out of curiosity, what hosting provider are you using? I believe the I think you could try checking the Cloudinit config file and seeing if it's possible to do that automatically, otherwise, you could maybe do it through the host operating system depending on how your hosting provider does the network config. |
Closing because not enough information |
Current Behavior
Create a vm via convoypanel i.e ubuntu images 18 - 20 - 22 you will get an issue for ipv4 not connecting
for some reason on creation of the VM itself its missing the
via the
/etc/netplan/50-cloud-init.yaml
inside of the VM that was created.I have to manually go in and add this into every VM created from convoypanel......
Expected Behavior
ping google.com -4
to actually work i.e port 22 being accessible to world.
Steps to Reproduce
explained below
Screenshots
Proxmox OS Version
8.1.4
Operating System
Bookworm
Browser
Edge - Always Latest Non Dev Version
Additional Context
Offering a means to set this via the convoypanel would be the simplest fix In my eyes,
but yes I'm not sure where the bug lies I'm still going to need some more time to try to pinpoint the matter but bringing to your attention @ericwang401 in hopes maybe you know the bug / issue / seen it before / know the fix / or hopefully addressing a first time 🐛 we can 👟(squash)
ping google.com -4
right away to see if ipv4 is active....nothingnano /etc/netplan/50-cloud-init.yaml
inside the VM and notice that the above aforementionedroutes
block is missing so i add it in and run anetplan try
then anetplan apply
if confirmed to be runnable.ping google.com -4
and i get a connection on the VM using the IPv4 it was assignedEach server gets a Free IPv6 address to boot via our DHCPv6 protocols in place hence a connection on hop for ipv6 but nothing for ipv4 unless above is done.
Panel Version
v4
Error Logs
No response
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: