Logs and Config Files

A quick reference for where ForgeKit keeps its generated config and logs. See Where are logs stored? for a troubleshooting-oriented walkthrough.

Per web-server instance

Inside /ForgeKit/instances/web/{instance_folder}/:

• conf/sites-enabled/vhosts.conf: vhost entries for every site routed to this instance
• conf/httpd.conf (Apache) or conf/nginx.conf (Nginx): the instance's main server config
• logs/access.log, logs/error.log: the web server's own main-context logs, covering startup errors, port conflicts, and any request that didn't match a site's vhost. Open via the Logs button on the web server's row.
• logs/php_error.log: PHP's own error log for this instance. Written by PHP, not the web server, and shared by every site on this instance (there's no per-site php_error.log). Open via the second Logs button, under the PHP section of the same row.

Each instance has its own copy of these files. They are not shared between instances, even if two instances run the same Apache or Nginx version. See Instances.

Per PHP binary

• php.ini: tied to the PHP binary/version, not to an individual instance. If two instances use the same PHP binary, they share that php.ini.
• /ForgeKit/logs/php-fallback/php-{version}.log: a fallback/default log for that PHP version, used when PHP runs outside any instance context (terminal, phpMyAdmin). Normal site requests are handled by the per-site or instance php_error.log instead, so this file can stay empty during regular usage. That's expected.

Per site

• /ForgeKit/logs/sites/{domain}/access.log, /ForgeKit/logs/sites/{domain}/error.log: written by that site's own <VirtualHost>/server{} block, same as a real Apache/Nginx vhost would. The first place to check when one specific site has PHP or web errors but others don't. Open via the Logs button on the site itself.

Per database instance

• my.ini (MySQL/MariaDB): inside the database instance's folder in /ForgeKit/instances/databases/.

Continue to → Where are logs stored? or Site missing from vhosts.conf?