Encountering a strange issue on the remote server side where everything works fine locally with a self-signed cert over https. However, when moving the code to the server, it works locally but not remotely.
A node app is created and hosted on the server using port 3000 for https. Socket IO lib is attached to the same https server. Nodeiis is not used; instead, rewrite rules are employed to pass it through Windows IIS.
The websocket module is already installed in IIS. Initially, websockets were used successfully with the current configuration before switching to Socket.IO which better suits the requirements.
Now onto the code
Html Page
<script src="/socket.io/socket.io.js"></script>
<script src="/js/Client.js"></script>
Client.js
$(document).ready(function() {
var address = window.location.protocol + '//' + window.location.host;
var details = {
resource: (window.location.pathname.split('/').slice(0, -1).join('/') + '/socket.io').substring(1)
};
const socket = io.connect(address, details);
socket.on('connect', function () {
console.log('Client Connected');
socket.emit('ping', 'hi server ping sent!');
});
socket.on('error', function (reason){
console.log('Connection failed', reason); //This is where the error is triggered
});
});
App.js
....
const https = require('https');
var socketlib = require('./socketLib');
const fs = require('fs');
const app = express();
var cookieParser = require('cookie-parser');
app.use(sessionParser);
var expiryDate = new Date( Date.now() + 60 * 60 * 1000 );
const sessionParser = session({
secret: 'secret', resave: true, cookieName: 'sessionName',
name: 'sessionId', saveUninitialized: true,
ephemeral: true,
cookie: { secure: true, expires: expiryDate, SameSite : 'None',
maxAge: 24000 * 60 * 60, // One hour
}
});
//// HTTPS Server ////
const options = {
key: fs.readFileSync(config.certKey),
cert: fs.readFileSync(config.certCert)
};
var httpsServer = https.createServer(options, app, function (req, res) {
console.log('request starting...https');
});
httpsServer.listen(3000, function(req, res) {
console.log('Server is running at', config.nodeApiUrl + ':', port)
});
socketlib(httpsServer, sessionParser);
app.all('/*', function (req, res, next) {
res.header('Access-Control-Allow-Origin', 'https://localhost:3000')
res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE')
res.header("Access-Control-Allow-Credentials", "true");
res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept, X-Access-Token,X-Key");
return next();
})
socketLib.js
module.exports = async function(httpsServer, sessionParser) {
var io = require("socket.io")(httpsServer);
io.use(function(socket, next) {
sessionParser(socket.request, socket.request.res, next);
});
io.use((socket, next) => {
if (socket.request.headers.cookie)
return next();
next(new Error('Authentication error'));
});
io.sockets.on('connection', function(socket) {
console.log(`New connection from: ${socket.handshake.address}`)
});
}
iis webconfig
<rule name="Websocket" stopProcessing="true" enabled="true">
<match url="socket.io" ignoreCase="true" />
<action type="Rewrite" url="https://localhost:3000/{R:0}/socket.io.js" appendQueryString="false" redirectType="Found" />
<conditions>
<add input="{HTTP_HOST}" pattern="domainxxx.com" />
</conditions>
</rule>
Browser Console Error:
socketio.js:57 Error Error: server error
at r.onPacket (socket.io.js:7)
at o.<anonymous> (socket.io.js:7)
at o.r.emit (socket.io.js:6)
at o.r.onPacket (socket.io.js:7)
at n (socket.io.js:7)
at Object.e.decodePayload (socket.io.js:7)
at o.r.onData (socket.io.js:7)
at i.<anonymous> (socket.io.js:7)
at i.r.emit (socket.io.js:6)
at i.onData (socket.io.js:7)
This points to:
switch(a('socket receive: type "%s", data "%s"',t.type,t.data),this.emit("packet",t),this.emit("heartbeat"),t.type){case"open":this.onHandshake(JSON.parse(t.data));break;case"pong":this.setPing(),this.emit("pong");break;case"error":var e=new Error("server error");e.code=t.data,this.onError(e);break;
You will see the line:
var e=new Error("server error")
When trying to access via domainxxx.com, it seems that something prevents the socket from connecting remotely while working fine locally. It appears that the issue arises after the rewrite rule, although it seems correct.
Your assistance in resolving this would be greatly appreciated as extensive research has been inconclusive!
Thank you very much!