@chinni 还好 tls 现在还能用。。。

@joysense
curl -s -o mtproxy.sh https://raw.githubusercontent.com/ellermister/mtproxy/master/mtproxy.sh && chmod +x mtproxy.sh && bash mtproxy.sh

@janeyee110 端口确实被墙了，试下 tls 看看

两种使用方式：

1.直接点击链接使用:

https://t.me/proxy?server=185.68.21.156&port=18443&secret=eec9f8b073ba0dff766dc268b1d590312f617a7572652e6d6963726f736f66742e636f6d

2.或者复制下面这段到 tg:

tg://proxy?server=185.68.21.156&port=18443&secret=eec9f8b073ba0dff766dc268b1d590312f617a7572652e6d6963726f736f66742e636f6d

@tabc2tgacd 没遇过，共享的都是用小号玩玩吧

@0576coder 在前端加了代码，打印不出来的

for (var key in fromFriendHashKey) {
console.log("Key: " + key + ", Value: " + fromFriendHashKey[key]);
}

// 遍历并打印出$toFriendHashKey 的所有值
for (var key in toFriendHashKey) {
console.log("Key: " + key + ", Value: " + toFriendHashKey[key]);
}

然后在服务器连接 redis-cli -h 127.0.0.1 -p 6379
keys *
也没有数据。但是前端是可以登陆看到消息记录的

@zhhbstudio 原来可以这样玩的，nginx 可以直接解析访问 js 文件？ 没有报错了，感谢

@via 改成兼容，代码改动量大？

@BeijingBaby 屏蔽感觉有点不好

@Belmode 是只要有重定向,nginx 都会有这个问题？

set $subdomain_root /www/test.net/$subdomain;

if (!-d $subdomain_root) {
return 404;
}

搞定了，先判断目录是否存在就行了。。。

@joqsc722 AI 解答的？

root /www/test.net/$subdomain;

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

原来的配置这样的

@adoal

原来是
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
改成
fastcgi_param SERVER_NAME $host;
页面无法正常跳转呢

@zhhbstudio
https://gitee.com/qice/qchat
https://gitee.com/qice/QchatServer

就这个，别人的源码，谢谢大佬

@zhhbstudio

不只这一个项目呢，还需要 nginx 代理其他的。。。

@zhhbstudio

"scripts": {
"dev": "webpack-dev-server --inline --progress --config build/webpack.dev.conf.js",
"start": "npm run dev",
"build": "node build/build.js"
},



webpack.dev.conf.js


'use strict'
const utils = require('./utils')
const webpack = require('webpack')
const cOnfig= require('../config')
const merge = require('webpack-merge')
const path = require('path')
const baseWebpackCOnfig= require('./webpack.base.conf')
const CopyWebpackPlugin = require('copy-webpack-plugin')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const FriendlyErrorsPlugin = require('friendly-errors-webpack-plugin')
const portfinder = require('portfinder')

const HOST = process.env.HOST
const PORT = process.env.PORT && Number(process.env.PORT)

const devWebpackCOnfig= merge(baseWebpackConfig, {
module: {
rules: utils.styleLoaders({ sourceMap: config.dev.cssSourceMap, usePostCSS: true })
},
// cheap-module-eval-source-map is faster for development
devtool: config.dev.devtool,

// these devServer options should be customized in /config/index.js
devServer: {
clientLogLevel: 'warning',
historyApiFallback: {
rewrites: [
{ from: /.*/, to: path.posix.join(config.dev.assetsPublicPath, 'index.html') },
],
},
hot: true,
contentBase: false, // since we use CopyWebpackPlugin.
compress: true,
host: HOST || config.dev.host,
port: PORT || config.dev.port,
disableHostCheck: true,
open: config.dev.autoOpenBrowser,
overlay: config.dev.errorOverlay
? { warnings: false, errors: true }
: false,
publicPath: config.dev.assetsPublicPath,
proxy: config.dev.proxyTable,
quiet: true, // necessary for FriendlyErrorsPlugin
watchOptions: {
poll: config.dev.poll,
}
},
plugins: [
new webpack.DefinePlugin({
'process.env': require('../config/dev.env')
}),
new webpack.HotModuleReplacementPlugin(),
new webpack.NamedModulesPlugin(), // HMR shows correct file names in console on update.
new webpack.NoEmitOnErrorsPlugin(),
// https://github.com/ampedandwired/html-webpack-plugin
new HtmlWebpackPlugin({
filename: 'index.html',
template: 'index.html',
inject: true
}),
// copy custom static assets
new CopyWebpackPlugin([
{
from: path.resolve(__dirname, '../static'),
to: config.dev.assetsSubDirectory,
ignore: ['.*']
}
])
]
})

module.exports = new Promise((resolve, reject) => {
portfinder.basePort = process.env.PORT || config.dev.port
portfinder.getPort((err, port) => {
if (err) {
reject(err)
} else {
// publish the new Port, necessary for e2e tests
process.env.PORT = port
// add port to devServer config
devWebpackConfig.devServer.port = port

// Add FriendlyErrorsPlugin
devWebpackConfig.plugins.push(new FriendlyErrorsPlugin({
compilationSuccessInfo: {
messages: [`Your application is running here: http://${devWebpackConfig.devServer.host}:${port}`],
},
onErrors: config.dev.notifyOnErrors
? utils.createNotifierCallback()
: undefined
}))

resolve(devWebpackConfig)
}
})
})




ort: PORT || config.dev.port,

也是 config 传过来的吧
new SocketJS 时传入的参数？
不太懂

@zhhbstudio 要怎么改呢？

看了日志，是 sockjs-client 这个模块 sockjs.js 文件

try {
self.xhr.send(payload);
} catch (e) {
self.emit('finish', 0, '');
self._cleanup(false);
}

这段代码报的错，注释之后，就没有了。只是注释之后，没有新消息提醒的。。。

@YellowDog7

server {
listen 443;
server_name chat.test.net;
ssl_certificate /etc/letsencrypt/live/test.net/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/test.net/privkey.pem;
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4;
ssl_prefer_server_ciphers on;
set $oldclient 0;
root /www/test/chat;
index index.php index.html;
include /etc/nginx/ext/*.conf;
location / {
proxy_pass http://127.0.0.1:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}

@HHsunday 原来就上有的，还是一样域名后有 8080 端口

@br_wang 不太懂，用的 npm 启动项目