Jump to content

benneth

Member
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

2 Neutral

About benneth

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nameservers are the path forward for sure. But why is the CNAME important when it comes to migrations? I thought it was for vanity/appearance.
  2. Ok, got it. So if I understand correctly, there's two approaches to ensure I grow the server farm properly, and also so client DNS records follow me (regardless of which hosting provider I am working with): 1. Buy your own IPV4 address (difficult, expensive). Create an A record for the client, set the IP for the DEDI1.exampleservice.com... same for DEDI2, DEDI3, etc... 2. Create your own nameservers (easy, cheap) - means you don't have to login to a client's registrar more than once (eg. set ns1.examplebusiness.com, ns2.examplebusiness.com) I'm looking at option 2 more seriously, due to the complexity and cost of option 1.
  3. Right, so something like "hosting.example.com", or "anotherService.example.com" is a service domain? Any other examples? Also, what do you mean by "if your domain has issues, client services are not affected"? Do you mean I can take my server elsewhere and after a migration, client services should be unaffected (except for those with A records w/ the old server IP)? For context, the only service I sell is web hosting for WordPress sites. I don't allow customers to order services, but I do allow them to login to their WHMCS account to update their preferred payment method. A bit strange, but my customers are 100% tech luddites who want someone to "just do it" for them -- so that means no cpanel access, and I'm OK with that. As for selling the "service domain", what do you mean by this? EDIT: Keeping in mind, the goal is to figure out the best approach to add VPS' or DEDI's in the future to offer a single service (web hosting).
  4. Hey Steven, Thanks for the speedy reply. What do you mean by "service" domain? Can you give me an example? Is there an advantage to using a service domain?
  5. How do you architect adding multiple DEDI or VPS servers for your WHMCS installation? CURRENTLY: 1. WHMCS is currently installed on a VPS with all of my client websites. The domain is "example.com" for this VPS. 2. Since my WHMCS shuts itself off when provisioning accounts via WHM on the same VPS, I am moving the client websites to their own DEDI server (which would require either A) a new domain, or B) a subdomin) 3. I understand you can use a subdomain on the "example.com" VPS in its DNS Zone, with the goal of configuring the VPS to point client website DNS to resolve on the DEDI... so the DEDI's domain would look like "dedi1.example.com", and DEDI2 would look like "dedi2.example.com" Does anyone else use this approach to scale their hosting biz? Thanks.
  6. Yes I believe so Brian. Funny thing is that I've never once set a product "termination date", yet after migrating from SiteGround to InMotion, a bunch of my clients were assigned termination dates automatically. Have you encountered anything like this? WHMCS even deleted 4-5 of the clients before I caught on to this termination date... had to re-migrate the sites, which was a bit of a nuisance. SG Migration Thread (in case you were interested in what's going on with SG/WHMCS):
  7. Hi Mandalorian (great show by the way), For the WHMCS migration, it was simple. They copied the files and database to the proper URL... pretty seamless. Eg. they transferred WHMCS.YOURWEBSITE.COM to WHMCS.YOURWEBSITE.COM (no change). The funny thing is that since SG offers no root access (on the VPS I had), InMotion recreated all of the accounts as individual cpanel accounts. At this point, I requested that all accounts live under "root" so you don't have to create dozens (if not hundreds) of unique API keys, one per website. Instead, create one API key with ROOT on InMotion, and then all of the cpanel accounts should show up in the "Server > Sync" admin in WHMCS. Another funny thing is that the packages in WHM were not migrated properly. You have to recreate these yourself (since there's no root access, therefore InMotion cannot do this for you). DEFINITELY get on this, I've spent a week, week and a half messing around with both support teams (mostly InMotion migration support). A "rolled out" migration is what I ended up doing, although InMotion doesn't like doing it this way. Consider doing it all in one shot if you can (including your NS/A record changes).
  8. I'm having the same issue after a migration from old host to new host. All of my packages in WHM are sync'd as products in WHMCS... and, my client websites and email are working...... BUT all of my accounts show as "INACTIVE".
  9. Went with InMotion. 3 years plan. Take-aways: -Make sure you recreate your products on your new server, as SiteGround didn't allow for the transfer of packages from WHM -Migration was free -Make sure the migration team lists ALL of your accounts, they missed a couple of mine and I had to track them down manually -There are 10 days left before SiteGround is shutdown for WHMCS customers... So, make this a priority if you need to migrate away from SiteGround! -ALSO, make sure you reassign the owner to your root account for WHMCS (InMotion migrated each account in separately).
  10. No root access, you'd have to do individual cpanel backups if you wanted to export your hosting business... sounds fun right? Can't use the built in cpanel backups or otherwise. Not even a virtual CLI for SSH is offered with their VPS. They have 7 day full hosting backups, and that's about it.
  11. As requested, I have confirmed that SiteGround will discontinue support of WHM and WHMCS effective February 1, 2021. I guess they made that call anyways... But let's get back to the main point! Which web host providers are a suitable replacement for SiteGround? edit: I can't believe I'm saying this... but even SG support encourages me to migrate elsewhere (since WHMCS is not in the picture). Dang.
  12. The way SG is wording it, is basically "We won't permit this application to run on our servers, supported or not".
  13. Well if I had to guess, SG wants to niche their hosting base. As far as VPS goes, this was the impact. Not sure about other machines they offer. Also consider that without ROOT access their VPS hosting for WHMCS wasn't great to begin with.
  14. Which hosting companies have you heard about? Or just in general. I really hope this doesn't impact WHMCS too severely... I love my WHMCS. InMotion seems like a good spot to go so far...
  15. Remarkably sad 😞 I liked SG, except for the lack of root access. You kinda feel like a well fed prisoner...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated