Jump to content
Froxlor Forum

Search the Community

Showing results for tags '404'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Froxlor
    • Announcements
    • Feedback
    • Development
    • Bugs and Feature Requests
    • Trashcan
  • Support
    • General Discussion
  • Other Languages
    • German / Deutsch

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. My main site is WordPress and is installed in /var/www/mysite.com and I just installed froxlor in /var/www/froxlor. And when i went to http://{your-ip-address}/froxlor that trigger's WordPress' 404 page. Do I have to set up a special vhost to access froxlor? Or do I need to add something to the .htaccess to avoid WordPress trying to find a page that matches froxlor? OR, do I need to extract froxlor inside /var/www/mysite?
  2. OS: debian 7 wheezy Webserver: nginx/1.2.1 PHP-Version: 5.4.36-0+deb7u3 MySQL-Server-Version: 5.5.41-0+wheezy1-log Webserver-Interface: FPM-FCGI System-Auslastung: 1.14 / 1.18 / 1.25 Kernel: 3.2.0-4-amd64 (x86_64) Webalizer V2.23-05 Since upgrading to froxlor 0.9.33.1-1 this is the first new customer I created. For this customer the webalizer stats do not seem to work. The webalizer dir ist there and has current stats, but the domain subdirectories are not created. Also, the main webalizer directory cannot be opened, since all /webalizer locations point to webalizer/<domain>/, which does not exist. So opening <domain>/webalizer always leads to a 404 error. I tried enabling the domain specific log file, but that doesn't seem to work at all. even after deleting and recreating the vhost file, it still uses the customer logfile. Where can I further look for the cause of this error?
×
×
  • Create New...