Forbitten Windows 8
Posted by: djdanni (---.du.xdsl.is)
Date: March 12, 2013 09:34PM

Hello. I am trying to acces phpmyadmin and i always get this Error
Forbidden

You don't have permission to access /phpmyadmin on this server.
Wuy do i get that?

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: RiggsFolly (---.as13285.net)
Date: March 12, 2013 09:35PM

What does the error message say in APache error log and/or php error log?

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: djdanni (---.du.xdsl.is)
Date: March 12, 2013 09:55PM

Here is my Error log
PHP Warning: PHP Startup: Unable to load dynamic library 'L:/wamp/bin/php/php5.3.8/ext/php_imagick.dll' - The specified module could not be found.\r\n in Unknown on line 0
[Tue Mar 12 20:25:07 2013] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Tue Mar 12 20:25:07 2013] [notice] Server built: Sep 10 2011 11:34:11
[Tue Mar 12 20:25:07 2013] [notice] Parent: Created child process 7676
PHP Warning: PHP Startup: Unable to load dynamic library 'L:/wamp/bin/php/php5.3.8/ext/php_imagick.dll' - The specified module could not be found.\r\n in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'L:/wamp/bin/php/php5.3.8/ext/php_imagick.dll' - The specified module could not be found.
in <b>Unknown</b> on line <b>0</b><br />
[Tue Mar 12 20:25:08 2013] [notice] Child 7676: Child process is running
[Tue Mar 12 20:25:08 2013] [notice] Child 7676: Acquired the start mutex.
[Tue Mar 12 20:25:08 2013] [notice] Child 7676: Starting 64 worker threads.
[Tue Mar 12 20:25:08 2013] [notice] Child 7676: Starting thread to listen on port 80.
[Tue Mar 12 20:25:08 2013] [notice] Child 7676: Starting thread to listen on port 80.

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: RiggsFolly (---.as13285.net)
Date: March 13, 2013 02:47AM

Do those errors not give you a bit of a clue??

php_imagick.dll does not come with php 5.3.x, you need to load it via PECL or PEAR or get it from their web site.
If you already did that then you probably got one that was compiled with CV6 and it should be compiled with VC9.
Or you got one that was not compiled for PHP 5.3


Try again

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: djdanni (---.du.xdsl.is)
Date: March 13, 2013 09:06AM

I have no clue. I just wan to know wuy the phpmyadmin gives me that error.

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: RiggsFolly (---.as13285.net)
Date: March 13, 2013 09:54AM

Show me the Apache access log please.

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: djdanni (---.du.xdsl.is)
Date: March 13, 2013 11:20AM

I get nothink in that log file

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: rmrevin (---.nationalcablenetworks.ru)
Date: March 13, 2013 05:07PM

The problem is that in windows 8 are short notations for ip. That is a script check comes ::1 instead of 127.0.0.1. Appropriately check Allow from 127.0.0.1 does not work.

Fixes a replacement in all configs Allow from 127.0.0.1 on Allow from ::1 127.0.0.1

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: djdanni (---.du.xdsl.is)
Date: March 13, 2013 05:34PM

In what files do i need to change that?

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: RiggsFolly (---.as13285.net)
Date: March 14, 2013 10:32AM

Right, Windows as of Windows7 comes with the ability to use the IPV4 network address range and the IPV6 network address range and by default they are both turned on.
IPV4 addresses look like this: 123.321.10.234
IPV6 addresses look like this: 2001:0db8:85a3:0042:1000:8a2e:0370:7334

The IPV4 address for localhost is 127.0.0.1
The IPV6 address for localhost is ::1


See
[en.wikipedia.org]
[en.wikipedia.org]
[en.wikipedia.org]


However, Wamp's security as of now ( Feb 2013 ) is only configured to expect the IPV4 address range, but the Apache that is delivered with WAMPServer is aware of both the IPV4 and IPV6 address ranges and is happy to use either or in fact both.
I am not sure how Windows/Browsers decide which range to use but it appears to be fairly arbitrary, so you can get either.

This is the route of your problem.

There are 2 ways you can go to solve this small anomily. You can either ignore the IPV6 address range or change the security to include the IPV6 address range.


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
KEEP COPIES OF ALL FILES CHANGED SO YOU CAN EASILY UNDO THESE CHANGES IF THEY DO NOT WORK FOR YOU

In fact copy c:\wamp to a backup location and then you can just replace
the whole folder if you have problems with your changes.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Option 1 is easier to do.
==============================================================

Option 1:
Ignore the IPV6 address range.


Use the wamp menus to edit these files where possible.

edit httpd.conf
change Listen 80 TO Listen 0.0.0.0:80
The 0.0.0.0 part tells Apache to only listen on IPV4 addresses.


