Dear Apache,
My story is the same as before, I would like to get my WordPress
working throughout a Windows 10 home network, but
can't seem to succeed.
I don't want to introduce the complications of bind or dns,
or any other similar facility in Windows.
Isn't there just a way that I can reconfigure Apache so that it
broadcasts, or is accessible by default, throughout my local network?
My Apache webserver is serving my WordPress site in https,
but if the certificate doesn't confirm, there is the option
to go ahead anyway, which I am happy with for the time being.
I do have my webserver running so that the XAMPP default screen
does run and appear in a web browser through the network. For
reasons that I can't explain, and more importantly don't know how
to repair, I can't get my WordPress to come up.
What can I do with Apache itself so that it just self naturally can be
accessed through the local network?
________________________________
From: Jens Kallup <kallup.j...@web.de>
Sent: Thursday, 7 April 2022 5:18 AM
To: users@httpd.apache.org <users@httpd.apache.org>
Subject: Re: [users@httpd] Getting XAMPP Apache on Windows 10 to work through
local network!
Hello,
As an alternative to the last postings, you can use the
C:\windows\system32\drivers\etc\hosts"
files to simulate DN-Server. The file is write protected, so you have to change
the permissions !
So you can add, and bind local names like "example.com" to a ip that you use in
your local
network configuration.
This implicit that you have disable the DHCP option on the router, and spend
all clients his
own private ip number, manually per hand.
This can be the subnet: 192.168.0.0 or 10.0.0.0.
The format of the hosts file is shown in line below:
127.0.0.1 localhost # ipv4 loopback of all machine owner
::1 localhost # ipv6 loopback ...
#
192.168.178.100 example.com # private network ip address for main
page
192.168.178.101 sub.example.com # ... sub domain ... (ipv4)
192.168.178.102 sub.sub.example.com # ... sub sub domain ... (ipv4)
#
fd00::100 example.com # same as above, but with local ipv6 hex
numbers
fd00::101 sub.example.com # ...
fd00::102 sub.sub.example.com # ...
#
# EOF - End Of File
If you can, you should be use the ipv6 format style.
Because the old ipv4 format is still supported, but it has deprecated, and
reached
EOL - end of life.
One reason is, that you can address many many more host's.
If you have change the hosts file, you have to "name" three (3) VirtualHosts
with the
ServerName, and optional the ServerAlias.
Into the VirtualHost block, you have to describe the directories, in which the
documents
rest, with custom (also your needs) options.
This can be the permissions of the user(s) who can enter the directory, and
show the
display content, ...
Under Windows 10/11, I advise you, that you can add ipv4, and ipv6 numbers for
one network
card device (adapter) in the system panel.
It is hidden on the new Windows design, but still present.
You can reach it, when you click on the Windows symbol at left lower area of
the screen.
Then a application panel should be open with the possibility to type in
informations in the
address bar at top of this window/app/panel.
Type in: system panel, and on the right side, you should be see the application
that you
can click on with the mouse, now.
The old system panel should then be open, and you can click the network setting
icon to
arive the network settings. Then on the left side of this window, you can click
on the text
network adapters.
Next, new window will open which display the network adapters that are
installed on your
Windows computer installation.
Click on the lan device, and change the network settings with the local network
ip address,
its subnet, and the gateway. If you would like to use the internet, you should
give the
DNS address of your router (and gateway).
The local network will be (e.g. example): 192.168.178.100, and the subnet mask
will be:
255.255.255.0
You can add network addresse's like describe above, to probe different ip, and
domain names
on the same computer you sitting on - I think this would be the local
development computer,
when you click the advance button - near the ok, and cancel button.
PLEASE NOTE: You should not use XAMPP as productive server !
I hope this informations can be helpful for you by the first playground
steps, and give you an overview what you need, what you can do, and maybe what
is not
possible.
As a pro: you can use XAMPP in local area home networks.
The cons: you have more maintain, because you use the Windows version of a
Apache2.4 server.
And as such, the directory format differs in some huge ways that should be have
attention
on your side.
This means Windows C:\, D:\ ... Linux /root /home/user
And the permission design are very different.
PLEASE NOTE: You should not use XAMPP DocumentRoot's under C:\ !
The best way is to connect to a network drive or an external usb
hard drive
device or a flash stick.
That should be enough to know for the first time
best regards
Jens Kallup
Am 06.04.2022 um 16:10 schrieb Frank Gingras:
If httpd works on localhost, all you need to do is set up DNS to access it from
another computer. Alternatively, you can use http(s)://IP_HERE/ to access httpd
from another computer.
Make sure that you use Listen 80 and/or Listen 443 to allow all clients to
connect.
On Wed, 6 Apr 2022 at 05:27, A Z
<powerus...@live.com.au<mailto:powerus...@live.com.au>> wrote:
Dear Apache, one and all,
-I am running Windows 10 64 bit Home Edition. My web browser is Firefox 64 bit
98.0.2. I have downloaded and am using XAMPP 7.4.28 from
https://www.apachefriends.org/download.html.
I am using WordPress 5.9.2. I used the free version of Elementor 3.6.2 as my
page builder. In Permalinks I have selected ‘Post name’. I am using the theme
‘Twenty Twenty-one’ to rely my present website on. I am operating in an
entirely Windows 10 local, home network.
I am aware that it is possible to run Apache as a webserver through a local
network only, certainly a Windows one, via the general mood on the internet.
I have changed SSL and Apache default port numbers. I have added ingoing and
outgoing firewall rules on both the client and server PCS, to allow Apache SSL
to get through, and WordPress website SSL as well, apparently, though not in
practice. 🙁
I have developed a local WordPress website on my local client PC at home. It
does work on the server machine it was developed on, and I want to test it
through the local network next.
I have gotten everything working up to the point where the client computer in
the Network can load the XAMPP dashboard that the server PC is serving. This
seems to imply that I have all my network nodes, firewall rules and protocol
transmission right. But I can’t get my WordPress website to get transmitted
through to the client PC web browser; I simply get a no connection error
message from the client PC.
I believe that my problem may be related to the configuring of Apache. I start
and stop Apache through the XAMPP control panel. I can also immediately access
and change the files
httpd.conf, httpd-ssl.conf and htttpd-xampp.conf, although I have only adjusted
the first two.
Is there anything better that I can do to get my WordPress Elementor website to
be viewable by Firefox on another PC inside the local network?
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscr...@httpd.apache.org<mailto:users-unsubscr...@httpd.apache.org>
For additional commands, e-mail:
users-h...@httpd.apache.org<mailto:users-h...@httpd.apache.org>
