tgonhawk1

Members
  • Content Count

    89
  • Joined

  • Last visited

  • Days Won

    4

tgonhawk1 last won the day on December 27 2017

tgonhawk1 had the most liked content!

2 Followers

About tgonhawk1

  • Rank
    Advanced Member

Recent Profile Visitors

6,754 profile views
  1. From what I understand, for shared hosting, each cpanel license (or sub-license) will be charged around $0.10 - $0.20/month going forward, assuming servers which typically host several hundred domains, are over any pre-packaged limits. Since that is $1.20 - $2.40 per year, it does not represent a huge increase for each one. It's up to HawkHost, given the ultra-competitive nature of the hosting business, if they want to bear that cost, pass it along to all customers, or only charge it on new accounts. In aggregate, it will matter more to Hosts than to customers who would see a charge of $25-50 per year go up by a dollar or two. Reseller, VPS, and Dedicated hosting accounts are another matter altogether, since that dollar or two can have a significant multiplier on it.
  2. There is now a second thread with more information on this topic on the Hawkhost forums. See the "Suggestions" section. LINK Also a blog post. LINK
  3. I read today on lowendtalk.com that cPanel is making a big change to their pricing. Never having looked into this before, I don't know what it was before. My question is this: what effect will this have on Hawkhost pricing? It seems to me that at $2-3 per month for shared hosting, a hike in the cost of a cPanel license might eat into already tight margins. I understand this is quite new and may take a while to sort out, and, it would seem, the primary impact would be on Reseller accounts, but once you do figure it out, it would nice to know its down-the-line knock-on effects. Also, I see that on the https://cpanel.net/pricing/page ("page" is not part of the link) they mention Cloud Linux and Litespeed. Does cPanel own those, too?
  4. Since this a question of perhaps general interest, I'll ask it here: Is it possible for a shared hosting user to read the cpanel webmail access logs for his site? On the cpanel forums, the location is identified as > cPanel, WHM, and Webmail activity is logged to /usr/local/cpanel/logs/access_log. > The ability to review this log file is restricted to the root user. ... The latter part appears correct since "ls /usr/local/cpanel" gives permission denied, ... and "ls /usr/local/cpanel/logs/" gives "no such file or directory. Is there a way to make this accessible? Perhaps not, if everyone's are all mixed together. Access from a POP client would also be useful - but that might evade even any generat cpanel logs.
  5. The hammer eventually did drop, and, having switched to Roundcube, let me just say, overall, RC is better. There are a few things I preferred about Squirrelmail, but there are more ways in which RC outperforms, making those pluses outweigh any minuses. I do use it zoomed-in one notch - the default font settings are just too small for these tired old eyes, and that overcomes my biggest problem with it.
  6. Here are some examples from the Hawkhost.com home page: These are reduced from full size. This is the original presentation - gray color, titillium-weblight font: This one changes the text color to black: This one changes the font to Verdana, and boosts the font-weight on the next and previous markers, which are VERY hard to see without that. And for good measure, this appears just below the reviews section: gray text on gray background!
  7. The prospective client specifically asked if there is a paid migration service. He will no doubt be pleased to learn that that service is included in the price of hosting.
  8. Given that this cPanel update addressed security problems, https://news.cpanel.com/tsr-2019-0002-announcement/ and https://news.cpanel.com/tsr-2019-0002-full-disclosure/ I can understand the urgency of getting it installed. cPanel identifies their releases with a Major number, a Minor number, and a Build number. These change in increasing order of frequency. If a new build, or a new minor release is made which doesn't impact users, there is no need to issue notices. When the Major part changes (as in 76 to 78), which is not very frequent, then it would nice to know why (for example) my webmail page suddenly stopped working from one minute to the next, or what new features are now available. As I read it, they released updates to both version 76 (the previous version) and version 78 (the new version). It appears to me that it was your choice to advance to version 78 at this time (which is your right to do), and since this was a case where there was a change affecting users, notice would be appropriate. Other points: I, for one, appreciate that you " actually don't update as often and frequent as many other providers unless we deem it necessary " (if it ain't broke, don't fix it) - since often times updates cause things to break. (See: Windows, Microsoft). I understand that it is the World wide web and it always the middle of the day somewhere, as I stated in my original post. That said, some times will be busier than others on any one server.
  9. Today, in the middle of the day, without any notice, cPanel was updated to version 78. I suppose in most respects this makes little or no difference, but in at least one way it did. Version 78 does away with Squirrelmail. The way I found out about this was that my open webmail page failed to update. (Fortunately, I was not in the midst of writing an email, which effort might have been lost.) Since I was well informed of this change, I easily made the switch to Roundcube - no big deal. Had I not known about this in advance, it might have been of more concern. My suggestion is two pronged: Don't do things like this in the middle of a busy day - typically a weekday. (subject to the fact, of course, that it's always the middle of the day somewhere, etc.) Provide some advance notice: "On Mar 19, we will be updating .... which will bring about these changes ..." Sending emails to everyone is probably not necessary, ,but at least a blog post or other notice would be nice.
  10. The Hawkhost people can probably best answer your question, but I'll take a stab at it. My understanding is the both of these services are based on "cloud infrastructure" (which I gather is some sort of distributed hardware platform with redundancy and scalability). Whatever it means, it's transparent to the user. For both services you are sharing that hardware infrastructure with other hosted sites. The cloud server is like a VPS - and perhaps gives you a bigger share of the hardware pie (so to speak). 4 GB and 2 (virtual) CPUs seems fairly hefty to me, and whether you need all that depends entirely on what your site consists of and what it does. The bandwidth number (50GB/month) strikes me as rather high: I have a couple of rather modest sites which get much less traffic than that, and which shared hosting handles with ease: Site 1: ~5000 visits/month - 200 MB/month bandwidth Site 2: ~1800 visits/month - 800 MB/month bandwidth You are talking about 70-250 times as much traffic, based on your bandwidth estimate. But ... depending what goes along with it, that may not be an issue. There is another option you have: what Hawkhost calls "Semi-dedicated Hosting". Basically, it's shared hosting with more resources (and less sharing with other sites). It costs a lot more than regular shared hosting, but it might serve your needs in terms of horsepower, combined with the convenience of shared hosting.
  11. On so many websites, for reasons that I cannot fathom, text is presented on a white background, using a gray - sometimes very light gray - font. The middle line above is the default (and it appears only) color on this forum, which isn't too bad, but isn't great either. I have seen many sites which use fonts akin to the top one - light gray. My question is ... WHY? ... The poor contrast with a white background is just hard to read. What's wrong with good old stands-out-from-white-background black? If anyone can enlighten me on what the merits of light-colored text on light-colored background are, I would be ever so grateful.
  12. I've been with Hawkhost for 3 1/2 years and find that almost everything is outstanding. Uptime - approaches 100% Speed - pages load quickly, and are the latest version, including right after an update. Price - as far as I'm concerned it's a real bargain Support - sometimes the Level 1 responses might as well be from bots, but problems are rarely very serious and are usually resolved in a fairly short time, even when they are bugs in software from a vendor.
  13. Replying to Brian's points: 1) ftp needing Passive - I will write up a ticket for you (that is now done). 2) Agree - ssh fingerprint change was ok - just seemed a bit worrisome at first, then I remembered about the migration 3) Not a big deal - lots of easy ways to learn the new IP.
  14. A week ago I got an email saying, in part, ... > Beginning Wednesday February 13th we will be starting the migration of the dal0XX.hawkhost.com server > which your account NameOfMyDomain.tld resides on to our new cloud based dal2XX.hawkhost.com system. > As a result of this migration we will be changing IP addresses on all accounts. > If you are currently using our nameservers (ns1.hawkhost.com / ns2.hawkhost.com) > * * * * you don't have to do anything * * * * and will have no downtime. The migration did happen, and went smoothly. I was not aware of any DNS-caused downtime, as was promised. However, ... I did have to take a couple of corrective measures for things that came up: FTP commands, which previously worked, stopped working. I now needed to specify Passive mode, which wasn't the case before. The change of IP address caused Putty to hiccup, saying "wrong (something or other) in cache" because that had changed. Both of these were very minor issues, but until I remembered about the server migration, I was wondering why things that had been working very nicely now were not. I am posting this just to give anyone else who might encounter these or similar problems a heads up. One other even more minor gripe: The first email said: " IP change which we will provide upon completion of the migration. " The second email said: "New IP Address: Refer to the 'Server Information' link inside cPanel" Which was not quite what I was expecting there.
  15. In my experience, in both the old and new styles, the domainname.tld (mysite.com in the example) is NOT appended. Whether residing under either /home/username/public_html or just /home/username/, the folder name is just the simple subdomain name (forum in the example), and not the fully qualified name (forum.mysite.com in the example). In other contexts (logs, ftp, and perhaps others), the fully qualified subdomain name IS used.