Publicly attached in-client bug reporting output log files are 403 Forbidden
closed
WubTheCaptain
Description
Since last night, trying to open attached log files from in-client bug reports with log file links (
https://api.vrchat.cloud/1/file/{fileId}/1/file
) on VRChat Feedback fails with 403 Forbidden, even for log files you have submitted yourself.This affects multiple people, while logged in to VRChat Home.
{"error":{"message":"Forbidden","status_code":403}}
An example where log files from in-client bug reporting were used to triage a bug (cannot be accessed anymore): https://feedback.vrchat.com/bug-reports/p/worlds-wont-work-or-avatars
Reproduction Steps
Visit https://feedback.vrchat.com/bug-reports and find an in-client bug report with an included log file. You're looking at one right now!
Click on an attached "Log file:" link.
To create an in-client bug report:
- Launch VRChat 2026.3.1 Build 1885or later.
- Open the Quick Menu, press Report a Bug.
- Submit an in-client bug report with "Include log file" enabled.
Details
- Category: Other
- Frequency: Always
---
platform: PC (platform: Windows, store: Steam, headset: None)
rawPlatform: WindowsPlayer
clientVersion: 2026.3.1-1886-a268441585-Release
unityVersion: 6000.0.60f1-DWR
In-Client Report
---
Log file:
output_log_2026-08-18_05-56-23.txtLog In
StormRel
updated the status to
closed
This was intentional. Closing out as not a bug.
WubTheCaptain
StormRel
Build 1896
client still says "Logs will be publicly visible." in the in-client bug reporting UI, so I assume this will be changed soon. I can create a new bug report if needed.WubTheCaptain
I made a new bug report just now: In-client bug reporting still says incorrectly "Logs will be publicly visible."
WubTheCaptain
In-client bug report log files from
https://vrc-logs-us-east-2.s3.us-east-2.amazonaws.com/bug-reports/{userId}/{filename}
are unaffected.