PHP session affected user or permission response

When this happens

Use this when admin accounts work but a real user or integration account fails. Do not stop at the screen message; validate the actor, role, group, owner, token, and permission boundary first.

Symptom checklist

• session appears repeatedly in the PHP UI or logs.
• php-fpm logs, memory_limit, composer, session, headers differs between successful and failed requests.
• The issue appears only after separating PHP code error from FPM/web server configuration.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• session specifically changes the investigation surface for PHP: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• session.save_path is missing or not writable by PHP-FPM.
• Cookie domain, Secure, or SameSite attributes prevent the browser from returning the session.
• Output is sent before session_start can set headers.
• Long requests hold the session file lock and block another request.
• Multiple PHP-FPM pools use different session settings.
• For the affected user or permission case, the first useful clue is the actor, role, group, owner, token, and permission boundary.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare php-fpm logs, memory_limit, composer, session, headers for success and failure in the same window.
3. Test the hypothesis: PHP session failure caused by unwritable session path, cookie domain mismatch, early output, SameSite policy, or concurrent session lock.
4. Classify this as affected user or permission: the actor, role, group, owner, token, and permission boundary.
5. Capture current values before changing configuration.

First evidence

Treat session as a affected user or permission case. First collect evidence for the actor, role, group, owner, token, and permission boundary.

Output examples

Normal output

The same action succeeds for the same role and target object.

Failing output

Only one user, group, owner, token, or object path fails.

Output-to-action branches

• Admin accounts work but a real user or integration account fails.
  Verify as the affected actor and grant the smallest missing permission or restore ownership.
• The working and failing outputs differ.
  Act on the differing layer first: For session, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not solve it by giving broad administrator access.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "session" ./logs

php -v

composer diagnose

tail -n 200 /var/log/php*-fpm.log

grep -R "session" .

php -i | grep -i "session.save_path\|session.cookie"

ls -ld /var/lib/php/sessions /tmp

grep -R "session_start\|headers already" ./logs .

grep -R "permission\|denied\|unauthorized\|forbidden\|owner" ./logs | tail -n 80

Fix order

1. Record the full session message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for PHP session failure caused by unwritable session path, cookie domain mismatch, early output, SameSite policy, or concurrent session lock.
3. Compare the failing case with a successful case before editing settings.
4. If this is the affected user or permission branch, Verify as the affected actor and grant the smallest missing permission or restore ownership.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For session, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Check PHP-FPM user permissions on session.save_path.
• Align session cookie attributes with the public HTTPS domain.
• Call session_start before output and redirects.
• Close the session early for long-running read-only requests.
• Compare phpinfo values between CLI and FPM.
• For the affected user or permission branch, Verify as the affected actor and grant the smallest missing permission or restore ownership.

Evidence links

• PHP session configuration official
• PHP session runtime configuration official
• PHP session_start official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for PHP session.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change PHP code error from FPM/web server configuration results.
• Do not trust only the PHP UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for php-fpm logs, memory_limit, composer, session, headers.
• Add Composer autoload, memory limit, session path, header order to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• PHP Fatal error first triage response
• PHP Parse error first triage response
• PHP memory exhausted first triage response
• PHP Composer first triage response
• PHP permission denied first triage response
• PHP session first triage response
• PHP upload limit first triage response
• PHP PDO first triage response