Category Archives: Information

New Testing for speed comparisons

While we still continue to compare new client’s sites with Pagespeed. We have also put together a tool which will show us aggregated time/count/sizes of loaded websites. Below is a read out of latest as well as Pagespeed results:

 

Site  Response Time  Load Time  Download (First Load)  Page Speed Score  Cost
Original340ms3.34s4.24MB  64 /   50?
Compare300ms1.38s3.5MB  88 /   70150$~

MariaDB Server Updates

In an effort to avoid this last weekends downtime again. The Database server was taken offline for a few minutes while the logs were moved to a separate hard drive. Previously there was approx 60GB of space available for the logs. This has been more than enough for nearly 2 years. However it was not enough this last weekend. So we have moved the logs into their own separate 500GB hard drive.

We will also be putting in a pruning system to avoid this issue even if the logs reach that 500GB size without auto pruning.

As with any downtime clients are compensated with much more time as a credit on their account for the downtime. For this last weekends downtime every client recieved a 1 week credit to their account for their subscription based services.

Updates

It’s been some time since a post was made here on our blog. We have been extremely busy with a couple large projects. So busy we are actually expanding our office.

While we can’t release a whole lot of information at this time. We are also excited to announce that we will be Writing a modularized platform software package. From this package users will be able to add in blogs, forums, shopping carts, etc. All into the same system and all able to run multiple domains. While this will be no easy task and it will take some time to complete. We believe there is a great need for software of this calibre.

Right now there are great softwares out there for each individual task. But then you have to mesh them together, spend thousands of dollars getting them to look the same. Even then they still don’t work together they work alongside each other. A user on your forum can’t log into your shopping cart, same is true with the blog.

More about this project will be announced in the coming months as licensing and trademarking of the name are complete.

Shared Hosting

CLDMV is proud to announce that by February 1st 2014 we will be offering shared hosting on the same platform which runs our hybrid servers. While there will not be some features bundled into the system. Such as SSD, backup control, image compression, etc. It will still have the same system in the background.

This will allow customers to run non-critical applications for a reduced price. Pricing structure is still under consideration. However we will not be charging for bandwidth. Disk space charges are still up in the air.

Potentially we may charge a flat rate and give limits to the space available. We might also setup the same way we currently do with our Hybrid hosting and charge for space used. Which generally allows users to get their hosting for cheaper.

We will also be offering our Hybrid hosting clients extended backups which will automatically store their backups remotely. Pricing is still to be decided with this feature. It may roll out as a free feature.

Changes to pricing

As of September 1st 2014 CLDMV will be changing it’s future subscriber pricing. All current clients will remain with the same pricing structure which was available previously.

Namely the subscription based fees will be changed. Clear examples are below:

Current Subscription fee(s):

  • First Node: 100$/mo
  • Additional Node(s): 25$/ea/mo

Example: Client runs 4 website businesses. First website business is 100$/mo, the additional 3 are 25$/ea/mo.  The total subscription fee per month would be 175$/month.

Subscription fee(s) as of September 1st:

  • First and Odd number Node(s): 100$/mo
  • Even number Node(s): 25$/ea/mo

Example: Client runs 4 website businesses. First website business is 100$/mo; the the second is 25$/mo, the third being 100$/mo, and the fourth being 25$/mo.  The total subscription fee per month would be 250$/month.

The change to the subscription fee(s) were carefully considered and debated. Unfortunately CLDMV would not be able to operate at it’s current standards if the original fee(s) were kept and half or more of the nodes available per server were taken up from additional 25$/mo cost. So in order to maintain our current standards and stay in business we came to the above compromise in cost.

Unlike most hosting companies who will put 100,000+ users on a single server; use network drives, use mass storage drives, use cheap 100mbps lines, or do anything else to make more money. CLDMV does none of those. Our servers are restricted to 500 nodes per server. The only time network drives are used are for backups. The only time mass storage drives are used is for backups. All of our servers are either dual 1000mbps or dual 10gbps connections. Our servers are also using the newest top software to serve our client’s websites. We aren’t using “clunky” and insecure control panels to host our clients. So our clients get better speed and better performance.

Various Updates

CLDMV has opened a Development portion to our business. With this clients or anyone for that matter can contact us for web development. We are also partnered with 1stwebstudio for design projects. So all that’s left is to offer is domains, SSLs, SEO. While we do provide domains and SSLs already there is no automation in this process.

Also CLDMV has opened a Twitter and Tumblr account for people who wish to follow updates and posts through those forms of media. The blog site has also had some minor changes in design related to social networking.

Moving forward we excited to be able to provide most web related services to existing and new clients. We are still looking for a reliable and friendly service for SEO.

New feature for JS and CSS

Any website hosted with CLDMV can now automatically serve up concatenated JS and CSS files. For example:

http://cdn.cldmv.net/cldmv/min/cldmv/jquery/?base64.js,decode.js

