[Bug]: Apache can not listen to 10.0.2.15:80 & 192.168.56.x:80 and consequently, does not start

Open
#947 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux
Domain
networking

Research direction

Start with the Network component and the attached configuration files to understand how VirtualBox initializes the 10.0.2.x and 192.168.56.x networks. Check whether their startup timing can leave the specific guest IPs unavailable when Apache starts. Done means reproducing the issue and identifying whether VirtualBox network initialization causes it; the report currently gives a workaround, not a confirmed cause.

Written by the indexing model from the issue text.

Description

bug
Version

VirtualBox 7.2.22

Host OS Type

Windows

Host OS name + version

Windows 11 Pro 25H2

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

Alma Linux 9.7

Component

Network

What happened?

When I configure my Apache settings to listen to specific IPs, belonged to VirtualBox networks, it can not start. However, if i do not specify the IP, but only a port number, the problem does not occur. Example:

Listen 10.0.2.15:80 .............................. Apache does not start
Listen 192.168.56.39:80 .................... Apache does not start

Listen 80 ............................................... Apache starts

Image
How can we reproduce this?

MY CONFIGURATION FILES: see attached

POSSIBLE PROBLEM: the VirtualBox networks 10.0.2.x and 192.168.56.x are taking too much time to initialize and Apache initializes before them.

SOLUTION: delay the Apache initialization as follow:

  • Execute in terminal the following command:
    systemctl edit httpd

  • Add to the configuration file the following lines:
    [Service]
    ExecStartPre=/bin/sleep 1

  • Save the file and execute the command:
    systemctl daemon-reload

  • Restart the machine. Apache now will start without problems.

confs.zip

Comments about the solution:
It delays the loading of Apache to allow time for the VirtualBox networks to initialize BEFORE it.
Minimum experimental value for the sleep parameter: 0.12

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Dominant language
C
Stars
1.4k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtualBox/virtualbox

All issues in VirtualBox/virtualbox

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.