You are currently trying to build a server.
However, even if you do as you investigated, you can never access your server website.
Although it is not built on the Internet just by building in practice, is it necessary to acquire a unique domain?
Now put something other than 80 (80X temporarily) into the SELinux http port
I changed the serverName to httpX_list listen 80X.
And in the host windows
http: // [serverName]: 80X/
http: // [serverName]: 80X/index.html
It is not connected even if it is accessed. Even number 80 was useless. (Index.html has been placed in the documentsRoot directory)
I run apache with systemctl start httpd.
So the part I want to hear finally is
・ Do you need to acquire your own domain
・ What to do with the URL to access (other than IP address)
Is there anything I should do other than what is written
It is a point.

  • Answer # 1

    If the network of the virtual machine is "NAT", you can find the expected site by searching "Virtual Box NAT".

  • Answer # 2


    Is it necessary to acquire an original domain?

    No need.


    What to do with the URL to access (except IP address)

    Usually connect with a local IP, but if it seems to be using a domain, set the host-side hosts domain IP to allow name resolution so that the host machine can resolve the name. The


    Is there anything else I need to do

    There is nothing else but it seems to be doing something extra.

  • Answer # 3

    Is the host adapter included in the virtual machine's network adapter?
    If only NAT is used, host OS ← → guest OS guest OS ← → guest OS cannot communicate.



    Network Address Translation (NAT)


    If all you want is to browse the Web, download files and view e-mail inside the guest, then this default mode should be sufficient for you, and you can safely skip the rest of this section.


    Host-only networking


    This can be used to create a network containing the host and a set of virtual machines, without the need for the host's physical network interface.

    If only the host-only adapter is used, the guest OS cannot connect to the Internet, so two virtual NICs, NAT and host-only adapter, are set, and if necessary, a static IP is set for the host-only adapter. I think that is good. (If you use it as a server, you can save time to start and check the IP address)

    Access the serverName as a static IP that is shaken toward the host-only adapter.

  • Answer # 4

    Have you checked the apache log?

    There is a log of the time the page was accessed
    ⇒ What is not displayed is a problem with apache settings

    There is no log of the time the page was accessed
    ⇒ The request for http has not been reached. There is a problem with the network settings

    You can narrow down the problem