Websocket Error with UFW Rules

[LianSheng197]

Hi, I have a machine and since I don't want its IP directly exposed to the public, I set some conditions with ufw.

The function is generally normal, but the console keeps popping up an error message about WebSocket Error, like these:

2023/08/01 05:25:43 Web server listening at :8080                                                                                                    
2023/08/01 05:25:58 ArozOS Neighbour Scanning Completed,  1  neighbours found!                                                                        
2023/08/01 05:26:00 [Scheduler] ArozOS System Scheduler Started                                                                                       
2023/08/01 05:26:03 upgrade:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header               
2023/08/01 05:26:03 http: superfluous response.WriteHeader call from imuslab.com/arozos/mod/filesystem/metadata.(*RenderHandler).HandleLoadCache (meta
data.go:240)                                                                                                                                          
2023/08/01 05:26:10 upgrade:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header               
2023/08/01 05:26:10 http: superfluous response.WriteHeader call from imuslab.com/arozos/mod/filesystem/metadata.(*RenderHandler).HandleLoadCache (meta
data.go:240)                                                                                                                                          
2023/08/01 05:26:16 [IoT] Initial IoT device scanning completed                                                                                       
2023/08/01 05:26:52 upgrade:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header               
2023/08/01 05:26:52 http: superfluous response.WriteHeader call from imuslab.com/arozos/mod/filesystem/metadata.(*RenderHandler).HandleLoadCache (meta
data.go:240)                                                                                                                                          
2023/08/01 05:28:26 http: superfluous response.WriteHeader call from main.system_fs_WebSocketScanTrashBin (file_system.go:947)                        
2023/08/01 05:28:26 Websocket Upgrade Error:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' heade
r                                                                                                                                                     
2023/08/01 05:28:46 upgrade:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header               
2023/08/01 05:28:46 http: superfluous response.WriteHeader call from imuslab.com/arozos/mod/filesystem/metadata.(*RenderHandler).HandleLoadCache (meta
data.go:240)

This will cause some features to not work properly, such as Speedtest.

2023/08/01 05:38:39 *AGI WebSocket*  WebSocket upgrade failed:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 
'Connection' header                                                        
WebSocket Upgrade Failed                                                   
WebSocket Setup Failed.

And this is my ufw rule setting script:

#!/bin/bash

# Stop
ufw --force disable

# Reset ALL Rules
ufw --force reset

# Default
ufw default deny incoming
ufw default allow outgoing

# General
ufw allow 22/tcp comment 'Allow SSH'
ufw allow from 127.0.0.1 comment 'Allow from localhost'

# CloudFlare Reverse Proxy
ufw allow from 103.21.244.0/22 comment 'CloudFlare Possible IPs'
ufw allow from 103.22.200.0/22 comment 'CloudFlare Possible IPs'
ufw allow from 103.31.4.0/22 comment 'CloudFlare Possible IPs'
ufw allow from 104.16.0.0/13 comment 'CloudFlare Possible IPs'
ufw allow from 104.24.0.0/14 comment 'CloudFlare Possible IPs'
ufw allow from 108.162.192.0/18 comment 'CloudFlare Possible IPs'
ufw allow from 131.0.72.0/22 comment 'CloudFlare Possible IPs'
ufw allow from 141.101.64.0/18 comment 'CloudFlare Possible IPs'
ufw allow from 162.158.0.0/15 comment 'CloudFlare Possible IPs'
ufw allow from 172.64.0.0/13 comment 'CloudFlare Possible IPs'
ufw allow from 173.245.48.0/20 comment 'CloudFlare Possible IPs'
ufw allow from 188.114.96.0/20 comment 'CloudFlare Possible IPs'
ufw allow from 190.93.240.0/20 comment 'CloudFlare Possible IPs'
ufw allow from 197.234.240.0/22 comment 'CloudFlare Possible IPs'
ufw allow from 198.41.128.0/17 comment 'CloudFlare Possible IPs'

# Start
ufw --force enable

Am I missing any rules?

[LianSheng197]

Well here is my problem.

I accidentally touched nginx.conf during the process of setting ufw rules, which caused the previous settings for websocket headers to be lost.
So the problem is nginx configure rather than ufw. I misunderstood it.