followed the documentation, yet it keeps returning a 500| Error page
please comethrough.
-
You MUST read the Babiato Rules before making your first post otherwise you may get permanent warning points or a permanent Ban.
Our resources on Babiato Forum are CLEAN and SAFE. So you can use them for development and testing purposes. If your are on Windows and have an antivirus that alerts you about a possible infection: Know it's a false positive because all scripts are double checked by our experts. We advise you to add Babiato to trusted sites/sources or disable your antivirus momentarily while downloading a resource. "Enjoy your presence on Babiato"
Onlinetrader - Forex Signal Service and Investment Management Solution 3 November 2023 Untouched
- Thread starter mcjay
- Start date
please comethrough.
Just read the documentation, it was pretty much explained there.
Also, note that when you check the url say example.com/cron, It will return an error, rest assured, if you set up the cron as the documentation explained it will work regardless. The best way to check if your cron works is from the email log.
i appreciate your response and trust me, i have hopes it will work this time. Now once i choose the cron job option from my hpanel( using Hostinger) i basically selected the custom option and used the wget command line with the subdomain that holds my cron job.. time is set to every5minutes ***... trust me i have gone over it many times.
www.subdomain.yoursite.com <- cannot be reached (do NOT use www)
subdomain.yoursite.com <- the real address that redirects to yoursite.com
subdomain.yoursite.com/cron -> error 500 - check your server error logs or laravel error logs (storage->logs)
And this is debug from only the link.
On the other hand I would suggest you to read this community rules and guidelines. We like to be helpful but not with strangers.
subdomain.yoursite.com <- the real address that redirects to yoursite.com
subdomain.yoursite.com/cron -> error 500 - check your server error logs or laravel error logs (storage->logs)
And this is debug from only the link.
On the other hand I would suggest you to read this community rules and guidelines. We like to be helpful but not with strangers.
we'll get there...www.subdomain.yoursite.com <- cannot be reached (do NOT use www)
subdomain.yoursite.com <- the real address that redirects to yoursite.com
subdomain.yoursite.com/cron -> error 500 - check your server error logs or laravel error logs (storage->logs)
And this is debug from only the link.
On the other hand I would suggest you to read this community rules and guidelines. We like to be helpful but not with strangers.
i'll make changes now.
You've seen what @slvrsteele sent. This is basic knowledge and the documentation never appended www to the Cron url
Actually doc appended www to curl for main domain but NEVER use www on subdomains (unless it have a DNS entry for it)
I am not a stranger here, I learn and appreciate everything here, whilst I prepare to add something vital to the forum, a step at a time, but in time my appreciation will be tangible.www.subdomain.yoursite.com <- cannot be reached (do NOT use www)
subdomain.yoursite.com <- the real address that redirects to yoursite.com
subdomain.yoursite.com/cron -> error 500 - check your server error logs or laravel error logs (storage->logs)
And this is debug from only the link.
On the other hand I would suggest you to read this community rules and guidelines. We like to be helpful but not with strangers.
Similar threads