edit c:\windows\system32\drivers\etc\hosts
If it exists, remove or comment out (comment is a # in colum 1) the line containing the IPV6 address for localhost >::1 localhost
(This makes the domain 'localhost' disappear from the IPV6 network, its existance is not hard coded anywhere it has to be mentioned in the hosts file to make it exists)
Make sure you have a line in the hosts file like this >127.0.0.1 localhost
(This makes the domain 'localhost' exists on the IPV4 network)

Wamps security should now work after a reboot. And
http://localhost
should now get you to wamps Apache installation. The exisiting security should also now work for phpMyAdmin,WebGrind and SQLBuddy


============================================================
Option 2:
Add the IPV6 address range to wamps security.


Again always use the wamp menus to edit these files where possible.

!!!! Make sure WAMP is set to 'Offline' before starting this part.


Now this is the dangerous bit!!!!! You must get these next 2 edits right. The text between the double quotes in C:\wamp\scripts\onlineOffline.php must match exactly that used in the httpd.conf file, so a copy and paste would be recommended. If you get this wrong the Online/Offline process will not work.

edit httpd.conf

Change
# onlineoffline tag - don't remove
Order Deny,Allow
Deny from all
Allow from 127.0.0.1

TO
# onlineoffline tag - don't remove
Order Deny,Allow
Deny from all
Allow from 127.0.0.1 ::1

Note we have added the ::1 IPV6 localhost address to the security, make sure there is a space between 127.0.0.1 and ::1.


Edit C:\wamp\scripts\onlineOffline.php
Change

$offlineText = "# onlineoffline tag - don't remove
Order Deny,Allow
Deny from all
Allow from 127.0.0.1";

TO

$offlineText = "# onlineoffline tag - don't remove
Order Deny,Allow
Deny from all
Allow from 127.0.0.1 ::1";

This makes sure that the Online/Offline process still works in WampServer. Make sure that this exactly matches your change above made to httpd.conf


Now edit each of the files
C:\wamp\alias\phpmyadmin.conf
C:\wamp\alias\sqlbuddy.conf
C:\wamp\alias\webgrind.conf

were ever you see >127.0.0.1 change it to >127.0.0.1 ::1
Ignore the lines that start with a #, as these are comment lines

This tells Wamp that whichever ip address from either address range you get for the domain localhost, is allowed to access the apache server.
Now whichever address range windows/browser picks for you when you use the
http://localhost
domain the security will allow you in.

edit c:\windows\system32\drivers\etc\hosts
In Windows8 you will probably see both domains in the file, but this is not guaranteed. When you are finished it should look like this.

127.0.0.1 localhost
::1 localhost

This makes the domain localhost appear on both the IPV4 and IPV6 address ranges.


When you get as far as accessing MySQL you will see that the 'root' user is configured so that it can be accesses from localhost and 127.0.0.1 and ::1 so that is all ready to go and needs no changes.

If you decide to change the password for the 'root' userid in mysql, make sure you use the same password for all the instances of root that exist in mysql. A complete MySQL userid is associated with a location, so it is not the same userid when you login from root@127.0.0.1 as when you login from root@::1. This is why there are 3 'root' userids in the default MySQL userid configiration.

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: djdanni (---.du.xdsl.is)
Date: March 14, 2013 12:34PM

ty all. This woorks now smiling smiley

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: astutonet (---.virtua.com.br)
Date: March 18, 2013 03:53PM

Hi.

I also have this issue in Win8, but with some differences.

In my case, I had two databases running perfectly on a laptop and added three more, migrated from another PC. I also copied the necessary files to the folder "www" so I could see the contents of the databases in the browser.

It happens that, after copying the databases, I can not view the content of the databases that already existed, nor of the new.

I also can not display the page content "Localhost".

The contents of the "phpMyAdmin" is displayed normally.

Even after to run the step 2 above, I get the following error message on the pages cited:

403 Forbidden

Forbidden

You do not have permission to access / on this server.


In apache_error.log, I have this error message:

[Mon Mar 18 11:41:33 2013] [error] [client 127.0.0.1] (OS 5)Access is denied. : Cannot map GET / HTTP/1.1 to file

Any idea?

Tks.



Edited 1 time(s). Last edit at 03/18/2013 03:58PM by astutonet.

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: zdy (27.17.16.---)
Date: March 21, 2013 07:18AM

The reason why it happens is IPV6. Windows 8 is by default an IPV6-first Operating System. How? Well just go to command-prompt and run the command

ping localhost
You will be getting response from ::1 i.e. the loopback address for IPV6. When you try to connect to the server it uses the port 80 along with IPV6 to locate it.
www.cusabio.com/ELISA_Kit-84601/ il-6 elisa kit

Options: ReplyQuote
Re: Forbitten Windows 8
Posted by: astutonet (---.virtua.com.br)
Date: March 27, 2013 10:46PM

Hummm... @Zdy, Tks for your reply.

The most practical solution I found to solve this problem, even with the hosts file configured, was reinstalling Wampserver.

After reinstalling, no more problems.

I think that is very interesting if we have new solutions for future cases.

Options: ReplyQuote


Sorry, only registered users may post in this forum.