Search the Community
Showing results for tags 'IPv6'.
Found 2 results
-
Hi, I noticed that started to get some spam comments on my site from IPv6 adresses, but unfortunately I cannot easily see from which addresses since IPv6 addresses get logged as 0.0.0.0. I found there is an (rather old) issue regarding this on Github: https://github.com/ryancramerdesign/ProcessWire/issues/1596 Is a fix regarding this on the roadmap? I would prefer not to use $_SERVER['REMOTE_ADDR'] or something similar. Thanks in advance! //Jasper
-
EDIT I got it working by adding a Rewrite rule to htaccess to specify the correct root. I wonder what changed in Windows 8 making this necessary It seems that I am having some issues with ProcessWire when running locally on a WAMP environment (specifically Windows 8). I had a working Windows 7 AMP environment and ProcessWire apps were working with ease. After updating to Windows 8, Apache seemed to be throwing 403s all over the place. It turned out WIndows 8 uses IPv6 primarily so ::1 references needed to be added to the apache conf file in addition to 127.0.0.1 references. After this change, all of my other local sites (WordPress, Drupal, Joomla, etc) started working again. However, my ProcessWire apps are still seeing issues. Basically I can navigate to and load the index page, but every other sub page results in a 403 (or 404 if I remove all Apache deny rules). I'm guessing something is off in ProcessWire's routing? Anyone have any insight on how pages are being served up and if there's a way to fix this? tl;dr Running Windows 8 AMP environment and ProcessWire is not serving up pages correctly
