[Bug] Blank Screen with HTML Dynamic Encryption enabled from Firefox/Opera
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22.6k
- Forks
- 1.5k
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 11
Description
What happened?
Blank Screen appears with BOT PROTECTION - HTML Dynamic Encryption enabled
Description: everything has worked well for about half a year.
After six months our application started to show white screen when users work with Firefox.
The process: Client Verification (Anti-Bot challenge) - Dynamic Decryption - White Screen
Topology: Nginx Reverse Proxy --> WAF SafeLine --> Application Endpoint
WAF Version: 8.9.1, updated to 9.2.7
Client Software:
- OS: Windows 10/11
- Browser: Firefox 144.0.2
Client IP addresses/locations/countries: Different (any of them affected)
If client software is MacOS/Firefox, everything works well. If clients use Google Chrome, everything works well
Steps to resolve (failed):
- Restart containers
- Restart the server
- Upgrade from version 8.9.1 to 9.1.7
Temporary Solution: Disable HTML Dynamic Encryption
How we reproduce?
There is no way to reproduce it 100%
There are only some conditions this problem appears under:
Clients OS: Windows 10/11
Client Browser: Firefox
Expected behavior
Application is loaded
Error log
192.168.200.250 is Nginx Reverse Proxy, 192.168.200.2 is the Application. These logs reflect the time we tried to load the App from Firefox so they are related to the issue 100%
cat logs/nginx/safeline/errorlog_5
2025/11/05 15:25:47 [error] 49#0: *1 connect() to unix:/resources/detector/snserver.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.200.250, server: myapp.domain.com, request: "POST /Default.aspx/GetServicveMode HTTP/1.1", host: "myapp.domain.com", referrer: "https://myapp.domain.com/"
2025/11/05 15:25:47 [error] 49#0: *1 connect() to unix:/resources/detector/snserver.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.200.250, server: myapp.domain.com, request: "POST /Default.aspx/GetServicveMode HTTP/1.1", upstream: "https://192.168.200.2:443/Default.aspx/GetServicveMode", host: "myapp.domain.com", referrer: "https://myapp.domain.com/"
2025/11/05 17:20:42 [error] 48#0: *1 connect() to unix:/resources/detector/snserver.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.200.250, server: myapp.domain.com, request: "POST /Default.aspx/GetServicveMode HTTP/1.1", host: "myapp.domain.com", referrer: "https://myapp.domain.com/"
2025/11/05 17:20:42 [error] 48#0: *1 connect() to unix:/resources/detector/snserver.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.200.250, server: myapp.domain.com, request: "POST /Default.aspx/GetServicveMode HTTP/1.1", upstream: "https://192.168.200.2:443/Default.aspx/GetServicveMode", host: "myapp.domain.com", referrer: "https://myapp.domain.com/"
2025/11/05 17:21:03 [error] 48#0: *13 connect() to unix:/resources/detector/snserver.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.200.250, server: myapp.domain.com, request: "POST /Default.aspx/GetServicveMode HTTP/1.1", host: "myapp.domain.com", referrer: "https://myapp.domain.com/"
2025/11/05 17:21:03 [error] 48#0: *13 connect() to unix:/resources/detector/snserver.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.200.250, server: myapp.domain.com, request: "POST /Default.aspx/GetServicveMode HTTP/1.1", upstream: "https://192.168.200.2:443/Default.aspx/GetServicveMode", host: "myapp.domain.com", referrer: "https://myapp.domain.com/"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with logs/nginx/safeline/errorlog_5 and reproduce the reported flow on Windows 10/11 Firefox with HTML Dynamic Encryption enabled. Compare it with Chrome and macOS Firefox, then determine why the application reaches a blank screen and verify that it loads while the protection remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nginx
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100