Site missing from vhosts.conf
Each web-server instance has its own vhosts.conf.
If your site works, but you can't find it in the vhosts.conf file you opened, you're probably looking at the vhost file for a different instance.
This happens when two sites use the same Apache or Nginx version but different ForgeKit instances.
Example:
Site A → Apache 2.4.65 instance #1 → vhosts.conf in web-apache-2-4-65
Site B → Apache 2.4.65 instance #2 → vhosts.conf in web-apache-2-4-65-1
Both sites use Apache 2.4.65, but their vhosts are stored in different instance folders.
Same Apache version does not mean same Apache instance.
How to find the right vhosts.conf
- Open the site in ForgeKit.
- Check which web-server instance the site is routed to.
- Open that instance's config folder.
- Then open its
vhosts.conf.
See also → How ForgeKit Works · Instances · Vhosts and Routing · Where are logs stored?