I signed-up in AWS(Amazon Web server) for my Wordpress site. I also installed wordpress through AWS-ec2. I followed the steps inside AWs-ec2 documentation like LAMP and others needed.As I go through inside AWS-EC2 environment, I launched an instance where i can work for my Wordpress. Having an instance creates a default public domain name for my wordpress (http://ec2-xxx-xx-xxx-xx.us-west-2.compute.amazonaws.com/).
Now, my problem is I want to make our own domain name like example.com as our wordpress site instead of default domain name given by AWS-ec2. and, what are other requirements or tools needed to deploy it? We bought our domain name in GoDaddy.
Your answers will be highly appreciated.Thank you.
DNS
You need to start with setting up DNS. To do this you can use the service provided by Godaddy or use Route53 in amazon. You will set up records to point to your instance.
Apache
If you are using Virtualhosts, you will need to set up your Virtualhost to respond to the new domain name. If you are not using virtual hosting, it will return the same site regardless of which domain you used.
Wordpress
Wordpress does save the domain you installed it with in the settings. If you change the domain these settings may cause some issues. If you can't get into the Admin UI to fix this, update wp_options table in mysql.
Related
In 2018 I made a Wordpress site by using a Bitnami AMI for a AWS EC2. Fine developed a site and created another custom AMI of the finalized Wordpress site. This was for domain X.
Now in 2020 I wanted to duplicate that website by using this custom AMI for domain Y. I have created an EC2 based on that custom AMI and instance went online without problems.
The problem is now that I can not reach the site by its url, I got blocked by "This connection is invalid", I also see that certificate is still based on the domain of 2018, thus is invalid. So I think that the issue is caused by the SSL configuration based on domain X while it is iinitiated for domain Y. But since I am not able to reach the site neither the admin panel, I am wondering how I can disable the SSL/HTTPS enforcement so that I can reach the site and admin panel?
I do have access to SSH, so probably I should be able to do something from there? But totally not known with that type OS and usage via SSH.
Bitnami Engineer here,
As you created a snapshot of the 2018 instance, the new instance has the same configuration you had at that time. Please check the following items so you can update the certificates and the app's configuration to work properly using your new domain name:
The certificates are configured in the /opt/bitnami/apache2/conf folder by default. You probably substituted the ones we include with valid certificate files for your domain in 2018. You will need to substitute the server.crt and server.key now with the new ones.
https://docs.bitnami.com/aws/apps/wordpress/administration/enable-https-ssl-apache/
Regarding the WordPress configuration, we have configuration tool that takes care of updating the domain name in the database. Can you take a look at this guide?
https://docs.bitnami.com/aws/faq/configuration/configure-custom-domain/
You will basically need to run sudo /opt/bitnami/apps/wordpress/bnconfig --machine_hostname my-new-domain.com.
I also suggest you check the WordPress' configuration file (/opt/bitnami/apps/wordpress/htdocs/wp-config.php) to see if you edited the WP_HOME and WP_SITE parameters there.
I have installed a WordPress multisite by bitnami on AWS EC2, and then configures Route53 to assign a domain name to the website. I have been unable to access the subdomains created since then.
I get this error whenever i try to access the website. Even, the dashboard can't be reached.
I have updated the .htaccess file as per the setting available in wordpress admin.
I have had a similar issue. You have to add a new CNAME record in the DNS records with the subdomain name, pointing towards the website. Alternatively, you can also add a wildcard '*' CNAME to make sure your multisite works without issues.
Also, make sure where your DNS is being resolved if your DNS is being handled by your domain registrar, then you will have to make changes there.
Hope this helps.
I'm pretty new to the Plesk AdminPanel. I own a Domain called riggiramone.ch. For a friend's project I'm trying to set Wordpress up on the subdomain mugi.riggiramone.ch. I did set up the subdomain and made it point at a subfolder of httpdocs (httpdocs/mugi). Then I have installes wordpress via the Plesk-own tool there.
My problem is that the subdomain mugi.riggiramone.ch is not reachable! I don't know why, I checked all the permissions.
Is there anything I did forget?
I think you are using external DNS server and due to that you are getting this issue. I will suggest you please check your main domain DNS zone and update the correct "A" record for your sun-domain and once you update it correctly you will not get any issues with your sub-domain.
I'm not sure if this is possible or what, I just thought about it.
I have a page in my site www.mysite.com/thispage
I want to change the whole URL of that page.
www.mysite.com/thispage to www.thispage.com without transfering and configuring another set of files and databases.. My site is in wordpress. Is this possible?
Sure - depending on your hosting settings. You can buy the domain name "thispage.com" and then ask your hosting company to set it up to be hosted in the folder "thispage".
Just a heads up - usually hosting companies charge more to host a domain name like this (or host multiple domain names).
Then you'll need to edit the settings within Wordpress to reflect the new domain name (under SETTINGS).
Our company is trying to transition to WordPress Multisite but we have several issues working against us at the moment. We host WP outside our server environment (we use Amazon for our WP sites) so we actually have to use an URL proxy to our Amazon servers. The other issue is that we needed to install Multisite in the root of the folder so the domain is http://100.10.20.30/foldername but we can't proxy that to http://www.domain.com/foldername because that is a live site that we're not moving to WP any time soon. So, of course, the problem we're running in to is that the IP is showing up not only in the source code but in Google now as well (which we don't want).
Does anyone know of anything we can do to keep the IP out of the source code/Google? I was thinking about rewrite rules in the htaccess file but didn't want to do anything until I had some better ideas.
Also, I can't use the domain mapping plugin that everyone seems to suggest for this type of issue because our sites aren't hosted in the root of our server (a prerequisite for the plugin).
So to break it down, this is what we need:
Multisite Parent Blog <-- This has to be the IP address
Multisite child blogs <-- Domain name but when we set the actual proxied domain name in the settings we get a 404 error because it's not looking in the right place. It's looking for an actual folder on our internal servers.
Thanks!
Found the solution myself. Posted below:
In the Multisite dashboard, click on "All Sites" then administer the specific site.
Under the "Path" field, you'll need to deselect the "Update siteurl and home as well."
Save changes.
Click on "Settings" tab.
Change the URL in the following fields: "SiteURL" and "Home"
Save changes.
When all is said and done, the IP is showing in the "Info" tab but it changes the URL in the source code to your domain.