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.
iHostART - 5.69$/yr 50 GB SSD&512 MB VPS DMCA Ignore & Leave invoice no. and duble ram 1x IPv4 NAT
This discussion has been closed.

Comments
I already got the IPv6 and double RAM, but the IPv6 cannot be connected and ping return 'Destination unreachable: No route'.
Yeah, me too. Ipv6 showed in panel but can’t use it
me too
Well, At least there is some progress.
Hello everyone , all new orders receive free upgrade for 512 MB Ram
About upload speed & IPv6 , we try for make work correctly
Thanks!
Regards,
Calin
Please double the ram for #1982
Invoice #2060
Thank you!
Invoice #2067
Thank you!
How does port forwarding work here? Inside the VPS, the ssh port was 22, but outside it's something else. How do I see the port mapping for other services that I'll setup here?
Has anyone tried using mosh with this? I'm not sure how that'll work, you need to specify one port to the mosh server and one to the client somehow
Invoice #2062
Thanks
you need to change the ssh port to one that is forwarded. Normally, the initial setup has the ssh port set on the one that is forwarded, but if you replace dropbear with ssh you will need to change manually in sshd_config to some port OTHER than the dropbear one otherwise ssh will not start. After it started and you connect to ssh, you can remove dropbear and change again the port to the old dropbear one.
If you choose centos you get openssh, not dropbear. Not sure why another distro on this platform would get dropbear instead.
Debian 10 does, but I am also not sure why. 512 MB should be a lot for SSH, it makes sense in 128 or less, perhaps.
You do not need to change the SSH port. SSH must remain on port 22 to work on the SSH port within the panel. This is forwarded/natted on the host. You can however change your SSH port to one of the other 20 ports that are assigned.
Don't change ssh port from 22. It's redirection is handled by NAT and it is not something you can change in OS itself. The public port for ssh was sent to your email.
For other stuff, you have 20 public ports. There are no default firewalls in this VPS so you can simply set your service to listen on e.g.
0.0.0.0:15003and it would be available on that port.For example for mosh you can use:
mosh --ssh="ssh -p 15020" root@vps_IP -p 15001(if 15000 to 15019 are available for you)Invoice #2072
@Calin also have invoice Invoice #2062 .
Can I combine them into one?
I have no connectivity to the outside. I messaged you on Discord. Please fix it, or I am getting something else.
Ign:1 http://archive.canonical.com/ubuntu jammy InRelease
Ign:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Ign:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:1 http://archive.canonical.com/ubuntu jammy InRelease
Ign:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Ign:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:1 http://archive.canonical.com/ubuntu jammy InRelease
Ign:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Ign:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Err:1 http://archive.canonical.com/ubuntu jammy InRelease
Temporary failure resolving 'archive.canonical.com'
Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
Building dependency tree... Done
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-security/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/jammy/InRelease Temporary failure resolving 'archive.canonical.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Try running
echo nameserver 8.8.8.8 > /etc/resolv.conf. Once that works, you can use the solution here to fix it permanently: https://askubuntu.com/a/1401016/1095763Yes! That fixed it. Thanks very much!
so so so terrible network......
the ping is terrible indeed, but I never expected unlimited traffic at bigger speeds.
You're paying $5 for your VM, don't expect something good to come out of it
When IPV6 🥹
Invoice #2081
Thank you!
Invoice #2092 thx
My bad, I was not clear enough.
I mean, while in the process of changing from dropbear to sshd, if you first remove dropbear then you lose access and if you leave ssh on default port 22 then it won't start as the port is already allocated to dropbear.
Ideally, in order to make sure you don't make some mistake, you should install sshd on a different forwarded port while still having dropbear on port 22 and only change after ssh is working on another port, i.e. login on ssh on the new port, remove dropbear, change sshd_config back on port 22, reload, done.
All that is moot once we have IPv6 :P All ports will be working, so, please hurry up
For Invoice #2014, I had mentioned the invoice number here, but my VPS was still activated with 512MB RAM.
Anyone else with the same issue?
That is normal, the extra ram is added later.
is this legit? I don't know this provider? How is their uptime? Anyone who already purchase? Is the uptime 90% above? Is there a slot left?
Invoice #2099
Tanx