tgonhawk1

Members
  • Content Count

    86
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by tgonhawk1

  1. 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.
  2. 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.
  3. 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!
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. Article about easy-peasy hacking of other hosts which allowed taking over user accounts. (Wel,l easy-peasy if you really know the nitty gritty ... but there are such people.) I'm confident Hawkhost has better practices than that, but ... I thought I'd bring those vulnerabilities to notice just in case a little pre-emptive action might be in order.
  14. It's a week before Christmas, And I want you to hear, Your service is great, And has been all year. The servers do run Quite dependably, The websites stay up, That's how it should be. On Tony! on Brian! and on Cody, too! A message to all three of you. You've got yourselves an excellent team, Keep up the good work, in Twenty Nineteen!
  15. I sent an email to epzinfo@etapizeta.org successfully, and got a reply. (from jsb#########@gmail.com). It looks like you're making progress here, since at least some mail is reaching your email address.
  16. If fiddling with Spam Experts didn't fix the problem, here is some information that might be relevant: Visiting etapizeta.org in my browser works great. traceroute to your site (which works from my PC, but NOT from a couple of VPS's I have) leads to the IP address 192.124.249.12 which resolves to cloudproxy10012.sucuri.net Visiting 192.124.249.12/~etapizet (which works on cPanel servers from most hosts, including Hawkhost) results in this: The site you are visiting is using Sucuri Website Firewall. And for some reason it is not configured properly. If you are the site owner, please open a ticket here asap for us to look at .... Have you engaged the services of this sucuri.net to secure your site? If so, I would look there for clues as to why your emails aren't arriving. (I wouldn't worry too much about that "not configured properly" message - if it's not a cPanel server, they probably don't support that sort of access at all. "etapizet" is your Hawkhost cPanel user id - shortened from your domain name.) A couple of other data points: I can successfully traceroute from my PC to your site, which appears to reside somewhere on the West Coast (where I am). [ Hawkhost's only location on the West Coast is Los Angeles. If you are not hosted there, this is another odd thing. ] Trying the same thing from a couple of VPS's I have in other parts of the US fails almost out of the gate - they go one or two hops and that's it. Emails to your site could be meeting the same fate - or they could be arriving at sucuri.net which doesn't know what to do with them. I am just another customer - who has always had good support from the Hawkhost team - trying to be of whatever help I can. Usually, when Tony or Brian gets involved, things get resolved pretty quickly, so your difficulties are a little surprising to me. .
  17. Go into cPanel - select "Professional Spam Filter", which takes you into the Spam Experts control panel. It's a complex interface (sadly), but you should be able to find how to turn it off there.
  18. I would like to voice my support for Hawkhost support. As with most hosts, the first responders (sometimes called Level 1) are not always able to solve problems right away, but since they do respond in a very timely fashion, with a little back and forth, problems do get resolved satisfactorily nearly all the time. Usually that happens within a very short amount of time. Most things I encounter require the "Level II team" to intervene, and then some real expertise gets applied and the problems are taken care of, including even those which require a 3rd party vendor to fix something. The bad news on that is, in my observation, the "Level II team" consists primarly of Tony, the CEO, for the most part, and sometimes Brian or Cody. Gratifying though it may be to have the upper echelons of the company working on my problems, my concern is that the technical expertise does not extend much beyond them, making the whole thing dependent on just a handful of people. But nevertheless, for the 3+ years I've been a customer, I've been completely satisfied with Hawkhost products and support, and recently began converting to 2-year renewals as a result of that. The very low price for shared hosting is just the icing on the cake.
  19. That will be helpful - thank you.
  20. Additional question: Will there be any notifications (such as an email) about the actual starting and stopping times for the outage? Thanks.
  21. Since this is not about just my site, I am posting here, rather than via ticket, in case others are interested. I received a mail today saying there would be a service outage in New York on Monday Nov 19, lasting as long as six hours. That's ok - sometimes you just have to take servers offline to do things and there is no workaround. I was wondering if it would be possible for Hawkhost to set things up so that visitors get something informative rather than just a "Cannot connect" or "Server not responding" error message which might discourage first-time visitors from trying agin later. The idea would be that any attempt to reach the servers would redirect somewhere which would generate a response page saying "Website is down for maintenance - try again later" or words to that effect. Given that it's a relatively short outage, this isn't critical, but would be helpful if it's not a lot of work to do.
  22. Here are some off-the-wall suggestions from someone (me) not really familiar with node.js, so don't be too harsh if they are also off the deep end. 1) When preparing dynamic content via CGI, my understanding is you need two newlines after the Content-type line (if the writeHead function doesn't do that for you). I know leaving those out can generate obscure 5xx errors. 2) Naive guess: should res.end() be res.send() ? seems like a more logical thing for that to be, although it might also just be a typo in trascribing it to the forum, or I could be completely wrong about it.
  23. As usual, you guys are on a problem quickly and effectively. SSH logins to the NYC server are now fast, too. Good work.
  24. I have two different shared services with Hawkhost: 1) Primary on nyc004 2) Basic (old style) on dal010 When I do an ssh login (using Putty program from my PC), both of them ask for the password without any delay, but after I enter the password there is a significant difference: With #2 the prompt appears essentially instantly, in less than 1 second. With #1, the login is consistently slow. I just tried it a couple of times, the first time took about 10 seconds, the second one nearly 30 seconds. After the login, performance on both is comparable, with commands always executing quickly. Since this not really a problem that *needs* to be resolved, rather than opening a ticket, I am posting here just to bring it to Hawkhost's attention, and also so that other users might see it and share any similar experiences (on either the fast or slow side of the question).
  25. Some suggestions here which might help in the short term: Try switching to landscape view and zooming to enlarge the text. The wider view will allow for longer lines, and while there will be fewer of them, it strikes me as being more readable that way. Another point is that the blog gets updated fairly rarely, so you might want to use the mobile just to see if there is anything new, and then return to read it from a device with a larger screen.