@pluto said:
Finally, my natvps is online again after 4 days. The support ticket of vpsid 6180 must not be handled anymore.
You can close your ticket yourself
I have just expressed my happiness when I saw my site online again after several days suddenly offline. Another sentence is only extra info, I will do it when I have address and right password in my head.
edit 3: well it's not fully working. but it's a NAT VPS, might just wait another week for support ticket.
ssh to ipv6 is working.
ssh to ipv4 with correct NAT port is not working anymore.
@MallocVoidstar said:
Was in the middle of making a ticket over PL network not working for ~2 days when it came up like two minutes ago. I should file tickets faster.
@yoursunny said:
zrh1-che
nyc1-usa
IPv6 VPS network abnormal, will it ever be fixed?
zrh1-che:
cannot ping IPv6
Virtualizor shows 🔴 Offline
click ▶️ gives: 1) The operation could not be completed
nyc1-usa:
cannot ping IPv6
NATVPS is IPv6 primary service so we expect IPv6 to be working.
@pluto said:
Finally, my natvps is online again after 4 days. The support ticket of vpsid 6180 must not be handled anymore.
@Abd said:
There is an ongoing issue with the nat vps control panel due to which OS reinstallations are not possible.
This is being worked upon , and expecting resolution in 48 hours,
Meanwhile existing services are online & unaffected.
here:48hours, status page showed in 36 hours. In fact, it's been more than 3 days/72 hours. Any update? Or give us a new ETA?
Status Page:
NAT VPS - Control Panel malfunction
An ongoing issue with the nat vps control panel has caused OS reinstallations to become unavailable. Primarily affects new services & orders.
This is being worked upon , and expecting resolution in 36 hours,
Existing services remain online & unaffected.
Date Created: 2022-08-10 02:24:22 (3 days ago)
Last Updated: 2022-08-10 02:27:57 (3 days ago)
You'all are too kind sirs. I am extremely sorry for the inconvenience caused over the past week.
Nat vps come with limited support. BUT that does not mean service can be offline. I work my best to provide a fully working service and will make sure whatever be the issue is resolved.
If the issue is still reflecting in your service, you're very welcome to make a ticket. We'll do our best to resolve it asap.
If the issue is resolved , you may please close the ticket on your end, as that helps reduce the load & will be greatly appreciated on our end.
edit 3: well it's not fully working. but it's a NAT VPS, might just wait another week for support ticket.
ssh to ipv6 is working.
ssh to ipv4 with correct NAT port is not working anymore.
@MallocVoidstar said:
Was in the middle of making a ticket over PL network not working for ~2 days when it came up like two minutes ago. I should file tickets faster.
@yoursunny said:
zrh1-che
nyc1-usa
IPv6 VPS network abnormal, will it ever be fixed?
zrh1-che:
cannot ping IPv6
Virtualizor shows 🔴 Offline
click ▶️ gives: 1) The operation could not be completed
nyc1-usa:
cannot ping IPv6
NATVPS is IPv6 primary service so we expect IPv6 to be working.
@pluto said:
Finally, my natvps is online again after 4 days. The support ticket of vpsid 6180 must not be handled anymore.
@Abd said:
There is an ongoing issue with the nat vps control panel due to which OS reinstallations are not possible.
This is being worked upon , and expecting resolution in 48 hours,
Meanwhile existing services are online & unaffected.
here:48hours, status page showed in 36 hours. In fact, it's been more than 3 days/72 hours. Any update? Or give us a new ETA?
Status Page:
NAT VPS - Control Panel malfunction
An ongoing issue with the nat vps control panel has caused OS reinstallations to become unavailable. Primarily affects new services & orders.
This is being worked upon , and expecting resolution in 36 hours,
Existing services remain online & unaffected.
Date Created: 2022-08-10 02:24:22 (3 days ago)
Last Updated: 2022-08-10 02:27:57 (3 days ago)
You'all are too kind sirs. I am extremely sorry for the inconvenience caused over the past week.
Nat vps come with limited support. BUT that does not mean service can be offline. I work my best to provide a fully working service and will make sure whatever be the issue is resolved.
If the issue is still reflecting in your service, you're very welcome to make a ticket. We'll do our best to resolve it asap.
If the issue is resolved , you may please close the ticket on your end, as that helps reduce the load & will be greatly appreciated on our end.
@PineappleBox said:
I cannot forward any TCP ports, but only on a single one of my NAT VPS's. Any chance you could take a look? (Ticket #3758458)
TCP ports are forwarded by default & no additional action is required on your end, please see the service activation email.
'domain forwarding' option is only meant to be used for ports 80 / 443
Comments
Scroll up
waw1-pol
fsn1-deu
nyc1-usa
lax1-usa
NAT VPS network abnormal , how long will it take to fix?
Network i.e. the control panel ? please recheck it is fixed.
@Smilence control panel is up now
there are still issues. ticket #1735888
well it just worked xD
edit 3: well it's not fully working. but it's a NAT VPS, might just wait another week for support ticket.
ssh to ipv6 is working.
ssh to ipv4 with correct NAT port is not working anymore.
@Abd when will the code work again ?
Was in the middle of making a ticket over PL network not working for ~2 days when it came up like two minutes ago. I should file tickets faster.
zrh1-che
nyc1-usa
IPv6 VPS network abnormal, will it ever be fixed?
zrh1-che:
nyc1-usa:
NATVPS is IPv6 primary service so we expect IPv6 to be working.
Finally, my natvps is online again after 4 days. The support ticket of vpsid 6180 must not be handled anymore.
You can close your ticket yourself
I have just expressed my happiness when I saw my site online again after several days suddenly offline. Another sentence is only extra info, I will do it when I have address and right password in my head.
You'all are too kind sirs. I am extremely sorry for the inconvenience caused over the past week.
Nat vps come with limited support. BUT that does not mean service can be offline. I work my best to provide a fully working service and will make sure whatever be the issue is resolved.
If the issue is still reflecting in your service, you're very welcome to make a ticket. We'll do our best to resolve it asap.

If the issue is resolved , you may please close the ticket on your end, as that helps reduce the load & will be greatly appreciated on our end.
It's working now. Thank you very much.
All NAT VPS back online, thanks!
How long will it take to solve the problem of NAT reinstallation failure?
Still can't access my nat's control panel. But it's just a nat, so I don't care much.
This is resolved today morning, kindly recheck.
Please open a ticket we won't know otherwise can't help. Hope you get that sorted
Still no, please check the work order 5969123.
10.37.126.51

Reloading fails all the time, could you help me reload it?
Can you share your ticket here? Of course, please hide your root password and other information.
The key information has been hidden, thanks for reminding me.
Check now it should have resolved.
I cannot forward any TCP ports, but only on a single one of my NAT VPS's. Any chance you could take a look? (Ticket #3758458)
@Abd when will the code work again ?
Yes, thank you.
sounds like a lot a of problems going on
TCP ports are forwarded by default & no additional action is required on your end, please see the service activation email.
'domain forwarding' option is only meant to be used for ports 80 / 443
@Abd
No offers for Aug XV ?
unfortunately not until I solve all these pending tickets
good thing is I expect them resolved by evening.
I don't mean to add more pressure, but....
Is there any ETA on newly purchased servers being setup? I purchased one in Poland yesterday.