So I've seen a bunch of questions like this, but many of them have no answers or the setup seems to be slightly different, so I thought I'd venture a new one.
I also apologize if some of this is vague and rushed, I'm sort of pulling my hair out trying to figure things out, but want to give as much detail as possible.
So I have a multisite WordPress installation on a Google Compute Engine instance. It was launched from the Cloud Launcher (https://console.cloud.google.com/launcher/details/bitnami-launchpad/wordpress-multisite). I have three sites running, one at mydomain.com, one at dev.mydomain.com, and one at staging.mydomain.com. It's all been working great for the past several months, but this morning a colleague was updating a plugin (Beaver Builder in case that turns out to be significant), and perhaps simultaneously taking a backup with Updraft Plus. In the middle of the update/backup, the browser redirected to a long error saying the update failed, and from then on the site was showing a 500 Server Error.
I got in to work about half an hour later and noticed it was showing the "Apache2 Debian Default Page". I took a look at the httpd.conf, and noticed the DocumentRoot was pointing to the default Apache folder. I tried changing it to the WordPress install folder, and then was getting a different error related to permissions. I set the file permissions of the wordpress install to the recommended settings, and after that both subdomains worked. The root URL was kind of working -- it redirected from mydomain.com to http://IPADDRESS/wp-signup.php. I looked in the wp-config and saw that DOMAIN_CURRENT_SITE was now set to the IP address, as well as the home and site url fields in the database. I changed them all to the domain name, and started getting a redirect loop error.
So for now I've left it as redirecting to the IP address, and added a NOBLOGREDIRECT setting to the wp-config to stop the wp-signup.php redirect. I am obviously not great at sys admin things, so I have no idea what to try next. I've ruled out the htaccess, plugins, and DNS settings (DNS hasn't changed).
Any help or direction would be greatly appreciated!
If you got the Debian Apache page then it is highly likely that someone installed the Debian apache2 package, which conflicts with the apache bundled in the stack. I advise you to uninstall the Debian Apache:
sudo apt-get remove apache2
Then restart the server services:
sudo /opt/bitnami/ctlscript.sh restart
Related
Let's say I have domain sxz.me.
Hostname is sxz.me, server is up and running. Unfortunately when I was typing in address sxz.me, it automatically redirected me to IP address 141.xxx.xx.xxx.
My point was to make it as domain name, not IP address. So I changed something in VestaCP that didn't work.
As a next idea, I have installed a plugin, which was redirecting IP address into sxz.me .. It worked! It started redirecting 141.xxx.xx.xxx into sxz.me. The problem was that sxz.me still didn't work e.g. didn't read files uploaded through ftp.
Then I've got genius idea of resetting the server from hosting support. I did it and then for whatever reason WordPress admin panel from 141.xxx.xx.xxx stopped working. I couldn't access it.
I've changed everything in VestaCP in the way described in this video.
Before it was also changed similar, but some parts were missing. We were waiting for DNS propagation and unexpectedly sxz.me started working! Almost there, but problem was that I still couldn't copy files from 141.xxx.xx.xxx by plugin, because of no access to WP admin.
I know there are also different ways, but that was my first idea. In the meantime I've started installing WordPress according to config.php from zero on 141.xxx.xx.xxx and website gone again! It just crashed somehow and started redirecting me once again to 141.xxx.xx.xxx so I'm completely confused and don't know what to do.
Domain doesn't work at all.
I have a a WordPress multisite install (using subdomains, not subfolders) running on EC2 (with Cloudflare for DNS). It is working good.
I am starting a new project that I want to setup a subdoamin for that is not using the multisite install. I have been trying for a few days to get it to work, but i cannot get it to stop sending trafic to wordpress (which is telling me there is not site set up (I hae set nothing up in wordpress as this project has its own site / code that I want to keep seperate)
What am I doing wrong?
Thank you?
After quite a while of banging my head agenst the wall I figgured it out.
How I got it to work was I went into the Apache config file (httpd.conf) and changed the server name to a fake address, then wet into vhosts.conf and created a virtual host for every site on the server, including the main one (that had been listed in the main conf) and the wildcard (for multisite).
I made sure the wildcard was listed LAST. After restarting the server it worded like a charm.
I put up a WordPress site on an EC2 instance (Linux, micro). I couldn't get the install of WordPress using ssh command line because it would constantly time out. But I did get it working by Ftping the files to my server. Now, everything is working but when I try to install a new theme or plugin through the wordpess admin interface, I only get the timeout error.
I have no idea why I'm getting timeouts when I connect to the www.wordpress.com site (for the install or plugins or themes), but that seems to be the common denominator.
Does anybody know what might be going on here?
Thanks
It turns out I forgot to include https for outbound connections in the security group.
I installed a clean Wordpress on AWS Elastic Beanstalk (Separate MySQL database on RDS and multiple EC2 instances (AWS Linux 64bit PHP 5.5)). I did some testing and was able to scale the system up to multiple servers and back down - everything was working beautifully. Problems started when I changed permalink settings in Wordpress from "Default" to "Post name", after which I tried to access Wordpress Hello world sample page again and got 404 error with an error message: The requested URL /hello-world/ was not found on this server. This only happens sometimes. If you keep clicking on the post link, many times it serves the page right (with the post name correctly in the URL), but sometimes it gives 404. I deleted the environment and started from scratch but got the same result.
Any idea how to fix this? Any other recommendations to consider when setting up auto-scalable Wordpress site on AWS?
Thanks for all the help and advice in advance.
Does apache have the permissions to rewrite the .htaccess file? Never used beanstalk but in AWS EC2 mostly this is the solution. In your console try this command
sudo chown -R apache:apache /var/www/html
/* Change the directory, if your wordpress is installed somewhere else */
I've followed several guides on how to migrate my existing Wordpress website onto my local computer, running it offline with XAMPP.
Everything appears to be installed, all my own files from wp-content, the database, all things configured to point at [http://localhost/wordpress/], however when I go to any address such as "[http://localhost/wordpress]" it redirects me to "[http://localhost/wordpress/wp-admin/install.php]". On a previous attempt, before reinstalling and trying again, I followed the install process, and it was a fresh website, without any of my content.
I've seen this problem appear before (read a comment), however the solution didn't apply to me (improper address in wp-config.php. I've followed all the instructions to the letter, but I'm getting this redirect suggesting something hasn't gone right. I suppose the fix is small, however I can't figure out what to do. Can anyone possibly provide some help?
You might need to go into phpMyAdmin and update the siteurl entry in the wp_options table. It should probably be something like http://localhost/yousite/ Have you done this?
For anyone else struggling with local WordPress development 5 years on, you could try using Docker instead of XAMPP.
I made a repository that will get you up and running quickly with it, it takes a pre-existing WordPress site and allows you to run it on localhost - https://github.com/lumonald/existing-wordpress-development-docker/