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? 

 

 

I'd guess you already have a special vhost for your wordpress, elseway it would make no sense why you hit its 404 handler...A common default vhost points to /var/www/, that's why we can say: open http://[ip]/froxlor ...

Yes, I have a custom vhost for WordPress, but even if it were the default vhost that would still happen as www.example.com/froxlor would still look like a "page" to WordPress so WP would try to match it and fail. Does this mean that I need a custom vhost for Froxlor? 

Froxlor handles its own stuff. You should add a customer and move the wordpress stuff in the customer docroot with its own domain/subdomain.

On 2/25/2016 at 9:20 AM, d00p said:

Froxlor handles its own stuff. You should add a customer and move the wordpress stuff in the customer docroot with its own domain/subdomain.

 

By own domain/subdomain do you mean have froxlor at froxlor.mysite.com instead of mysite.com/froxlor?

Thanks for asking that Zigger. I wasn't sure either. I'm sure "customer" is a typo, but I can't figure out what d00p was trying to say. @d00p, could you clarify? 

No, customer was not a typo.

 

Open froxlor, add a customer, move wordpress to the customers docroot, remove any custom vhosts and let froxlors cronjob create them for you.

 

Then you can open wordpress with the standardsubdomain created by froxlor or you add another domain for the customer and use that.

I'm talking about my own server setup and don't see where any customers figure into the equation, so I'm very confused about your use of the word here. What does adding a customer mean/entail? And I can't open froxlor, that's the point of this thread. 

1) remove all custom vhosts and let the default point to /var/www/ as intended. that way you can open http://[ip]/froxlor

 

2) you do know what froxlor is for dont you? I'm a bit confused that you don't know what i mean with "customer". That's what froxlor is about, providing an interface for shared-hosting customers (and you as admin of course...)

Thanks for breaking it down for me. Since a customer is someone who buys things and I thought Froxlor was a server management UI somewhat akin to cpanel, I didn't see the connection. I appreciate the clarification and will try your suggestions a little later on. 

We are somewhat like cpanel....it's the same thing there....you may want to call it "users" instead of "customers" if it suites you better, but it stays the same somehow. 

16 minutes ago, Sofia Bovino said:

I am facing the same error, and i tried the solutions which are given above but still facing the same:( anyone for help please

Too less information, what is your EXACT problem, provide steps to reproduce/test, give information about setup, distribution, vhost-content, etc.etc.etc. please

For future reference. If you have installed froxlor via package manager (for me ubuntu 18.04). The default directory is /var/www/html for apache server. You have to edit default config file and change the webserver default to /var/www

```

nano /etc/apache2/sites-available/000-default.conf

```

Once you have done it restart the apache server and go to http://<IP>/froxlor you should see the installation panel.

4 minutes ago, Sisir Adhikari said:

For future reference. If you have installed froxlor via package manager (for me ubuntu 18.04). The default directory is /var/www/html for apache server. You have to edit default config file and change the webserver default to /var/www

```

nano /etc/apache2/sites-available/000-default.conf

```

Once you have done it restart the apache server and go to http://<IP>/froxlor you should see the installation panel.

1) old thread

2) this is mentioned in our wiki already

This thread comes up as #1 on google search. Could be helpful for people coming from search result