Question 1

Privacy policy

Accepted Answer

The short version

We do basic analytics but we will give clear easy to understand ways to disable at any time, and we self host all of this so it's not shared with a third party. We don't share data with anyone without user permission FIRST!

The long version

We will not sell or disclose your personal information to third parties without your consent except as otherwise provided in this Policy or our Terms of Service and Appropriate Use Policy. We may use information about who you are, where and when you browse our network, and how you use our network to provide you better service.

We respect your privacy and we do use a internal analytics service on our website, all data collected via this service is anonymized and original data is not stored. This data is not linked to an account if you have one, and is used to average how people find and use our services. This data is NOT shared with any other parties, this data remains private and is deleted after 30 days.

This Policy applies to customers who purchase and use our services and products in Canada. Collection, use, disclosure, and protection of personal information may be subject to different regulation outside the Canada.

NodeHost will revise and update this Policy as it is deemed appropriate, including, for example, if changes in the law so require. You should refer back to this page for the latest information.

Question 2

Setting up, and installing Wordpress

Accepted Answer

Wordpress is the most popular CMS on the internet, and today I wanted to show you how to Install Wordpress on NodeHost in a few steps and some info you will need along the way.

Launch a "container"

The first and big step is to launch a new container on NodeHost.

When you click on Create Container you will get a screen asking fo the type, just pick the default "PHP Running On NGINX/APACHE" (at the time of writing there is only one option). Then pick a location and a size for your site, the size and resources of your site can be changed later, no need to worry, pick the normal "$0.06 / 24hr" option as a default if you want. You should now see this, click create container, it will take a few seconds.

Setup your domain

Now just open your new container and go to the domains section in the side menu.

You will see 2 options, one is to set the domain you already own, if you don't own one you will need to buy one from a provider like Dynadot. Unless this is a testing site always set the domain you will be using and don't use the free myws.ca domain option as your first domain on the container (it cant be changed after).

Once y

Question 3

Account information API

Accepted Answer

Quick jump to call

${color}#96d35f - Info

This will fetch the account information for the user accessing the API like username, first and last name, email, account credit, and location information.

Request URL

https://api.nodehost.cloud/getaccountinfo

Parameters

None

More info

None

Response

{
  "data": {
    "id": "1232",
    "username": "apiuser",
    "first_name": "API",
    "last_name": "User",
    "email": "support@nodehost.ca",
    "email_alerts": "0",
    "email_recepts": "false",
    "email_updates": "0",
    "register_date": "1538862744",
    "type": "normal",
    "verified": "false",
    "referral": "0",
    "parent": "0",
    "credit": "56",
    "credit_referral": "0",
    "country": "Canada",
    "state": "British Columbia"
  },
  "system_connection": "true",
  "system_version": "v_55_65418c9",
  "system_user_id": "1232",
  "system_user_username": "apiuser"
}

${color}#96d35f - History events

Will return

Question 4

Terms and conditions

Accepted Answer

By creating an account you are agreeing to be bound by these Terms and Conditions of Use, all applicable laws and regulations, and agree that you are responsible for compliance with any applicable local laws. Breaking of our TOS rules or misconduct will result in deletion of any accounts and services. If you do not agree with any of these terms you can delete your account or not use our services. The materials contained in this web site are protected by applicable copyright and trade mark law.

Disclaimer

The content and use of the site are provided "as is". NodeHost makes no warranties, expressed or implied, and hereby disclaims and negates all other warranties, including without limitation, implied warranties or conditions of merchantability, fitness for a particular purpose, or non-infringement of intellectual property or other violation of rights. NodeHost does not warrant or make any representations concerning the accuracy, likely results, or reliability of materials on its Internet web site provided by users or NodeHost or otherwise relating to such materials or on any sites linked to this site.

Affiliates

NodeHost does not take any responsibility for affiliate services actions, and or the use of our services. We are providing services just like we would with any other customer.

Limitations

In no event shall NodeHost be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption,) arising ou

Question 5

Make Let's Encrypt work when using Cloudflare (ACME Challenge)

Accepted Answer

So first things first Let's Encrypt and Cloudflare are amazing, but just enabling the Cloudflare cloud and Let's Encrypt makes it impossible to auto renew domains. This rule change will allow you to auto renew with Let's Encrypt and make everyone happy.

This is because Let's Encrypt will do a ACME challenge on your domain on each renewal attempt, and with the default Cloudflare settings it will fail.

The simple solution is to enable a simple page rule on Cloudflare. This is a simple rule to disable SSL force on the ACME requests.

Now here is a copy of the rule, and just disable SSL.

*yourdomain.com/.well-known/acme-challenge/*

Question 6

Service level agreement (SLA)

Accepted Answer

We work hard to make our services work as smooth as they can with 99.99% uptime. But with scale sometimes things break, for example our cloud panel handles more then 35 million requests per month. So we want to make everything clear, on how we handle any downtime events.

Services

Containers

We will after any downtime event give all users on the affected node credit based on the amount of time that any container was down. We want you to host with us and not worry, having a site go down can be one of the worst things for your business.

System Downtime

We can't always say our panel will always be online as we are always making changes, but if something breaks when you are doing work, just send us a message and we will give you some credit. We know having things not work when trying to get things done can be frustrating.

Downtime reporting

We always report all downtime on our status site https://status.nodehost.ca. This page is fully automated and records data every 2 minutes for all servers. We will never edit the status page to remove past events.

Suspension and deletion of services

After a week of no balance on any account we do suspend all services that account uses like containers. 30 days after the service resource is suspended we do delete from our systems. We do send account alerts during all events, and this is fully automated.

Frequently Read Articles

Browse All Categories