Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/28/2016 in Posts

  1. Paul

    Cronjob With Https

    I'm guessing this isn't the answer you're looking for, but in the off chance - /usr/bin/wget -q https://www.yourdomain.com/blesta/cron/?cron_key=CRONKEY >/dev/null 2>&1 If you're trying to determine whether the cron is being accessed via HTTPS or not, you will not be able to determine this via CLI. If you execute your cron in the manner mentioned above, then the $_SERVER["HTTPS"] global should be present. Just not via CLI.
    2 points
  2. Paul

    Cron Stopped Running

    It sounds like the cron is not set up. The cron will validate the license once a day normally. When you received that message when logging in, that your license revalidated, it means that it has been more than a week since it was validated. Setting up a cron job will prevent that error, and automate everything in Blesta. Go to Settings > System > Automation. Try running the cron manually by clicking the button. If it works, you should get some output. Then, confirm that your cron job is set up properly on your server.
    1 point
  3. Check your error/access log of your webserver. It will tell you why it is giving a 403. It could very well be mod_security related. -Adam
    1 point
  4. 403 error is maybe a modsecurity error
    1 point
×
×
  • Create New...