Unable to load my site after installing Nginx with python-certbot on Ubuntu 16.04 - nginx

Yesterday, I was securing my website by adding SSL using the technique given by you. The link is given below
https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04
I was able to add the SSL but then my website homepage started showing the Nginx page instead of my webpage. I deleted it from the root server and also I removed the new account that I made on ubuntu. My current version is 16.04. Can you please look into this matter and tell me how to solve it so I can able to load my website without SSL? If you can tell me what did I do wrong here?
The screenshot is attached below

Related

The requested URL was not found on this server. Error after installing wordpress

i have installed WordPress on my Ubuntu machine. i have also installed all the required resources like PHP, MariaDB and others.
At first i navigated to the sample site and i even made some few changes. Then after tempering with settings, when i try to go back to my sample site am getting an error.
This is the image error.
I have tried to do everything i could but still getting the same error.
How can i resolve this

localhost redirecting to http://localhost.192.168.1.33.xip.io/

I recently installed wordpress on my Ubuntu 16.04 machine. In order to connect to a wordpress website locally I made some configurational changes because of that whenever I try to connect to localhost, browser directs my requests to http://localhost.192.168.1.33.xip.io/ automatically. I am not able to access my local Wordpress because of this. Please help.
I had the same issue and solved. If you are using bitnami, you need to change site URL in bnconfig.
sudo /opt/bitnami/apps/wordpress/bnconfig --machine_hostname YOURDOMANIN
For more details, please have a look at bitnami forum.
Good luck

WordPress Multisite Redirect Loop After Botched Plugin Update

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

EC2 and Wordpress Times Out When Downloading Anything

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.

Wordpress installation not get completed in Wamp server

i have installed wamp server on windows 8, and trying to install wordpress on it, but while installing it could not complete it. it's showing me the error like
http://localhost/wordpress/wp-admin/install.php?step=2
after that the process stops.
Screenshot:
I had refered the question on Wordpress Installation not getting completed but it could not help me.
Can anyone sort this out.
Wordpress is normally a breeze to install.
Have you read this Famous 5-Minute Install and the pre-requisites on the same page.
I had the same problem, I resolved it after finding this: http://wordpress.org/support/topic/installation-hangs-on-step-2-after-creating-basic-dbs-without-admin-user?replies=16
so i just edited the php.ini file as suggested in that post (increased the max_execution_time) and it worked for me.
I had the same issue. The fix for me was that I needed to include the port onto the localhost when assigning the database host.
Like: localhost:8080.

Resources