New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
So what happens if you spin up another VPS in the same/different location?
If you created the VPS from the launch instance wizard and specified the number of IPv4 to be assigned, then the panel will not assign an Internal(private) IP to the VPS, unless the private IP pool is created without checking the "internal" checkbox.
AFAIK serial console connects you to the main server, not the VM. Than Virtualizor will just mirror everything thats sent from the VM.
You might want to update your ticket regarding this since QH may suspend you for using un-purchased IPs.
@Ympker also, remove the screenshot link as it has your public ip
This time I acctually got an internal ip (cant ping it) of the block 192.168.33.x which I can easily relate to a public ip using https://quadhost.net/account/knowledgebase/5/Find-your-IPv4-NAT-Instance-Public-IPv4-Address.html
For some odd reason my london vps got a non shared ipv4 adress it seems.
I created it from the launch instance wizard but the second time I used it I got assigned an internal ip so it does work fine I guess. And I can't manage the ip pool. That being said there is no other way for me to create a vm than to acctually use that "Launch Instance" option.
@sanvit
Trying to remove it but let seems to be a bit buggy
Edit: Should I just try to delete and re-create the vps with the public ip and see if I receive a nat instead to avoid using someone else's ip? Anyway updated the ticket^^
It seems that each time I use ldn10-uk location I get a public Ip that can be pinged. Using other locations such as GRA gets me an internal ip.
No, rebuilding VPS will not solve it, it will assign the same IP.
Yeah I destroyed it and created another but it has a different ip of the same block :P
Yes, a new VPS will get a new IP if you have more than one IP in the Pool.
I didnt read that correctly I thought you would be rebuilding the same VPS.
I just want to thank you. You aren't coming off as rude or anything from my perspective. Not sure why other LET members have severely been hurt by you.
I for one appreciate that LET isn't spammed with help tickets....
No worries I was not being too detailed either :-)
I can see your ticket has already been replied to.
You also want the i83 team since its a i-83.net product.
Yep everything is going smooth now
Basically all the confusion was caused by this public IP I have been assigned due to some bug. Everything is as should now. Thanks for the catch-up!
You can randomly get public IPs, I'd reported it to @quadhost more than a week ago and it's apparently a virtualizor issue in their specific configuration.
Tried all locations and about 6/10 gave me a public IP. Reported them all :-)
@Ympker Did you open a ticket to have your bundle activated or does that happen "automatically" after some time?
It does happen "automatically" after ~ 2 days.
As far as I know Virtualizor does not support Private IP allocation from Cloud panel unless they are added in Public IP Pool by the Admin.
@quadhost Do you know what's going on at @i83 at the moment? I ordered (and paid) a Resource Bundle which has not been provisioned yet. It's fine if they need more time, but some kind of information would be helpful...
My resource bundle I ordered 2 weeks ago took about 3 days to provison. Be advised that 6 out of 10 resource bundle locations dont work atm as you are assignsd public ips instead of internal ips. Ive reported that 3 days ago but no update on the situation.
NAT locations you cant use atm due to this:
NATNC
NATSG
NATBEG
NATNDK
NATVAR
NATPUN
My bundle has been provisioned few minutes ago... took them five days in my case.
Hope they fix the private/public IP issue soon.
Glad to see someone else has this issue. Coming near 2 weeks and no ticket response. Getting public IP's instead of Private IP's. I'm just gonna use these IP's. I gave them ample time to respond.
I may acctually do the same as @quadhost and @i-83 do not respond on the tickets for me either.
Use it, but don't depend on it... you may lose them anytime. @quadhost is very strange, bursts of activity for a day or two .... and then silence.
8balls don't come often at $3/yr.
Seems they at least put it on their network issue tracker.. https://quadhost.net/account/serverstatus.php
>
>