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.
Related
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?!
I have a laravel 8 app hosted on https://tonguelearner.com and it's running only on my Mac OS which I used to develop it. On other devices including mobile, only home page is working and other throws 404 server error.
Not sure how to identify the problem. Need some help.
If only home page works, it seems laravel can't handle routes except root of yout site. If your htaccess is over there and proper, enable mod_rewrite on apache;
sudo a2enmod rewrite
Suddenly my PHP site, which is developed in core PHP in localhost is trying to connect to HTTPS.
Local path: local.trekmania.com
hosts setting: 127.0.0.1 local.trekmania.com
apache2.conf:
<Directory /var/www/wp-projects/trekmania.com>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
Yesterday the site was loading fine, but today I the following error has popped up suddenly.
This site can’t provide a secure connectionlocal.trekmania.com sent an
invalid response. ERR_SSL_PROTOCOL_ERROR
This is happening for another site as well.
None of these sites has any .htaccess entry to force HTTP to use HTTPS. Both the sites are developed in core PHP. Another core PHP site, however, is loading properly. This has URL rewriting rules set in its .htacess. WordPress sites are also loading OK.
Google could not help to find an answer which addresses this particular issue.
I tried the following solutions
https://galaxyinternet.us/google-chrome-redirects-localhost-to-https-fix/
And
by deleting localhost, local.trekmania.com, 127.0.0.1 under Delete domain security policies at chrome://net-internals/#hsts
None of the above solutions worked even after restarting Chrome and the PC. The site is always redirecting to HTTPS! The same thing is happening in Firefox as well.
OS: Ubuntu 16.04
Please let me know how can I resolve this issue.
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've installed php support on my IIS7 via FastCGI. Under IIS I've created a new website that host Joomla. Uploaded my site and it works fine.
Now I wanted to add another application under that website so that when someone goes to my url http://www.mysite.com/application_name he will get to the site hosted under that url.
What ends up happening is that on Chrome and Firefox I see the Application site, but on IE it points me to the root of the site (http://www.mysite.com/application_name points me to http://www.mysite.com/).
I've played around with .htaaccess file but had no luck. I even removed it entirely but it still does that and even when removed the entire joomla site keeps on working.
What configuration am I missing?
Thanks
.htaccess works only under Apache servers, it doesn't work on IIS. You should work on the web.config file.