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
Related
Recently I have moved our 25 websites on Google cloud hosting successfully.
but today I am getting strange issue, after move a website (which is working fine on previously hosting) on Google cloud hosting.
my WordPress categories suddenly stop working and it says 404 I tried everything changing permalinks replace .htaccess but no luck. I tried changing permissions all thing nothing worked.
I create a new instance with WordPress which is working fine with sub category and post working but with index.php like this http://0.00.00.00/index.php/front-page/post-url/ (which reminds me yahoo hosting issue with WordPress).
This problem is same as I am having on my in-house server which is on already Debain os.
I need solution because I am not a Server administrator guy so if anyone having same issue or solution?
got a solution and it worked .htaccess Is Not working in Linux(Debian) Apache2
in my case apache2 configuration file location is /etc/apache2/apache2.conf
and i just replaced AllowOverride None to AllowOverride All then restart apache service using following command
service apache2 restart
after restart go to WordPress admin and remove index.php from permalink.
When ever I try to open wordpress website on my localhost I get below error.
HTTP Error 404.3 - Not Found
The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
I have tried enabling HTTP activation but that did not work.
I have installed PHP for IIS from microsoft web PI, that did not work.
I think there is handler mapping missing, I am not able to map handle.
install wamp or xaamp and start php and mysql Service.
create a folder for example "site".
Copy all worpress folder and file in to www/site in wamp server
and enter the "localhost/site" in the browser and install wordpress quiqly.
soon wordpress goto run
Go and download the WAMP http://www.wampserver.com/en/
Its a set for web developers, that includes php, apache and mysql.
You can se localhost to act as a real webserver, you can find online many tutorials and how to
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 want to use phpList when user signs up in my website.
Currently i am working in local. To install phpList should i only copy to content of public_html/lists/ folder or whole public_html/lists folder into my local folder.
I tried this.
1)
I am bit confused here. Because i tried both in documentation it says you need to copy the content of the public_html/lists/. When i am doing this it successfully installed but when i try to create new subscriber page and try to save changes it give me this error "The requested URL /lists/admin/ was not found on this server."
2) When i copied lists/ folder into local server and when i tried open admin page it displays this. it hasn't even shown installation process which it normally does(database initialization).
To install phpList into local what should be copied into local folder?
I had this same issue after installing a second instance of PHPlist. The way I was able to fix it was by rebooting my server entirely. Upon logging in, I got the standard installation page. (Otherwise, I continued to receive the missing tables and invalid login page, even when rebooting XAMMP on a Windows Server.)
Using CPanel/Softaculous to install Mediawiki on my hosted website appears to install fine. Though not sure how much the installer checks.
I then setup a sub-domain such as wiki.mydomain.com to accept requests there.
After that, I also setup SSL cert in Cpanel. The cert is self-signed because at the moment I am just testing out the wiki and everything before I decided if I will purchase a cert.
Then, if I attempt to go to http://wiki.mydomain.com. I get the landing page of MediaWiki but if I attempt to go to https://wiki.mydomain.com I get nothing but a blank browser window.
Now, if i go to https://wiki.mydomain.com/index.php, I get a 404 error (I created a simple html page with a 404 error message then modified my .htaccess to show it on the 404).
When looking at the logs, it appears to be trying to find the index.php file under /home/mydomain/public_html/index.php instead of /home/mydomain/wiki/index.php.
Very confused on why this isn't working at all. I can post some configs and things as well but this account is a newly created CPanel account so not much as been done on it other then installing the wiki software.
(Edit) This is using SharedSSL. I couldn't get it to work without it. Some reason even after I made sure the site was the only one on the IP Address using WHM it was still showing it as a shared IP. :P
Fixed the SharedSSL by using this information: Cpanel Forums
You will have to make a new install of MediaWiki via Softaculous. Go on the install form you will get an option to "Choose Protocol" choose https:// there and in the "Choose Domain" dropdown choose your subdomain https://wiki.mydomain.com leave the "In Directory" field blank and then click on Install button.
Then you should be able to access the MediaWiki install at https://wiki.mydomain.com
I think the reason for this issue is due to how cPanel works with sub-domains and SSL. From what I gather, this appears to be a SSL cert issue since when CPanel rebuilds the httpd.conf using /scripts/rebuildhttpdconf command, it does not create a SSL virtual host for the sub-domain. Also, the parent domain works fine.
I ended up putting the wiki in /home/mydomain/public_html/wiki then setting up redirects for http://mydomain.com and https://domain.com to point to https://mydomain.com/wiki.
For now, that's all I could figure out to fix the issue was to drop the sub-domain.