This definitely looks more like a network/proxy connectivity issue than a test execution issue.
A few things you should check:
1. Proxy/VPN blocking Katalon services
Try:
-
Disconnecting from the VPN temporarily (if permitted by your organization) and rerun the test.
-
Running from a different network (for example, a mobile hotspot).
If the issue disappears outside the corporate network, then the VPN/proxy/firewall is likely blocking a required Katalon service.
2. Verify that Katalon endpoints are allowed
Ask your network/security team to verify access to Katalon services such as:
-
*.katalon.com
If these services are blocked, you may experience:
-
“Unable to create logger” timeout errors
-
Blank Log Viewer
-
Missing user/workspace information
-
Analytics/TestOps/TrueTest related connectivity issues
All communication is typically over HTTPS (port 443).
3. Check Proxy configuration in Katalon Studio
Go to:
Windows-> Katalon studio Preferences → Proxy
Verify that:
-
Proxy host and port are correct
-
Authentication settings are configured if required
-
PAC file settings (if used) are valid
4. Clear workspace cache
Workspace metadata corruption can occasionally cause logging and UI issues.
Try closing Katalon Studio, backing up the project, and clearing the workspace cache before reopening the project.
5. Check the detailed stack trace
The most useful information will be in:
.metadata/.log
Look at the lines immediately following:
Unable to create logger. Root cause (Operation timed out)
The full stack trace often reveals the exact hostname, endpoint, and port that Katalon was attempting to reach when the timeout occurred.
6. Verify HTTPS/WebSocket filtering
Some enterprise proxies allow standard HTTPS traffic but block WebSocket connections. Since the Log Viewer relies on live communication, ask your network team whether HTTPS/WebSocket traffic to Katalon services is being filtered or inspected.