Client or integration
Codex CLI
Area
Web
Summary
When viewing logs in Google Chrome on a desktop computer, the request to /api/log fails to load properly. It times out after 30 seconds, and then automatically triggers a new request, which also times out — resulting in an endless loop of repeated timeouts. However, the same operation works perfectly fine in Google Chrome on a mobile device, where the logs appear quickly without any delay.
Reproduction
ocx start on centos 7.6
Version
2.33.0
Operating system
An unofficial Node.js 22 build that works with glibc 2.17 on CentOS 7.6
Provider and model
No response
Logs or error output
Screenshots and supporting files
No response
Redacted configuration
Checks
Client or integration
Codex CLI
Area
Web
Summary
When viewing logs in Google Chrome on a desktop computer, the request to /api/log fails to load properly. It times out after 30 seconds, and then automatically triggers a new request, which also times out — resulting in an endless loop of repeated timeouts. However, the same operation works perfectly fine in Google Chrome on a mobile device, where the logs appear quickly without any delay.
Reproduction
ocx start on centos 7.6
Version
2.33.0
Operating system
An unofficial Node.js 22 build that works with glibc 2.17 on CentOS 7.6
Provider and model
No response
Logs or error output
Screenshots and supporting files
No response
Redacted configuration
Checks