Jump to content

sunrisepro

Members
  • Content Count

    147
  • Joined

  • Last visited

  • Days Won

    1

sunrisepro last won the day on March 3

sunrisepro had the most liked content!

About sunrisepro

  • Rank
    Advanced Member

Recent Profile Visitors

517 profile views
  1. The recommended command is */5 * * * * /usr/bin/php /home/username/public_html/backstage/index.php cron The complete job I have is /opt/cpanel/ea-php72/root/usr/bin/php /home/username/public_html/backstage/index.php cron And the last time cron ran was when I manually ran it yesterday. Also how does CLI relate to this?
  2. So the cron path on my server changed because I upgraded the server to PHP 7.2. According to my server admins, cron jobs are running properly but is /home/username/public_html/backstage/index.php cron correct? Or should it be something different for php 7.2? Or do I need to upgrade Blesta?
  3. Where do I update the url for the cron command? The 'cron command' field is not editable and I can't find any info on this is your documentation. I only realized when invoices had not been automatically paid since I thought I had updated the command url; I just ran cron manually.
  4. Figured it out - I had upgraded the server to php 7.2 and the path had changed. All good now.
  5. Yep - the last time cron seemed to have run was 2/25: https://nimb.ws/FfBcDw Checking with my host. What can I do to check/fix on my end?
  6. Interesting a new retainer that is starting did not have the invoice automatically sent on 3/1 as it should have. Is this pointing to a cron issue?
  7. There are nine recurring hosting invoices that were supposed to be run on 2/28 that are still sitting there. However, 3 recurring hosting invoices did run on 2/28. I'm doubting that all 9 have issues with their automatic payment accounts, that would be too great a coincidence. What's the best way to troubleshoot this?
  8. sunrisepro

    Upgrading 3.6.2

    I've been remiss in updating and want to upgrade Blesta so I can use php 7.2. I assume the normal upgrade process (unzip & overwrite existing files, go to ~/admin/upgrade, click the link) will be fine? Or do I need to upgrade to an intermediate version before the latest version? Also, I am considering moving my Blesta install to a different cpanel on the same server (due to rebranding my business, the new domain is in a different cpanel on the same server). 2 questions: 1) I currently have Blesta installed in a subfolder. Will the domain change matter? 2) Since it's on the same server, will the new install maintain it's connections to WHM? I'd like these to go as smoothly as possible so any advice on things to look out for would be appreciated.
  9. OK - checked the services for two clients and the usernames are identical to the ones in WHM.
  10. np. The cPanel module is connected; my new host imported all the cPanels for me (no change in cPanel names or anything). Is there anything else I need to do?
  11. I migrated my hosting to a new server. I just cPanel module settings to connect Blesta to WHM. It shows '2/20' accounts, which I'm not sure what it means (there are 20 cpanels total). How do I connect each cpanel for automated suspension and such?
  12. I just switched the DNS for the domain that includes Blesta. What do I need to disable on the old install of Blesta to prevent charges from going through? I don't want to double charge clients for invoices that are to set to autopay today or tomorrow.
  13. It looks like a sample because I edited out aspects I wished to remain private Says 'The cron last ran on Feb 10, 2018 6:10:03 PM.'
  14. Hmm - that was the cronjob set in cpanel. This is what's in Blesta: */5 * * * * /usr/bin/php /home/xxxxxxxxx/public_html/xxxxxxxx/index.php cron I'd check the logs but I can't find them.
  15. And here's the cronjob: /10 * * * * /usr/local/php56/bin/php-cli /home/username/public_html/folder/index.php cron >/dev/null 2>&1 That looks ok?
×
×
  • Create New...