I am currently migrating my website that was hosted on GoDaddy to an Amazon Linux instance. Everything has worked so far using elastic IP that I allocated, but I haven't been able to access other pages using the GoDaddy domain I transferred from my original website.
I have tried to change the site address/URL structure in the Wordpress settings, but I almost broke my website (TWICE!). Should I be changing one of the .htaccess files instead of the native Wordpress setting?
My elastic/public EC2 instance IP is: 52.26.232.168
The domain I would like to point to the IP is: artrantsbyaj.com.
Any help is greatly appreciated.
NOTE: I do not yet have a high enough reputation to post images yet, I apologize.
Try to refresh your permalinks:
Go to the permalink settings and save them (do not change anything, only click on save to refresh your permalink structure).
Test it and let me know if you have any problem.
Regards.
Related
http://sidparmar.ca/portfolio/ This is my portfolio website and an only home page is working with the domain name. Every link is broken unless replaced by IP of my VPS which is 64.20.53.42.
So usually it should work like sidparmar.ca/portfolio/contact/ (give me an error "The requested URL /portfolio/resume/ was not found on this server.")
but currently, it is only working if I type 64.20.53.42/portfolio/contact/ as URL.
Please let me know if you have any suggestions/advice or pointer that I should look into. Any help is appreciated.
Has your site been like this since you installed Wordpress? If so, then where did you install wordpress (i.e. what directory)? It looks like you did not install it in the web root directory of your web server. Also, when you installed Wordpress, are you sure you specified the correct URL of your website?
My suggestion based on the limited information you provided and the minor amount of custom content of your website is to simply delete your database and files, create a new database, and re-installation Wordpress following exactly the correct instructions. Your VPS host may have an outlined process for you.
Alternatively, if this is a new issue, do you think you caused it? If so, what did you do? If not, you should probably contact your VPS host to see if you or they need to make an update in your DNS settings.
Found the answer by myself! Yeah!
I just added "ServerAlias www.domainname.ca" to my apache2 conf file (000-default.conf) which you can probably find at /etc/apache2/sites-available directory in your VPS.
Not sure why this worked or what exactly caused the problem but I am sure that it happened because of Yoast SEO plugin.
I have a wordpress site on the Ubuntu computer that I am using as a webserver. I have the wordpress system installed in /var/www/html. I have created pages which display nicely from any computer, tablet or handheld within my lan environment.
I am going crazy trying to access my website from the internet. Can anybody please help?
I have a noip address and a BTHub which allows me to set up dynamic dns to inform my noip account automatically when the ip changes and this works fine.
I have set up port forwarding for http and https to the computer hosting my wordpress site
I have tried assigning DMZ to my wordpress hosting computer
I have made sure I own the wordpress folders and files within them
my LAMP installed without a hitch and over the LAN access is no problem with one exception - I can only use the default permalinks or wordpress can not find my pages - no idea why? I had to cut wordpress into var/www/html as it initially went into www and could not be found
I have spent DAYS with this! It is a part of a bigger project where I want to run some projects across the internet. I dispair that if I cant get a simple wordpress site to work that my projects are doomed! lol.
When I try to access my site from another location across the internet, I get the first page, but without the media picture that should be on it. When I try to change pages I get the not found message. I also get the initial page without a style sheet in some instances. I have no clue about how to fix this. I took up Linux about three months ago, having been a windows and OSx man for years. I am in love, but have a steep learning curve!
It looks like a location issue or a WAN address issue or something I cant figure out!
I would appreciate any help that anyone out there can give me.
Eric
Thank you for your feedback. I have just this moment sorted it out. I read up the permalinks wiki thoroughly and I found out how to change the URLs from within the wp- files in the theme I was using. After a few refreshes it now works. I will post up a how-to for any others who may be experiencing the same frustration.
I recently pointed my 1&1 registered domain, masonsmn.com, away from justhost where I had a wordpress site built toward my new site constructed using squarespace.
I would like to view a few pages of the old site as they were previously (i.e. I messed up. In hindsight a few screenshots then would have been a good idea).
Does anyone know how I can access those wordpress pages at this point?
Thanks,
You can add a hosts entry to your computer to force it to go to the old IP address. See google for instructions for your operating system. Don't forget to remove it later! :-)
The old site is on justhost. Do you still use them for hosting? If so, just download your old wordpress files via ftp. If you already cancelled your hosting, but it wasn't long ago, they may have your files backed up still. If this is the case I would give them a call and see what they can do.
The WP back end of a site I'm working on (It's a multisite) takes about 25 seconds to load.
Everything was working fine until yesterday and the front end still works perfectly well. All other sites on the same server run just as well, so it MUST be a WP back end issue.
I don't remember exactly what change it was that made it so slow. I remember updating WP recently (to version 3.4.2), adding some plugins on one of the sites and changing the max upload file size.
I tried to disable all the plugins, changing the themes back to default, changing the max file size back, and adding define('WP_MEMORY_LIMIT', '1024M'); (and other values) to WP-config but none of it helped.
Also tried to 'Update network', but I got an error - couldn't connect to host.
Any ideas?
I got in touch with our network admin and we resolved the issue.
I will copy his answer here. Hope it helps someone.
Does Wordpress use 'self-referential URLs' ? What I mean by this is...
is wordpress trying to access it's own templates/css using fully
qualified domain names in the URL (e.g. http://example.co.uk/someurl )
Because we use Network Address Translation (NAT) on our firewalls to
hide the real IP address of the server, it has the side effect that if
the server tries to access it's own URLs, it will try to send the
traffic to the external interface on our firewall, which is where the
DNS resolves to.
The fix for this is very simple - we just add the site url into the
/etc/hosts file so that the server knows to use it's own IP address
instead of the address on the firewall.
So he added our address to the hosts file and now it works perfectly.
Awesome.
I've seen this before where the admin pages are trying to poll external Wordpress sites for details of Wordpress upgrades, plugin updates and Wordpress news. If there's no proper access (because of firewall restrictions, bad DNS, etc) then the page has to wait for the HTTP requests (I think WP uses cURL) to timeout.
If you're still unable to identify the cause I'd recommend a catch-all solution of installing xdebug and profiling the page with webgrind, xcachegrind, etc
Had the same problem for a week and now the problem of very slow WP-admin was solved!
Before, I cannot access my sites if I use incognito or I am not logged in as WP user, but all times in the wp-admin, it takes me 40 seconds- minute or even never.
Solution that worked:
I accessed the files in the file manager using the CPanel, and I saw so many unused and unnecessary folders and themes and that's the reason that causes the very slow access to admin.
It was because during the days of being a newbie, I stuffed a lot of files in the Public Http and that made it congested.
I logged in to another CPanel account that I bought personally before, and compared the folders of the "proper" versus the "congested" and compress, backed-up and deleted all the unnecessary.
My host: Hostgator, responded well also.
Hope this would help others.
I also had a very slow Dashboad in wordpress. Reading the James C´s answer, I realized that my site is located in a corporate intranet behind a firewall to access internet.
James C answered:
"I've seen this before where the admin pages are trying to poll external Wordpress sites for details of Wordpress upgrades, plugin updates and Wordpress news. If there's no proper access (because of firewall restrictions, bad DNS, etc) then the page has to wait for the HTTP requests (I think WP uses cURL) to timeout."
My solution was avoid all the internet conections: (1) disable all the wordpress updates using the wordpress plugin "Disable all wordpress updates". (2) activate de wordpress pluging "Disable google fonts"
After these two plugin activations, the Dashboard works to a suitable speed.
Please can someone help me to clarify what issues i might have when the hosting company changes the DNS settings to point away for the current old site (basic html) and to the new WordPress version of the web site?
Both sites are with the same hosting company (I cannot change hosts or hosting names now, my client and the hosting company are long term business partners). I think the server that the current live website is unable to host WordPress. So they set up another server for WordPress and called it something completely different.
Old website address http://www.therealwebsitename.co.uk
Current Location of new WordPress site on hosting server: http://test.blahsystems.co.uk
I think this bit is important!!
The new website is on a Windows Server and uses pretty perma links and also the .html pages plugin. There are also some redirects going to 7 pages on the old site. Everything is currently working ok.
Nest week the hosting company are going to change the DNS settings to point to the new website http://test.blahsystems.co.uk which will hopefully become the new website with the new address of http://www.therealwebsitename.co.uk
The hosting company have also said that I should not have used Permalinks at the moment because once the DNS is pointed to the new site the links will have become permanent (well I had already set up permalinks before they told me). I have not used the full address when making any links within the site.
Will the 'Find & Replace' plug-in on the database still work ok to make any required changes? I am confused as to how the DNS change actually works, will this affect what the links are called in the database or can I still change them from:
http://test.blahsystems.co.uk
to
http://www.therealwebsitename.co.uk
I presume I will need to change the Word Press address and site address in the settings panel to http://www.therealwebsitename.co.uk, once the DNS propagation has finished.
Very long winded I know but any help would be much appreciated.
Thanks
Ok - I will do the best I can to answer these 8-)
Please can someone help me to clarify what issues i might have when
the hosting company changes the DNS settings to point away for the
current old site (basic html) and to the new WordPress version of the
web site?
When you change your DNS - it's like moving into a new house.
The whole building can change - so it sounds like you're leaving a Windows environment for a Linux environment. Which is cool.
What happened on the old site - should not really impact the new site OTHER than the fact that search engines will still try to remember the old sites structure. It will take time for the search engine to realize that things have changed and that pages are new or missing.
301 Redirection can help with this.
Both sites are with the same hosting company (I cannot change hosts or
hosting names now, my client and the hosting company are long term
business partners). I think the server that the current live website
is unable to host WordPress. So they set up another server for
WordPress and called it something completely different.
Old website address http://www.therealwebsitename.co.uk Current
Location of new WordPress site on hosting server:
http://test.blahsystems.co.uk
I think this bit is important!! The new website is on a Windows Server
and uses pretty perma links and also the .html pages plugin. There are
also some redirects going to 7 pages on the old site. Everything is
currently working ok.
WordPress can use permalinks. If you have moved pages around - like mysite.com/about-us and it's not called mysite.com/about - you will need to create a 301 Redirect to let search engines know.
Nest week the hosting company are going to change the DNS settings to
point to the new website http://test.blahsystems.co.uk which will
hopefully become the new website with the new address of
http://www.therealwebsitename.co.uk
The hosting company have also said that I should not have used
Permalinks at the moment because once the DNS is pointed to the new
site the links will have become permanent (well I had already set up
permalinks before they told me). I have not used the full address when
making any links within the site.
I don't think using permalinks will cause a problem. They aren't "permanent". Nothing is - it's all in a transient state.
Will the 'Find & Replace' plug-in on the database still work ok to
make any required changes? I am confused as to how the DNS change
actually works, will this affect what the links are called in the
database or can I still change them from:
http://test.blahsystems.co.uk to http://www.therealwebsitename.co.uk
Sounds like this plugin is outside of the WordPress install? If so - it should still work.
If it's a plugin your hosting provider is giving you, then there should be no problems.
I presume I will need to change the Word Press address and site
address in the settings panel to http://www.therealwebsitename.co.uk,
once the DNS propagation has finished.
Yes, make sure to update your General Settings prior to the site going live so you don't have any down time.