Hosting Websites on Bare Minimum VPS/Dedicated Servers

TCNHosting – 3GB and 6GB VPS Specials – As low as $20 a year!

Tags: , , , , , , , , , , , , Date/Time: June 13, 2019 @ 2:00 pm, by Frank Williams

TCNHosting is back with a flash sale for the community. They have been featured here once before, so we hope you enjoy what they are offering to us today! As always we’re interested in hearing your feedback so feel free to comment in the comments section below.

You can find their ToS/Legal Docs here. They accept PayPal, Credit Cards, Debit Cards, Alipay, Bitcoin, Litecoin, and Ethereum as payment methods.

Here’s what they had to say: 

“Here at TCNHosting, we have built our hosting company based on our customer’s values. Since day one we kept our servers secure and reliable. We know how important it is for customer’s to keep their sites always available.
Whether you are facing issues with payments or require technical assistance we are always available to help you in the process.

You’ll also be pleased to know that all of our servers are powered by SSD technology, which means no spinning drives for better reliability and performance for your applications! We look forward to contributing more to the LowEndBox community in the future and hope you find one of our LEB specials below beneficial for your VPS hosting needs!”

Here’s the offers: 

3GB-SSD-VPS

  • 2 CPU Cores
  • 3GB RAM
  • 30GB SSD Storage
  • 3TB Monthly Transfer
  • 1Gbps Port
  • OpenVZ/SolusVM
  • 1 x IPv4 Address
  • $20.00/yr
  • [ORDER]

6GB-SSD-VPS

  • 4 CPU Cores
  • 6GB RAM
  • 90GB SSD Storage
  • 15TB Bandwidth
  • 1Gbps Port
  • OpenVZ/SolusVM
  • 1 x IPv4 Address
  • $40.00/yr
  • [ORDER]

NETWORK INFO:

Dallas, Texas, USA

Test IPv4: 192.3.237.150
Test file: http://192.3.237.150/100MB.test

VPS Nodes – Host Node Specifications:
– Intel Xeon E3 Series
– 32GB DDR3 RAM
– 4x 1TB Samsung Enterprise SSD’s
– Hardware RAID-10 powered by LSI MegaRAID
– Dual 1Gbps Network Uplinks

Please let us know if you have any questions/comments and enjoy!

