How to Fix Incorrect Joomla Log and Temp Paths

Record the current paths before changing anything

1. Sign in to Joomla Administrator.
2. Go to System → Global Configuration.
3. On the Server tab, record Path to Temp Folder.
4. On the Logging tab, record Path to Log Folder.

Keep the old values until the repair is verified. Both settings should be absolute filesystem paths. Do not enter an https:// URL in either field.

Determine the correct filesystem paths

Use your hosting control panel, file manager, SSH access, or provider documentation to identify the site's current absolute path. Confirm that the intended temp and log directories exist and that the PHP/web-server account can write to them.

• The temp directory should be dedicated to temporary application work.
• The log directory should be suitable for Joomla log files and should not be a shared system-wide directory merely for convenience.
• Use normal secure ownership and permissions; avoid broad write permissions as a shortcut.

Correct the temp and log settings

1. Enter the verified directory in Path to Temp Folder on the Server tab.
2. Enter the verified directory in Path to Log Folder on the Logging tab.
3. Select Save.
4. Reload Global Configuration and confirm both values persisted.

These settings are stored in the site's root configuration.php. If the Administrator cannot save configuration changes, investigate that file's ownership and permissions rather than repeatedly submitting the form.

Verify both paths independently

Open System → System Information → Folder Permissions and review Joomla's writable-directory checks. Then test an operation that uses temporary storage, such as a safe extension-package operation, and separately confirm that Joomla can create or update a log when a configured logging event occurs.

If one path works and the other does not, troubleshoot them separately. A valid temp path does not prove the log path is correct, and vice versa.

Recover when a bad path prevents normal access

If a path error contributes to an Administrator failure, back up configuration.php and use a controlled server-access method to restore the last known-good values. Change only the affected properties. If the correct directory is still unwritable, investigate PHP user ownership, hosting restrictions, filesystem permissions, or a read-only mount instead of weakening security permissions.

After a migration, check for other stale absolute paths

Log and temp paths are common migration casualties because they are absolute server paths. If both were wrong, review extension settings that may also store absolute filesystem paths, but do not perform a blind database-wide replacement. Back up the site and correct only confirmed stale values.