I don’t have experience with bitnami so I don’t know how it changes the apache configuration but I would say the problem is the domain mapping. mywebsite.com maps to lets say /var/www/mywebsite but your wordpress is installed in /var/www/mywebsite/wordpress so the url to it isn’t mywebsite.com but mywebsite.com/wordpress and when you login it redirects you … Read more
You’re wanting to use MAMP, but VirtualHostX shows that Apple’s built-in Apache is running. You’ll need to stop it by running this command in a Terminal window… sudo apachectl stop Then, start MAMP using their control panel and try again. Also, make sure “MAMP” is set as your “Default Web Server” in VirtualHostX’s Preferences window.
It is hard to say whether it is overkill or not. Generally there are several type of caches need to be implemented, Opcache (for PHP codes), Query cache (for Database access), Object cache (for community type of website or shared server where content are constantly updated) and Page cache (for static content such as HTML). … Read more
WordPress keeps WP_HOME and WP_SITEURL in DB, this is set during initial installation and usually is the domain of your website, in your case it is a LAN IP. Your visiting site via WAN IP, but WordPress redirects to LAN IP, causing redirect loop which obviously fails. To fix this, change WP_HOME and WP_SITEURL values … Read more
I found out that the issue was on .htaccess file. I restored the file to the original wordpress config and it work fine again # BEGIN WordPress RewriteEngine On RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress Here is the … Read more
I don’t think this can provide a solution but hopefully I can help you troubleshoot a little. Firstly, let’s go over debugging: Debugging You’re saying “white screen of death”, but the screenshot you provided looks more like it’s hanging while trying to load the page. Typically, the WSOD appears as exactly that – a completely … Read more
I believe the answer was a messed up entry in either site_url or home within the MySQL database. I changed those settings and the issue was resolved.
You can adapt the site url which is stored in the database based on what domain you are viewing the site from. Add the following to wp-config.php: define( ‘WP_HOME’, ‘http://’ . $_SERVER[‘HTTP_HOST’] . ‘/yourwebsitename’ ); define( ‘WP_SITEURL’, WP_HOME ); If you use a subdirectory install (ie: you view the site from http://192.168.0.2/yourwebstename but the WordPress … Read more
Codex has an article on Changing The Site URL, you can edit values in database or override them in config. To have your site work from root you can either relocate WP there altogether or configure it to support root of the site, while still residing in subdirectory. See Giving WordPress Its Own Directory on … Read more
Judging from other threads, here are the two most common causes of this problem on freshly built servers: .htaccess override is disabled by apache2.conf Apache mod_rewrite module isn’t enabled. In the file /etc/apache2/apache2.conf: <Directory /var/www/> AllowOverride All </Directory> “AllowOverride” is the switch that tells Apache whether to listen to .htaccess files or not. WordPress relies … Read more