RossMitchell

Sorry, I was not clear enough.
You edit (as superuser) the apache config file “000-default.conf” and add the block there. You will need to do the same for the other websites, copy the block and edit the names and paths.

I very much doubt that with your present settings that you are really viewing your websites from the localhost server. What happens when you break the connection between the server and the internet, or between the LAN and the internet ?

With the new VirtualHost configuration, and hosts file edits, you really will be able to mirror your websites. Just comment out the lines in the hosts file to switch.

The nature of backgrounds and borders etc are under control of your theme. You may find better expertise and experience in the support forum of your theme.

It also seems that your website is under “wordpress.com”, this is support for “wordpress.org”, which is sufficiently different that you should seek support from wordpress.com

What do you see in the webserver error logs ?
Has there been a change in webserver settings ?

Yes, I too are looking forward to Ubuntu 18.04 LTS, I will be updating many systems.

These are the settings I need to have if I am to help you further. At each of the websites on your localhost PC
A:
– login to the WordPress dashboard
– browse to Settings > General
– tell me the text that is in the fields for “site address” and “wordpress address”

B:
– give me the contents of the “VirtualHost” blocks from the apache2 configuration.

C:
– give me the contents of your “hosts” file, probably “/etc/hosts”

It can be a challenge to give the css selectors sufficient weight to dominate the evaluation criteria and hence get their properties adopted. There are rules about this that I have never learned, instead I add selectors that are appropriate but not too specific to do the job. The browser inspector also helps here, this is what right click Copy > CSS Path gave me:
html.js.svg.background-fixed body.page-template-default.page.page-id-98.wp-custom-logo.page-one-column.colors-light div#page.site div.site-content-contain div#content.site-content div.wrap div#primary.content-area main#main.site-main article#post-98.post-98.page.type-page.status-publish.hentry header.entry-header h1.entry-title
Which is way too much, and specific to just this page, so I would try:

.site-content #primary..content-area .entry-header h1.entry-title {
 font-size: 180%;
}

The browser inspector will show you in the css area if your phrase has or has not been incorporated.

The 3 websites can’t be browsed correctly on remote browser which, in this case, is Firefox on Host after upgrade.

internal-ip/ballet
internal-ip/opera
internal-ip/string

I don’t know why?

The problem comes down to what is the “site address” and “WordPress address” in the dashboard > settings > general ??? These are crucial settings in locating where webpage resources are available from.

It s now necessary to describe the details of how your web browser fetches the parts for a web page. Initially you enter the page address in the browser address bar, or click on a bookmark or link. This address is resolved by the dns mechanism etc and finds your webserver, and it finds the page requested, the server then responds with a single html file, it contains the TEXT for the words on the page, and for other resources such as css and image files it provides a URL for each. The browser then fetches the contents of these resources by throwing each URL at the network, and the dns etc sends the request to the web server, and the server responds with the contents of the requested file. The surprising point is that EACH request does the full navigation of the path from your browser.

An example will show how this so easily goes wrong. Say the localhost server has an IP address of 10.0.0.67 and as is very commonly the case on localhost WordPress setups the site address is 127.0.0.1 (the universal localhost self address). So on the browser on the same machine, I can enter either “http://127.0.0.1/” OR “http://10.0.0.67/”, in both cases the server returns the results of processing index.php from “/var/www/html/index.php”, it will have the text from the homepage, and for say the style.css resource it will say it is at “http://127.0.0.1/wp-content/theme/twentyseventeen/style.css”, this is great while the browser is on the same machine as the server, all is well. BUT if you are on a different machine (say 10.0.0.50) the page text is fetched correctly, but when it comes to getting the css file, the request is not sent to the server! the network tries to find it locally on 10.0.0.50 The same happens for all the other resources.

So depending upon what the site address and wordpress addresses are set to, I suspect that when you were earlier serving pages from your localhost PC, that the critical resources were still being fetched from godaddy, as were subsequent pages.

So please give me the details of what you have in your site address and wordpress address fields.

Can you give us the URLs that work and those that don’t. Also the file paths of where the website files live. Also the VirtualHost config blocks from apache and the lines you have in your “hosts” file.
In addition to the “VirtualHost” blocks in the apache config, there are also directory permission blocks like:

<Directory C:/WebSiteFiles>
 Options Indexes FollowSymLinks
 AllowOverride All
 Require all granted
</Directory>

Can you find anything in that apache error logs ?

Does your website hosting technical support have any ideas, it could be another aspect of their security settings that also block the auto updates.

Suggest that you turn on debugging in your wp-config.php file prior to doing a manual plugin update, you will hopefully get more informative error messages.
In wp-config.php find the line:
define('WP_DEBUG', false);
comment it out and add:
define('WP_DEBUG', true);
Be sure to reverse this after you have finished.

• This reply was modified 8 years, 2 months ago by RossMitchell.