I've been struggling with a 403 error on my WordPress site. All of the suggestions I found involved modifying the httpd.config of the apache server, particularly
(located: C:/Wamp/bin/Apache/apache2.2.22/config/httpd.conf)
# onlineoffline tag - don't remove
Order Deny, Allow
Deny from all
Allow from 127.0.0.1
</Directory>
to
# onlineoffline tag - don't remove
Order Allow, Deny
Deny from all
Allow from all
</Directory>
However this didn't work for me. I changed it back to the original settings and restarted WAMP - Now WAMP's icon goes orange instead of green.
I've seen a lot of people saying it's skype. I do not have skype installed. Wamp was working earlier today but it stopped after I made changes.
(Note, to find the httpd.config file I did a search of the folder of Apache. he first result was for a file with the same name located in: c:/wamp/bin/apache/apache2.2.22/conf/original/httpd.config) I mistakenly modififed this file initially but once i realised it was wrong I reverted it to it's original form).
Point 1.
Use the wampmanager icon in the system tray, left click menus, to access config files and lots of other things. Then you will be editing the correct files.
Point 2.
What did you think the effect of
Deny from all
Allow from all
Was going to be?
Question:
Where did you install your wordpress site? ie what folder?
Just back up you www directory along with your database tables, then uninstall WAMP totally. After uninstall, delete the WAMP folder. Then reinstall WAMP
Related
I want to run my Django app created in virtualenv on ubuntu with python3. Folder structure in virtualenv folder:
-bin
-include
-lib
-myapp
-share
pip-selfcheck.json
The myapp folder contains my application with apache folder configured as specified in this tutorial: https://www.sitepoint.com/deploying-a-django-app-with-mod_wsgi-on-ubuntu-14-04/
I have all apps installed I need in my virtualenv, after 'sudo service apache2 restart' I see only Apache2 Ubuntu Default Page.
File /etc/apache2/sites-enabled/000-default.conf is like in the tutorial:
<VirtualHost *:80>
WSGIScriptAlias / /home/myuser/mysite/apache/wsgi.py
<Directory "/home/myuser/mysite/apache/">
Require all granted
</Directory>
</VirtualHost>
Of course with correct paths pointing to my project location in 'venv' folder.
No idea where to move on, what to check, thanks for suggestions.
EDIT:
I realy dont get this, I edited the mentioned file, had a try, nothing happened so I edited it back and after restart it it worked.
The official Django documentation on using mod_wsgi can be found at:
https://docs.djangoproject.com/en/1.10/howto/deployment/wsgi/modwsgi/
It may be better to consult that for how to set things up specifically for Django, you are missing various required configuration elements.
As to why you are still getting the default page, it could be because you added that configuration as an extra thing to the end of the default sites file, rather than inserting the contents of the VirtualHost you have into the existing VirtualHost in that file. If you added it after, it will be ignored as it will still use the existing VirtualHost as it comes first and you haven't set up correctly named based hosting.
Also be aware that where other people say you should use something else, every solution will have a learning curve if this is all new. No solution is simple if you want to integrate into your existing host system. So jumping around looking at different solutions can be a great waste of time. Select one which you think you like and stick with it. The idea that one is superior to others is in general nonsense as their performance is similar.
I would actually suggest you skip even trying to integrate it into your host system to begin with if you are just playing. Use a WSGI server that you can run from the command line, even if it is just the bundled development server with Django. Options which are simple to run from the command line are:
mod_wsgi-express
gunicorn
So after editing the file, restarting apache, editing the file back it works (/etc/apache2/sites-enabled/000-default.conf). Really dont get it, several restarts yesterday did not help...
I have Ubuntu 20.04 and Apache2. I followed the mod_wsgi installation instructions linked to here but forgot to enable the module in /etc/apache2/apache2.conf (or to include a file from apache2.conf that does so). I added that and then the WSGIScriptAlias / /home/myuser/mysite/apache/wsgi.py directive in my 000-default.conf did not cause an error when I restarted the server with systemctl restart apache2
I'm new to Django and Apache, so apologies if my terminology is a bit off.
I have a Django app that I'm serving with Apache using mod_wsgi. I used this guide, and just switched to Apache from the Django dev server. In my 000-default.conf file I have this line
WSGIScriptAlias / /home/ubuntu/Projects/myapp/wsgi.py
Everything works fine and the homepage of my app is example.com. However, I find now that there are images (a few tilesets) that I was previously accessing at example.com/tiles which are now not accessible, because they are actually stored at /var/www/html/tiles.
I understand why the paths aren't working, but I'm wondering if there's a way I can keep running the django site from example.com while also serving the tiles from a different directory.
I think if you add a preceding configuration directive:
Alias /tiles /var/www/html/tiles
... it should fix it.
Please note that order of Apache configuration directives may matter. More information about Apache and Alias.
I am trying to start wamp serve which was totally running fine on my laptop two weeks ago, but now after two weeks I suddenly get this error:
could not execute menu item(internal error)[exception] could not execute run action: the directory name is invalid
When I click on wamp, then I go to apache, then I select service then test port 80 and this is what I see:
when I write localhost, it goes there but when I click on Localhost and phpMyAdmin, i get this error:
please tel me how I can fix this . thanks
WAMP is trying to open your browser, but the directory in the settings is not correct. It could be that your browser is now located somewhere else. To fix this:
Edit the file wampmanager.conf inside your wamp direcotry.
Replace the full file path under the [main] section for the navigator parameter
Save the file
Right-click on the wamp icon and select refresh
Try it now
Good luck!
The paths are incorrect in multiple ini files and the wampmanager conf file. Here are the ones I changed since my installed moved from g drive to e drive. I had to change all instances of g:/ to e:/ as well as my chrome.exe location
wampmanager.conf:
in the [main] section update the path of chrome.exe or ensure it is correct.
wampmanager.ini:
change all instances of g:/ to e:/ (or whatever your install drive letter is)
php.ini (under /wamp/bin/php/php5.5.12/)
again, change all instances of g:/ to e:/ (change to your install letter)
Wampmanager started correctly once these changes were made.
I had a similar problem, and to get my WAMP server working again on my laptop I ran the executables for Apache and MySql independant of the WAMP system tray icon.
In Windows Explorer, I ran (elevated):
{wamp folder in my case C:\wamp}bin\apache\apache2.2.22\bin\ApacheManager.exe
This put the apache manager system tray icon in.
then I used the apache system tray icon to start apache server
Then I ran (elevated):
{C:\wamp}bin\mysql\mysql5.5.24\bin\mysqld.exe
This allowed me to use localhost\phpmyadmin, which to me demonstrates the php, mysql and apache are all working.
My web app was also back and running.
The age of my MySql version and apache version show how long this had been stable for.
I initially thought the problem may have been caused by a google chrome upgrade which included the notifications icon in the system tray, as the chrome upgrade was the only thing I recall changing. I unistalled chrome but this did not fix it - although this does not rule out Chrom Notifications being what broke it!
This appears to be an oversight on the WAMPSERVER developers. For some reason it does not translate the file path syntax from Linux to Windows, resulting in the following error message:
Aestan Tray Menu: Could not execute menu item (internal error)
[Exception] Could not execute run action: The directory name is invalid
To fix this, edit wampmanager.conf and replace the forward slashes in the file path with backslashes.
EXAMPLE:
Incorrect
editor ="C:/Program Files/Sublime Text 3/sublime_text.exe"
Correct
editor ="C:\Program Files\Sublime Text 3\sublime_text.exe"
Save the file, then right click the tray icon and select "Refresh". You should now be able to edit your files with your selected editor without issue :)
i have met this problem and fixed by editing 4 files
- wampmanager.conf in root
- wampmanager.ini in root
- php.ini in (wamp64/bin/php/php5.5.12)
- httpd.conf in (wamp64\bin\apache\apache2.4.18\conf)
I've previously had a Drupal installation set up in WAMP. It's still in my www folder.
I want to start work on another (Wordpress) site. I made a new folder in WAMP and set the Drupal folder to Drupal.old so that it wouldn't use it, but I could still keep it there.
Now when I go to PHP My Admin in WAMP it just displays a 404 error.
What am I doing wrong? I just need to install WP on my local machine
Francesca,
You should never put anything of yours in the www folder. That belongs to WAMP and is basically the localhost site. So by renaming it you have deleted the loclahost site and therefore phpmyadmin with is an alias off your now lost localhost site.
You should either create subfolder below the www folder for your sites like
c:\wamp\www\drupal1
c:\wamp\www\wordpress1
But that is not the best solution.
It is better to create Vistual Hosts, one virtual host for each of your sites.
Pop over to the WAMPSERVER Forum
Do a search on 'Vistual Host HOWTO' and you should find a tutorial on how they are setup.
I am very new to apache and django, so execuse me if this question is simple. I am trying to deploy an existing site to an apache server. For the time being, the site is still in development so I am only deploying it as a virtualhost on my local machine.
I am using Django's WSGI module in the deployment. In my site's config file, I have the following aliases:
Alias /media/ /home/tester/Desktop/siteRootDir/media
Alias /content/ /home/tester/Desktop/siteRootDir/content
WSGIScriptAlias /c /home/tester/Desktop/siteRootDir/deploy/site.wsgi
When I run apache and go to localhost/c I was getting the (13)PermissionDenied error in the apache log. To get around that error, I (admitedly stupidly) ran
chmod -R 777 /home/tester/Desktop/siteRootDir
I know that is not the way to deal with the issue, but I just wanted the site to work so I can continue its development.
So my question is, what are the correct permission settings to the siteRootDir directory and its sub-directories such that the site will run and I do not expose unnecessary files in the directory.
Also, I realize that this is not an ideal set up and I will likely run into problems when I deploy the site in production. Can anyone please suggest a better organizational approach to this?
Thanks!
The tightest permissions possible would be 0600 for files and 0700 for dir's and as a owner the user owning the apache processes. This user differs per OS and flavor (e.g. for OSX it's www, for Debian/Ubuntu it's www-data).
This would probably too tight for a development server. At least would you like to be able to modify all your files through your IDE of text editor, so either you should add ACLs for yourself (i.e. the user that edits the Django files, templates and static files).
Also, in a production server you want the apache user to be able to write to directories that hold web uploaded content. That would be somewhere in your static files section (or on a different dedicated static files server).