Cody R.

  • Content count

  • Joined

  • Last visited

About Cody R.

  • Rank
    Chief Technical Officer

Profile Information

  • Gender Not Telling
  1. Lots of spam showing up here

    We're aware of this - we clean the forums several times a day and try different captcha related options to prevent automated accounts. We opt not to do new user moderation as it's frustrating for some customers to have to wait for us to verify their account before they can post (we may go this route eventually). It also adds some overhead on determining which users are legitimate and which are merely spam related.
  2. The search from Kayako (which both the client area and support area uses) is abysmal. Unfortunately we can't do much a bout that.   Regarding the styling on the client area KB link - it is goofed that's for certain. I'll see if I can get the spacing issues resolved.
  3. Server Status

    We actually intend on changing the server status page shortly - it's going to be more generic and list any current issues (and previous ones being viewable). Once we do that we can try to tweak it to everyone's liking.   I've added this to our internal issue so we can evaluate it once we launch the new page .
  4. Small glitches in Ticket system

    This should now be better - the close button is gone and the sorting should now have the last updated tickets are on the top.   Please let us know if you're seeing any issues!
  5. Small glitches in Ticket system

      Could you clarify if you're viewing tickets through the client area ( or the support area (   Regarding closing of tickets by users - we disabled this due to some of our workflow choices. We should be able to remove the button however to make it less confusing.
  6. Again please help with error 522! Please

      Did you submit a ticket? This may be something we can debug as I don't believe it to be a latency issue that moving servers would resolve.
  7. cPanel 2-Step Verification

      We've been curious about this for awhile / numerous people have inquired to cPanel about it as Brian mentioned. I've tried to implement my own using Authy and their authentication API however I didn't have too much success. One big feature request that's pending which will make this much easier is once they start using PAM for some things.   It's worth noting that it's easier said than done - a cPanel server has numerous services running: FTP, cPanel, WHM, SSH, Mail, etc. These won't all be covered by 2-factor easily. Even if they protected the cPanel / WHM logins you have to worry about the API.   Hopefully they do something sooner than later though!
  8. SpamExperts - how to manage?

      Unfortunately this isn't possible through the current UI however SpamExperts does have an API. If you like I'd be more than happy to write up a quick script for you and give you a list (if necessary on a regular basis / cron job) of accounts that SpamExperts is enabled for.   While this does seem like a big pain in the butt (it is in some circumstances) it's ultimately allowing us to keep a good reputation for our mailservers and has stopped a large amount of SPAM from entering and exiting our network. You may be interested in our blog post here.
  9.   Great to hear! We're very happy with the transition on several levels - this allows us more flexibility in what we can offer in the future, we really enjoy the network which has been great for some of our international customers (and great as always for our local crowd) and brand new machines! Nothing like dusting the cobwebs off and freshning up things a bit.   Please let us know if you run into any issues!
  10. Moving to LAX?

      We're consolidating our West coast hardware into LAX due to us finding good peering for our customers and allowing us more flexibility (owning our hardware vs. renting). We'll be working with resellers to try to mitigate the migration and will likely keep those specific servers online longer than our standard shared ones.   Ultimately it's a decision based off our growth in that particular region and issues we've had with some of our customers with our current provider (SoftLayer) - primarily peering.
  11. SSL key length of 256 is too weak

    We should be using 2048 bit keys and by default using strong ciphers (IE: AES-256). If you want to PM me the key you're referring to I'll be more than glad to double check. Ideally we'd like to have forward secrecy but I don't believe cPanel supports that quite yet - I'll have to take a look.   It may be worth noting most certificate authorities require a minimum key length of 1024 bits - including the one we resell through (Global Sign) and use internally:
  12. Unlimited Bandwidth ?

    Hello,   We're still rolling out the changes however if you like contact our support department and they'll move you over right away!
  13. Zero Response from HawkHost to email hacking

      Excellent advice and one we adhere to at Hawk Host for all employees. We require the use of a password manager / unique logins for *everything* and *everyone*. This reduces the chance a single compromise will lead to a larger issue. I do recommend LastPass or KeePass for local password management.
  14. Common sense support

    I understand the confusion / frustration in regards to this however this is a strict company policy we have in the support department(s). If you contact *support* without a e-mail not tied to a account we'll likely ask you contact us from one that is tied to an account.   Why?   Well you have to realize we often get inquiries from resellers customers (we don't provide support for them, only the reseller) and or visitors of a website will contact us asking information about a website or server which we will not divulge unless you own an account with us (do you want a visitor on your website knowing MySQL crashed due to a flaw on the server?). This is merely a policy to help preserve privacy / security for everyone. We rather be stringent in this regard than to accidentally divulge too much to the wrong people (this includes server information that's not readily available publicly (we'll state we're updating kernels on our status page due to a bug or security concern. We will not divulge it to a random person inquiring)).   How can we fix this? I'm not sure - If you're noticing issues with your account / server I think it's reasonable to contact us with an authorized e-mail. Can you elaborate as to why you'd submit an inquiry to us that's not tied to your account (keep in mind you can add numerous e-mails: )?     I see why you think this - we have very strict policies in regards to replying / supporting people who are not authorized to receive that support. This is not our support staff's fault but a policy our upper management (including myself). We rather tread on the side of caution.   If you have any suggestions that can make this scenario better please let us know - just understand it's not done blindly / trying to deflect inquiries.
  15.   Hi CharlesM,   It's generally ill-advised to delete things out of a database directly as sometimes they will have direct relations to other tables. The best way to do it is through the software itself as it will clean up any "loose ends". A quick Google search suggests it may be safe to delete users directly but again I would advise again it.   To do something like that you'd go into PHPMyAdmin in your control panel and select the database you installed MediaWiki on. From there you'll get a list of tables - one of them is likely to be named something along the lines of `users` or `user`. Select that and you'll have the option to manipulate the rows - including deleting them. Again I highly advise to not do it via this method.