Search results

Thanks a bunch @Kaspar ;) I tapped out out and ran a forced update of our system app and it seems to fixed the issue. Not sure why or what generated the 500 error which would have been useful to know for future internal reference. I'm suspecting some of the web apps files must have been...

Thanks for the suggestions! Unfortunately all your suggestions doesn't yield any results. I'm still stuck with the default splash error screen (and I have enabled debug mode too in the larvavel app too (including PHP of course): Still searching with a torch in the server for any clues. Haven't...

Thanks a bunch @Kaspar I'll look into that in a while from now. Very appreciated!

So I finally have some time to go through this error on our company server. The mentioned log file doesn't exist in "/var/log". the error_log file simply doesn't exist. So that is a dead end for me to figure out what is wrong here.

While searching for another issue I found this message in the PHP error log (/var/log/phpx.x t): "Server reached max_children setting (10), consider raising it" Any idea how to tweak this setting for a website in the system? Thanks in advance.

Use BitWise SSH which is free to use too. It makes it very easy to manage Linux and you can also configure it to use the Windows short cuts for paste/copy etc. Download Area | Bitvise

It seems to be accurate. Thank you @Peter Debik for your kind assistance. Kind regards

Thanks @Peter Debik for your kind reply. I've tested and deleted the backups made in the "backup manager": However there is still loads of files in the "dumps" directory and sub folders: /var/lib/psa/dumps/.discovered Now sure how they are generated, and how clean this up. Logically (At...

So in var/lib/psa/dumbs there is a ton of backup files which fills a huge amount of GB and just taking up server disk space. More examples here directly in Linux: Is there a way to delete them in directly Plesk or shold we delete them manually in Linux? (I assume that Plesk is generating...

I guess we we'll do that and also enable debug in the Laravel code. The server is self in regards to the above in this thread doesn't seem to reveal much why apache pukes the 500 error.

It only tell that you have the 500 internal server error. But we like to know the reason behind why the 500 error is created. So basically its a "nothing burger" as we have no information that leads us to the real issue so we can solve it on our server.

I did and I cannot find them? Yes, of course;

How do we do that? Thanks..

Right, thanks! That is where the below screenshot comes from. But that isn't much helpful.. Thanks for your reply @jorge ceballos !

So that log file also reside in that directory? (/logs). Thanks in advance for your answer.

Thanks for the reply Peter. Well yes though Linux with elevated privileges I suppose we can access that. So there is no way to configure Plesk to display this information directly in the GUI itself? No, not really. Only the default three click options on the domain level.. (like the...

So we have this app running web cron and now we are getting the dreaded 500 internal server error. But that is not the issue itself: The issue is that Plesk do not give you more information about the 500 error itself. So it is very complicated to attempting to solve this issue when we have no...

Interesting. Thanks a bunch for the feedback. Sorry for the misspelled link by the way, here is the correctly formatted link: takemarket.co.uk The conundrum still remains though. I guess we (me and my colleges), just need to keep digging and hopefully we will find something sooner or later...

Well yes for all request that doesn't concern the webapps that is installed. The above logs are for for the company corporate website: https//:takemarket.co.uk so that is not what you are seing (HTTP/1.0 /default page). Hmm... With that said; I mean it does say "HTTP/1.0", could it be that we...

Thanks for the reply Mow. None. 1.) You need to know the URL/domain name to access our systems on our server. If make a misspelling you will either be served with 404 (if domain is correct), or if nxdomain/and/if typo; you will be served the default landing page which I also mention below...