When v2ray over websocket is enabled, some sites are downloaded as a .gz file instead of opening. I tested with chrome and edge. This is my config.json
#
listen 443 ssl default_server;
listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name domain.com;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
return 444;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
location /websocket/ {
proxy_redirect off;
proxy_pass http://127.0.0.1:8388;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
}
ssl_certificate /etc/nginx/certs/domain.com/fullchain; # managed by C ertbot
ssl_certificate_key /etc/nginx/certs/domain.com/key; # managed by Cer tbot
When v2ray over websocket is enabled, some sites are downloaded as a .gz file instead of opening. I tested with chrome and edge. This is my config.json
this is my sites-available/default server {
SSL configuration
} ssl_certificate /etc/nginx/certs/domain.com/fullchain; # managed by C ertbot ssl_certificate_key /etc/nginx/certs/domain.com/key; # managed by Cer tbot
}