8 Comments

  1. Erik Ashfolk:

    Hi , (1) Will you (VPS-Provider/Reseller) PLEASE INCLUDE these below REQUESTS with any of your above KVM VPS (VIRTUAL-private-server) SERVICE-instance offer (for the same (advertised) price) ? and i have few extra QUESTIONS/inquiries :

    (2) Full Root Access of VPS available to client/customer user ?

    (3) IPv6 net:
    (3a) will you be able to add/include 1 native /64 IPv6 “NET”/”subnet” resource ?
    ( one /64 IPv6-net/subnet/range has 18-QuinTillion (18QN) IPv6-addresses . 1-Billion has 9 zeroes after 1 , & 1-Quintillion has 18 zeroes after 1 . According to IANA/IETF/etc an end-user/end-site should have a minimum /64 IPv6 subnet, and standard recommendation is /48 for business end-users & /56 for residential end-users ).
    (3b) do you have/use native IPv6-address pool or tunneled IPv6-address ?
    ( my project need internet-connected native /64 IPv6-subnet/range for our server-apps/scripts which will run inside your provided VPS service-instance ).
    (3c) if you cannot provide 18QN x IPv6-Addresses ( a /64 IPv6-subnet/range ) , then can you provide atleast a smaller amount: 281-Trillion x IPv6-Addresses ( 281TN = 281Trillion IPv6 addresses are equivalent of one /80 IPv6-subnet/range ) ? or even-smaller 4-Billion x IPv6-Addresses ( 4BN = 4Billion IPv6 addresses are equivalent of one /96 IPv6-subnet/range ) ?
    ( our project cannot work with a IPv6 range that is smaller than /96 )

    (3d) and for other LEB user’s sake, can you add at-least 30xIPv6 addresses ?

    (4) my project needs either “PTR/RDNS-setup-API-SUPPORT” or “NS”-pointer:
    (4a) Currently do you support setup of PTR/RDNS DNS-record for IPv4 & IPv6 address(es) manually thru your VPS CONTROL/MANAGEMENT PANEL or via opening a support-ticket ?
    (4b) does your PANEL have API SUPPORT for VPS-customer’s server-apps/script(s), so that app/scripts can setup IPv6-adrs’s PTR/RDNS instantly & by itself ?
    if your panel’s API can allow (our project’s) server-apps/scripts (running inside your provided VPS) to setup IPv6-adrs’s PTR/RDNS,
    then (for now) i/we do not need any “NS”-pointer toward our NameServer (which will be running inside your provided VPS) , as we can adjust our project’s server-apps to use your provided API to setup IPv6-adrs PTR/RDNS instantly.
    (4c) (but,) if your PANEL does NOT have PTR/RDNS setup API SUPPORT for VPS-customer’s server-apps/scripts , then we need to ask/request you , if you can add a “NS”-pointer (dns-record) in the provided /64 IPv6 net’s reverse-lookup-zone , & point toward the NameServer that will be running inside your provided VPS ?
    The file where you (or your PANEL) usually add “PTR”/RDNS dns records for IPv6-addresses , exactly in that reverse-lookup zone file , you will have to add just two dns lines: one “NS” dns record & one “CNAME” dns record , then VPS-customer can use their server-apps/scripts to further configure their NameServer (DNS Server: BIND/named or any other standard DNS Server) to setup PTR/RDNS for any IPv6-addresses from your provided /64 IPv6 NET, inside your provided VPS.
    if you agree then i will give/send you those 2 lines of codes, then you can further evaluate/adjust/suite/apply them.
    ( Our project’s server-apps inside (your provided) VPS service-instance will need to setup (add/delete / modify/query) PTR/RDNS dns-record(s) for any of those provided IPv6-address(es) very-quickly + instantly at any random moment for our (any/new) users . Manually setting-up each IPv6-address’s PTR/RDNS one by one for our project’s each new user in beginning (during our startup period) will be ok as now we do not have much users , but in the long run such will not work for us , it will not be convenient when later we will have more users & we will definitely need more automation ).
    (4d) do you have any future plan to build API SUPPORT for your related PANEL so that VPS-customer’s server-apps/scripts can setup PTR/RDNS instantly ?

    (5) Privacy-Rights, Privacy-Laws:
    (5a) do you (and does your USP (upstream-SP(service-provider) or upstream-ISP, both) respect+follow+uphold People+client+customer’s ( & their-user’s ) PRIVACY-RIGHTS ? ( USA’s Fourth + Ninth + First + Fourteenth Amendements, etc . United Nations’s UN-UDHR article-12 , UN-ICCPR’s article-17 , UN-GA-res-68/167 , UN-GA-res-69/166 , UN-HRC res 28/16, etc . CoE ECHR article-8 , EU GDPR , California article-1:sec-§1 , Florida article-I:sec-§23 , etc ) , and
    (5b) Do you (and does your USP) follow data+person Privacy+Protection+Security LAWS ? ( Laws similar to EU+EEA’s GDPR (EU-2016/679), etc ? Laws similar to California(Cal)-USA’s SB-1386 civil code §§ 1798.29, 1798.82, 1798.84, 1798.83 (SB-27), 1798.81.5 . Cal-Gov §6267, Cal.civil §1798.90 . Cal-Lab §980 . CalOPPA (Cal-Bus-&-Prof) §§ 22575-22579, §22948.20 . CCPA (AB-375 / SB-1121) §§1798.100 ? Laws similar to Illinois 820 ILCS 55/10, 105 ILCS 75/10, 105 ILCS 75/15 , Florida-§501.171(2) , Virginia §40.1-28.7:5, §23.1-405, VA-HB-2081 , Wisconsin-§995.55 , Washington article-1(§7) , Montana article-2(§10) , etc ? USA states have more than 600 laws . USA has around 12 Federal PRIVACY-LAWS which have substantial “opt-out” requirements. etc . )

    (6) security & protection of data & code, network, etc:
    (6a) do you ( or does your USP (upstream SP(service-provider) ) or upstream-ISP ) AUTO SEND any ( root / vnc / ssh / VPS control-panel / management-panel / resource-mgmt-panel / web-portal / support-ticket-communication ) message with PASSWORD ? into any customer’s/client’s email-address or into any of your staff’s/admin’s email-address , thru / via OPEN EMAIL ? when any client/customer Orders VPS or Reinstalls OS or Changes PASSWORD, etc ? ?
    if you ( or your USP ) do include PASSWORD in any ( OPEN / unEncrypted ) message/EMAIL then you ( and your USP, both ) are violating various laws , and i also strongly oppose such activities , PLEASE fix your ( and push your USP to fix their ) software + bugs + policies , by-default do-not auto send any PASSWORDs unless a specific user gives very specific clear consent or unless a specific user has chosen a very specific option by himself/herself/themselves . Silence/entrapment/coerce/assumption is not Consent.
    (6b) Do you (or Does your USP) allow clients/customers to setup the VPS ROOT-PASSWORD in the ( HTTPS based secure ) VPS ORDER webpage ? if your (or if your USP provided) web system do that, then you are following at-least one good security+protection policy+law . Please make sure your software/system does-not send this PASSWORD over OPEN EMAIL, even for once.
    (6c) Do you ( or Does your USP ) share any ( non-Public or Private or Personal ) data/code from provided VPS with anyone else or with any 3rd-party ? when you ( and your USP, both ) do-not-share , and when you ( and your USP, both ) guard/protect all data/code , only then , ( both of ) you are upholding People’s+User’s+Client’s+Customer’s Privacy-RIGHTS , and following Privacy + Protection + Security, etc Laws.

    (7) TUN/TAP/PPP enabled/available ? Debian v9.9 (64bit) (minimal) or higher version available or possible ? VNC/SSH access ? Virtualizor access ? is it OVZ7 & Docker supported ? CPU passthrough & AES enabled/available ?

    – – – – – – –

    EXTRA-NOTES:

    * When any EMAIL’s content is NOT-Encrypted With GPG/PGP/SMIME (keys/certs) Then that EMAIL is OPEN EMAIL.
    * Data passing thru HTTP or FTP is OPEN.
    * Data passing thru HTTPS is secure/ENCRYPTED . HTTPS is Encrypted with CA validated certificates/keys.
    * Data passing thru SSH is secure/ENCRYPTED . SSH is Encrypted with PKI keys.
    * Data passing thru FTPS, SFTP, etc are secure+encrypted . When you have option to use both, prefer FTPS (as it uses FTP over/thru SSH).
    * Correct FCrDNS, PTR/RDNS, WHITELISTED-IP, (SPF), etc are necessary for MAIL-server(s) to send-out EMAILs into the “INBOX”, or else EMAILs are either REJECTED or placed into SPAM/TRASH folder.
    * DNS is OPEN . DNS queries & answers can be secured by using DoH (DNS over/thru HTTPS) or DNS-over-TLS, etc . DNS answer’s authenticity can be verified by using DNSSEC.
    * Certificate’s authenticity can be verified by CA root certs and also by using DANE+DNSSEC . Server’s SSH public Key(s),etc can be verified by DNSSEC.
    * VPS (virtual-private-server) , is a SERVICE-instance, & provided /64 IPv6-net is a resource, etc, and all of those remain with you (VPS-Provider) , inside your own DataCenters/Servers ( or in your upstream-service-provider/USP’s/ISP’s DataCenters/Servers ) . A remote Client/Customer/User with a remote access into that VIRTUAL-server in your DataCenters/Servers/premise , cannot take your provided any service/resource away from you & move into another service-provider/location . So adding those 2 lines of (NS & CNAME) dns-records in your DNS NameServer is NOT A REAL DELEGATION or SUB-DELEGATION . You did not really transfer (full) control of your service+resource to another person/entity who can or able-to move-away from you with your provided resources , into another location (or with another VPS-Provider) as their own service/resource . Adding those 2-lines of (NS, CNAME) DNS codes (or adding PTR/RDNS DNS-Codes) is just a temporary attachment of a service+resource for the sake of providing SERVICE for a VPS(virtual-private-server) which remains with you inside your own DataCenters/Servers . But we named/call it “DELEGATE” for the convenience of identifying it’s functional (partial-)similarity , but in reality no real TRANSFER occurred , no real DELEGATION occurred . You are merely/simply providing/adding / attaching few service(s)+resource(s), etc in your/provided VIRTUAL-server SERVICE-instance inside your own DataCenters/Servers , for a remote Client/Customer/User with a remote-access . This allows a remote client/customer to setup/add “PTR”/RDNS, etc various DNS records for the any of the provided IP-address, by client/customer themselves, inside the provided VPS, and setup/modify the service instantly with any desired/necessary TTL(Time-to-Live).
    * When (domain-registrar’s) DNS-NameServer-1 points a domain-name’s forward-lookup zone toward another DNS-NameServer-3, OR when (IP-address-range (aka “net”, “subnet”, “block”) owner’s/VPS-Provider’s) DNS-NameServer-2 points an IPv4/IPv6 address-range’s reverse-lookup zone toward another DNS-NameServer-3 , then DNS-NameServer-1 & DNS-NameServer-2, both serves/handles much much less (forward & reverse DNS lookup/answer) DNS traffic/packets which are (configured-to-be) served/handled by the DNS-NameServer-3 for the specific domain & provided IPv6/IPv4 address-range . And less DNS traffic/packet means that DNS-NameServer-1 & DNS-NameServer-2, both consumes/uses / handles/serves less DNS data , So DNS-NameServer-1 & DNS-NameServer-2, both also pay less $ for total data used . Client’s/Customer’s DNS-NameServer-3 serves/handles it’s own + all (forward+reverse) DNS traffic.

    June 13, 2019 @ 6:11 pm | Reply
  2. Deckard:

    Their website design looks exactly like AlphaRack’s web which was just closed yesterday! What a coincidence, LOL!

    June 14, 2019 @ 4:15 am | Reply
  3. Deckard:

    Their order/billing page design looks exactly like AlphaRack’s which was just closed yesterday! What a coincidence, LOL!

    June 14, 2019 @ 4:17 am | Reply
  4. Derak:

    That offer appaers to be “shared hosting”, not a vps.

    June 14, 2019 @ 7:16 am | Reply
  5. Jose:

    What version of OpenVZ/Virtuozzo are you guys running?
    Does it support the newer libc6 so that we can use newer Ubuntu releases like 18.04 LTS?
    I don’t see the option in the dropdown box.

    June 16, 2019 @ 3:43 pm | Reply
  6. Piero:

    It doesn’t look like alpharacks E ‘alpharacks these scammers are opening sites one behind the other one of which PskHosting and god knows how many others to continue to defraud users. I reserve the right to report this fraudulent behavior to lowendbox. If they allow these people to continue publishing offers, I don’t think they will consider buying lowendboxes in the future.

    June 20, 2019 @ 11:45 am | Reply
  7. MPG:

    All these sites look the same to be honest. I dove in an ordered 2 VPS not realizing these were VZ servers. Which had limitations on kernel upgrades I would have to do. Ended up finding an alternative way to do to install and this dudes were awesome. While I was getting all pissy, they totally helped out and got me situated. So far service has been good we’ll see in the long run. But I’m digging it! Kudos to TCN! and Thanks for the great deal!

    June 23, 2019 @ 7:40 pm | Reply
  8. Bohdan:

    The service seems to be decent – they got back to my ticket in under 12 hours, but for web hosting the server keeps going down. It was too good of a deal.

    July 8, 2019 @ 9:25 pm | Reply

Leave a Reply

Some notes on commenting on LowEndBox:

  • Do not use LowEndBox for support issues. Go to your hosting provider and issue a ticket there. Coming here saying "my VPS is down, what do I do?!" will only have your comments removed.
  • Akismet is used for spam detection. Quoting webhostingtalk.com URL seems to get binned consistently here, but I do peek into the spam box frequently to publish those comments.
  • Use <pre>...</pre> to quote the output from your terminal/console, or consider using a pastebin service.

Your email address will not be published. Required fields are marked *