Lost connection to API after upgrade to v0.14.0
# upgrades
j
Lost connection to API after upgrade to v0.14.0
@average-helicopter-96869 put update here
a
sorry 🙂 wasn't trying to clutter up the channel
j
just wanna give these threads a try, if someone else runs into the issue it'll be more helpful here
a
wow, i am shocked, i can't even ping the host
j
...on the public IP?
a
right
j
hmmmm...that does not sound netmaker related...
a
i tend to agree, but i'm uncertain what else changed
j
the one thing we do now is make sure ipforwarding is accepted on server startup
iptables --policy FORWARD ACCEPT
^ this gets run now on server startup
a
yeah, i ran into that on 13.1
i'm super confused. i just setup this VM fresh on 13.1 a few days ago... did nothing until today upgrading it to 0.14.0 today...
ufw status
still looks good... it can ping itself... but multiple remote IPs are failing to ping it... i'll have to look closer at the iptables
j
yeah i don't really understand how netmaker could be causing that...unless a weird forwarding policy was set up causing some sort of loop
a
wow, frustrating... i disabled ufw and docker... rebooted... now there are zero iptables rules in kernel, only the 3 default chains, INPUT/FORWARD/OUTPUT all set to ACCEPT
and... i can't ping it
but it can ping out
not on ipv4... but i can ping it over ipv6
uh.... so weird... maybe vultr had something happen on their end... because now i can ping it
j
hmmm
maybe they just freak out if they see too much networking stuff going on
a
maybe... the one thing i did, i ssh'd out of my vultr (netmaker) box into another remote machine... then i could ping the vultr box
ah! and now i see they are dealing with some network outages... ok, that probably explains it 😄
phew! great timing guys!
j
😂
I love it when things aren't our fault
a
anyway 🙂 the MSI still can't find my Wireguard installation
j
womp, i will switch over to windows and see...may be the old installer by accident
a
you want a ticket on that somewhere?
Copy code
Revision number {816FBAA2-EF1F-42AD-8181-CA023A6D6E97}
Content created 5/16/2022 1:18 PM
j
yeah...that's definitely wrong
a
happy to help 😄
oh, the MSI shows up on github releases now... i'll see if it's the same
same