The above URL is two separate files put together and minified as well. Now lets go over the portions of the URL:

The prefix of the URL (this is required in order to get the script to work.

The directory:

Then the marker to indicate the files you want to serve (this is required and never changes):

Then finally the files you want to serve under the above directory:

Each file is separated by a comma.

Normally to get both of these scripts to run you would include the follow urls:

Instead you can now just include:

Update: Since Chrome has an issue with double question marks I’ve reduced the code to only require a single question mark.

 

Current Status of Control Panel, security updates, and server updates

First lets start with a screen shot of the dashboard in progress for the control panel.

current-cp

Unfortunately Data prior to the 28th of May 2014 is a bit skewed. But as you can see we have plenty of navigation so consumers never get lost. We also show are currently showing all site traffic for all sites hosted under a specific user. Though with some crashes here and there we might put these charts on their own separate page per domain but still give the user the ability to view an all domain report as it’s setup right now (at their own risk).

Currently the theming for the charts is still to be completed. But we have the ability to show and hide specific points of data if we want, select a range of the data from the range bar below. And most importantly reset it all to dive into more data.

Updates outside of the control panel:

A lot of reforming to the back-end has happened in preparation of the control panel.

Security is always a concern when dealing with the online world. We have adjusted some security features. The control panel (unlike commercial panels today) will not actually be able to modify anything within the network per-say. What I mean by that is every command done through the control panel will actually hit a sub-system which allows or disallows access at that level. Which then hits the root system which can only run specific commands pre-written into the system. So unlike most control panels today where the code is on the forefront of the system, CLDMV’s back-end is segregated to many systems to prevent hacking. While data can be retrieved from the control panel anything which has to change the system will always be done through our set of sub-systems to insure stability and security.

Also it’s important to note there was a brief downtime of FTP log in and email receiving on 2014/05/31 at approx 5pm PST to 5:30pm PST. This was due to a mass restructuring of the back-end in order to support the new changes to come.

Log Parser V2

Prior to version 2 of he log parser the logs were simply dumped into the database for the past 60 days every hour. It was planned that Users could view these logs instantly through a control panel. But unless you really knew what you were looking at this data was sort of useless.

So we came up with V2 of the Log Parser. This parser parses errors and website access into tables which gives a lot more information about the logs. For example I can pull up a number of how many 404 errors happened on any site hosted with CLDMV on any day in the past 60 days. As well as any redirect. If I want to view all the 404 or redirects I can do so. This functionality will be included in the control panel asap.

Why did we do this?

Simple answer really. Analytics services can provide you with how many visits your site gets and a ton of data about this. However they only work on pages where their code is present. Since we can track on the server level we can provide a lot more data. This data helps website owners make critical decisions and code fixes where they see trends in their software.

“Why am I not being indexed by [insert name of search engine]?”

We hear this question quite often. Simply put we do not control how search engines index websites. But we can show you (now) that your site is being crawled by their bots. V2 of the log parser is also logs if the visit was a bot or not.

To show an example:

domainyearmonthdaybot_visitsbot_unique_visitsvisitsunique_visitsfourohfoursredirects
blog.cldmv.net201452720330500

The above results show this site’s basic stats for 2014-5-27. Visits and Unique visits are overall. So all we have to due to find human visits is subtract the bot visits from those numbers.

yearmonthdaydomaintimestampipreal_ipsslbotajaxresourceurlresponse_codevisitrefererbytesgzip_ratiolog_entryuser_agentrequest_typerequest_versionremote_user
2014528example.com140124881166.249.73.71110php/exampleurl.php30213166.249.73.71 - - [28/May/2014:03:46:51 +0000] "GET /exampleurl.php HTTP/1.1" 302 31 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-" "-" "https" "-"Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)GETHTTP/1.1

Above is an example of all the data available through our Log Parse V2.

DNS Mail Settings

While most people never have an issue with their emails. One of the most basic ways to help prevent being black listed and prevent spam from being spoofed from your domain name is to set up SPF records.

Here is http://cldmv.net/ SPF record:

We’ll go over what each of the portions mean now.

v=spf1

This specifies what version the SPF is. Currently the only version supported is spf1.

mx

Specifies that email originating from MX records of the domain name may send email as well.

ptr

Allows any sub domain of the domain to send out email. This can be spoofed but not very easily. Generally someone would need to have access to your DNS records to change this. Also if you have an A Record with “*” pointing to your server this helps prevent this as well.

include:cldmv.net

Specifies that any domain ending in cldmv.net may send email for the domain as well. Generally this would be for your hosting provider to determine based upon their setup.

-all

Notice the negative sign. It tells servers which follow SPF to reject all emails which do not meet the previously set rules.

Anyone hosting email with CLDMV should set their MX record to mx.cldmv.net as well as add the following txt record in order to insure emails are sent and recieved following SPF.