• Content Count

  • Joined

  • Last visited

  • Days Won


tgonhawk1 last won the day on December 27 2017

tgonhawk1 had the most liked content!


About tgonhawk1

  • Rank
    Advanced Member

Recent Profile Visitors

7,081 profile views
  1. You can get your blog into Google's search space by creating links to it on other sites. Even better is getting a link to appear on another popular site. Then more people will see it, which in turn will lead to more links and more searches and more visits. If the link text includes likely search terms for your blogs, people will find their way there when they search those terms. That is, if they are specific enough to your blog that you don't end up on page 35 of the search results. Also, it will depend on the contents ... if what you write ends up in search results and isn't buried by more popular sites who write about the same thing, you will get more traffic that way. All these gimmicks (directories, pings, etc.) probably work to some extent, but in the end, if you have what people want, they'll find you.
  2. If you install Wordpress on a Shared Hosting Account, are they any additional charges? A friend of mine has an "EasyWP" subscription with Namecheap, which allows him to set up a Wordpress site. It appears that you do everything through wp-admin, which you get to by signing in to your Namecheap account, and working your way through Apps and EasyWP pages. (Possibly you can get to directly through the client's website, but I'm not sure about that.) Is that the same wp-admin that would be part of a Wordpress installation here? In other words, is EasyWP making things any easier over just adding Wordpress to a site here?
  3. You can request being moved to another server (which may or may not help, depending what the underlying problem is). If it is another user hogging resources, you'll get away from that, but there is no guarantee the other server won't have similar problems. I agree that hosts should act on their own when problems like this occur. Unlike isolated users, they are in a position see what is going on server-wide. "Proactively" is the buzzword du jour I believe.
  4. I don't know the ins and outs of Wordpress, since I don't use it, but in general, can't you do this with an addon-domain or a subdomain? To illustrate in more concrete terms, suppose your main domain is under /public_html. You create another directory called, say, /staging (parallel to rather than under /public_html) and replicate the whole thing under there, including, notably, /public_html/cgi-bin. You point your add-on domain or subdomain to /staging as its document-root. Then do all your updates and testing on the files under /staging, and when you're satisfied, copy them over to /public_html? If you're using databases, you'd need testing versions of those too. I assume this Softaculous function takes care of that for you.
  5. Your regular expression (above) matches the following: ^ -> means the start of the target, so the matches will have nothing before /iklan/. Something like /abc/iklan/ will not match. ( ) is for grouping, but that is not used here, so those are redundant .+ -> means one or more of any character $ -> means the end In summary, this will match anything starting with /iklan/ followed by one or more characters. It would appear that it is redirecting the URLs (the part before the ?'s) and preserving the query strings (the ? and what comes after). That accounts for the 301's. The 410's must arise from some other rule.
  6. If you are not the single longest tenured customer, you are surely in upper ranks. 12 13 years ago would be 2007 2006, and Hawkhost only got started three two years before that (2004). It's good to know that they've been doing such a good job for so long, and long may it continue!
  7. Look at the Metrics section and then choose Awstats. It may be that Awstats has to be enabled first (to gather the stats) but usually that is the case. There is another one in there - Webalizer, but I don't use that one. For reasons I don't understand, the two often have different numbers. Also check "CPU and Concurrent Connection Usage".
  8. 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.
  9. 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
  10. I read today on 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 ("page" is not part of the link) they mention Cloud Linux and Litespeed. Does cPanel own those, too?
  11. 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.
  12. 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.
  13. Here are some examples from the 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!
  14. 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.
  15. Given that this cPanel update addressed security problems, and 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.