I already got a domain example.com and a subdomain configured under analytics.example.com.
I have ghost CMS running under example.com and want to install Matomo on the same Digitalocean host under analytics.example.com.
I already configured a second site on nginx. Permissions on the corresponding files in /var/www/matomo are set correctly, however, the index.php is downloaded instead of being executed. Any clue what is happening?
I am inclined to say that php is not working correctly. However, ghost comes with php, so it must be working?!
Related
I'm setting up an existing Laravel app onto a Windows machine for testing. The windows machine has a virtual machine setup and is running Linux.
I've edited the Windows hosts file to include the IP address and if I go to http://app.dev I can see the Laravel app as expected. however, as soon as I try to go to http://app.dev/page I get a 404 error.
The routing is set up correctly and this works fine on my typical dev machine, which is a Mac. Is there an additional setting I need to apply to make paths beyond the root path for the domain work?
If using Apache, make sure you have mod_rewrite enabled and either AllowOveride on (to use the htaccess file) or make the entries in the Apache Virtualhost to handle the rewrites.
Magento 2.0.6
Bitnami stack
Google compute Instance.
So after going up and down through all support for Bitnami Magento stack on the web, I decided I am the only one with this issue.
So I had my site running flawlessly with the Stack 2.0.6 given by Bitnami through the Cloud Launcher then I added an extension to setup the outgoing emails. And now I am unable to access my website using the domain name. If I enter my Domain name on any browser or computer it takes me to "Apache2 Debian Default Page" if I add /index.php to my Domain name it takes me to a semi loaded version of my Magento store. If I attempt to go to domain/admin it tells me, basically a 503 error.
There has been an error processing your request
So then I went through all my folders on the cloud and tried finding that index.html it loads with just the domain name and deleting them. After finding and deleting them it still loads the "Apache2 Debian Default Page". Very frustrating.
So I decided to take a break then come back and thought maybe somehow the conf files are telling it to only open index.html first. So I went through all the configs and nothing is directing it that way.. so it seems everything loads correctly in the cloud instance no errors on the back end starting or restarting Bitnami script just the front end is broken somehow apache2 isn't reaching the Magento folder correctly.
Then I decided, well if all else fails I will start a new Cloud instance with the new 2.0.7 Magento Bitnami. Wrong instantly upon setup it directs the domain straight to "Apache2 Debian Default Page" except if add /admin to the fresh instance loads the backend and only loads the front end if I manually add /index.php to the domain name.
Am I missing something?
it has configuration in
/opt/bitnami/apps/magento/conf/
make sure to make changes in that
you can change DirectoryIndex index.php in htaccess.conf
after that you can restart the apache by
service bitnami restart apache
I read and tried several methods and none worked. I always get either 400 or 500 error. The app works perfectly on localhost.
What are the exact steps in order to get Laravel 5 up and running on a VPS with DirectAdmin CP??
Please don't link to other questions as I read them all. Some don't even work with Laravel 5 anymore.
Note: DirectAdmin sees public_html as the document root.
I have SSH root access and Composer is installed.
VPS Configs: Apache 2.4.9 and PHP 7.0.3.
Turns out DirectAdmin has a section where you can define custom Apache configs (including Document root). So here are the steps:
1- Login to your admin area (as System Admin)
2- From Extra features select Custom Httpd Configurations
3- Select the domain you want to config
4- In the textarea at the top enter the following:
|?DOCROOT=/home/username/domains/example.com/public_html/public|
5- Click save. Now wait for a minute or two and voila! It works.
Obviously you need to change the username and example.com according to your setup.
Read more about this feature.
I created a local WordPress site and in XAMPP set it up with Virtual Hosts so the address test-wp.dev was the home adress. All was working fine and then for some reason I decided to turn off apache, leave mysql on and try the build in server.
So I navigated to C:/xampp/htdocs/test/wordpress/ and ran php -S localhost:8080
It worked fine. However, today I went to go back to test-wp.dev using the Apache server and it keeps redirecting to localhost:8080. I don't want to use the built in server now. I want Apache.
Where do I "unbind this" or free up that port or whatever. I don't want to have to run the built in server for that folder anymore.
Thanks.
Windows 7
PHP 5.6
In our current environment, if any changes need to be made to the code, these changes are directly coded and updated to the Live server. GWe would like to set-up a development server where we can test our changes before uploading to the live site.
I have attempted to build a development site locally by installing Apache, PHP & MySQL and copying all the htdocs to the Apache folder. However, when I try to access localhost/ it redirects me to the server default page. Any ideas on why this may be happening?
Have you setup Apache VirtualHost and configured it for your sites Document Root?
I would look into your production site and see what's configured.
Also note that when you're setting up a dev/prod environment you will need not just PHP/Apache/etc.. install but also any packages/mods/libs that they are using installed as well.
For Example: if you're using Mod-Re-Write with Apache you need to install and enable it