I am trying to install elgg version 1.12.3 on WAMP, but i keep getting an 'Internal Server error' on Requeriments Step.
I activate "mod_rewrite" on my apache, and check the htaccess file. Still have no idea why dnt work.
500 error is a very generic error that does not tell much itself (it's basically "something is very wrong on server side"). You should have more details in Apache error log. It's likely that either something is off with Apache configuration or additional thing is required in .htaccess. Error log should make it clear. You can find it under "Apache" -> "Apache error log" in wampmanager.exe options.
Related
I installed the Postman interceptor Chrome extension, the Postman interceptor and the custom Node version I was asked to install and once I try to start the capture I get a toast telling me that there is an "Error creating interceptor session" without any further useful information.
Following the troubleshooting tips I verified that:
Chrome is installed
the directory ~/Library/Application Support/Google/Chrome/NativeMessagingHosts exists.
I have a working internet connection.
my firewall allows Postman to connect to the internet.
I have permissions to read and write in the ~/.postman/InterceptorBridge directory.
I have write permissions to my ~/Downloads folder.
which node yields /usr/local/bin/node
the manifest file com.postman.postmanapp.json is not in ~/.postman but the documentation does not tell where it is even supposed to be. I deleted ~/.postman and reinstalled Postman. The directory did not reappear. The error persisted. I have no possibility to reinstall the interceptor from within Postman now.
Before deleting ~/.postman the Interceptor binary existed therein but is obviously gone now.
Executing pm.interceptorInstaller.reset() in the Postman dev tools did not enable me to reinstall the interceptor either. The error persists.
I appreciate any help.
Postman version: 9.15.8
Chrome version: 100.0.4896.60
macOS version: 12.3
I am trying to run a Django site, using Gunicorn (with docker compose). Everything works as expected in Firefox, but Chrome reports the error "Uncaught SyntaxError: Unexpected number" for random .js scripts. If I reload the page, scripts are loaded without any errors.
So, at first I had a similar issue, since Chrome was randomly failing to load scripts. I solved this by changing the port in Gunicorn from 8080 to 80. However, once I did that, the scripts started loading but also started throwing the Unexpected number error.
I have tested it on both Chromium (Ubuntu 18) and Google Chrome (Windows), running the web site locally and from a server.
Also, I've noticed the following:
1) files which throw errors are rarely the same, so in one window script example1.js may work, and example2.js throws the error, and in another window example3.js throws an error and the rest work.
2) if I reload the page, no .js file throws an error.
3) every error indicates that the problem is in line 5, like this: "Uncaught SyntaxError: Unexpected number jquery-3.2.1.min.js:5".
Would greatly appreciate any advise on how to tackle this.
can some one please help me to solve the mentioned error? I uninstalled the tika and reinstalled it but getting error. I don't have idea about how to solve this error.
You need to kill apache server process or you can simply restart your machine and re-run your script
I'm working with a website running on laravel. The site works fine on my local through Homestead, no problems.
Recently, I pushed the git repo up to a server that never had this site running on it before. I set everything up right (had some nginx config issues for a while, but got those all sorted out). Nginx has the public folder set as the site root, so it hits the proper index page when you load the page.
What I'm getting is a 500 error. My error logs reveal the following is the reason:
site_root/public/../bootstrap/autoload.php - Failed to open stream: permission denied
in
site_root/public/index.php on line 22
I can confirm that the bootstrap folder and the autoload.php file are both accessible by the web user, and have permissions that should allow access.
I've read a few cases online of people solving this issue with a 'composer install'. I tried updating composer, doing an install, and dumping its cache. I also tried removing the vendor folder (which had been a part of the git repo), and running composer install to regenerate it. None of these have worked. Happy to supply any info that will help. This is Laravel 5.2 running on Ubuntu Server 14.04 with nginx, all on an AWS box.
Solved it. This was actually an issue with site-wide permissions. They were set to 770 instead of 775. I suspect that I can and should restrict them more. For now, I'm just happy to have it loading again.
Moral of the story is to check your permissions site-wide, not necessarily just on the file which gives you the fatal error. You may continue to get the same fatal error, despite permissions being wide-open on the mentioned file. If so, look for permissions issues elsewhere.
We have django 1.1.1 website, that works fine on development server (python manage.py runserver). But when we use nginx + wsgi, ngnix is timed out and return "504 Gateway is time out". error.log is empty.
So, probably it is environment issue but I don't know where to start because it was working fine and now its not and I have no error to point me in the right direction. Restarting nginx doesn`t help.
I'm new enough to this environment, could someone possible give me some idea of how I could find the problem
Thanks,
Derek
You can try setting DEBUG = True in settings.py and see if you can review the errors.
If that doesn't work, set DEBUG back to False try setting up the ADMINS so you receive emails with the error reports.
Those are my only suggestions at the moment. Good luck.
Look at the error logs for the Nginx server. My guess is that it's invoking something through FCGI or WSGI (whatever you had set up), but that it's not responding correctly. More detail should be in those logs.
It turned out to be mistake in the middleware configuration ... fixed it and all back to normal.