@cservers said: The underlying system is in XFS for this particular server (an exception for the general FS used everywhere else), so we're running a xfs_fsr online and things should improve in the next 24/48h without downtime for anyone.
That's great to hear too! I have no performance complaints - though after the recent no-inbound-ports scare I am making an rsync backup just-in-case. That's proceeding slowly... but it doesn't need to be fast: just slow and steady...
And we've created a new article that essentially envelopes the symptoms and the resolution, called "NAT IPv4 Inbound is not working on my server. What to do?", which is now here and it is public so that other VirtFusion users at other providers can attempt the solution as well. The article is available here: https://web.c-servers.co.uk/info/nat-ipv4-inbound-is-not-working-on-my-server-what-to-do.
@cservers said: 30 days extra free service for @skorous. Send us your associated e-mail and VM where you desire those 30 days over PM and we'll do it tomorrow. This will also be reported to VirtFusion.
Appreciate that but no need. I'm just happy to have helped out a community member.
@skorous said: Hey @Nybble, did you get this taken care of? I was in the same boat ( my ssh port didn't work - was the only thing I had mapped to ipv4 ) but after adding a couple rando ports to see if it was just ssh or if something else worked my ipv4 magically started working.
Holy. Crap. That worked! Thank you!
They had tried assigning me a new internal IPv4, but nothing changed. However after adding a new useless port-forwarding rule like you suggested... all the old broken rules reactivated. I need to try some other things: but it looks like that fixed things.
Keep in mind that on latest ubuntu ssh port does not change with a sudo service ssh restart, needs to do some cycle on the network. Easiest is to reboot.
Comments
Exactly.
In the meantime, we've updated the following articles:
» "I'm unable to login over SSH IPv4 immediately after closing SSH" (registered users only) with a section for that solution: https://web.c-servers.co.uk/info/im-unable-to-login-via-ssh-over-ipv4-immediately-after-i-closed-ssh-what-to-do
» "I've opened a NAT port but it wasn't immediately effective" (registered users only) with a section just after the VPS restart that includes the solution: https://web.c-servers.co.uk/info/ive-opened-a-nat-port-but-it-wasnt-immediately-effective-what-can-i-do
And we've created a new article that essentially envelopes the symptoms and the resolution, called "NAT IPv4 Inbound is not working on my server. What to do?", which is now here and it is public so that other VirtFusion users at other providers can attempt the solution as well. The article is available here: https://web.c-servers.co.uk/info/nat-ipv4-inbound-is-not-working-on-my-server-what-to-do.
( chuckle ) Glad I could help.
Appreciate that but no need. I'm just happy to have helped out a community member.
Keep in mind that on latest ubuntu ssh port does not change with a sudo service ssh restart, needs to do some cycle on the network. Easiest is to reboot.
Hey teamacc. You're a dick. (c) Jon Biloh, 2020.