Web Terminal don't work

[Febtw]

New issue for "Web Terminal don't work" problem.
The Web Terminal shows nothing but black, and can't type in anything.
I checked the browser and got two errors. (I have tried Edge v103, Chrome v103, safari 15; I got the errors on Chrome)
DevTools failed to load source map: Could not load content for https://34.125.133.35:3000/cache_js/bootstrap.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://34.125.133.35:3000/js/xterm.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

[jamielsharief]

I have not tested on edge, but used with chrome and no problems. you not seem to have no error messages (the map error messages are not the problem) but you are able to communicate with the lxd server , therefore I suspect it is something with either your browser extension or firewall or if not the nodejs server is not running or working properly in the container.

[Febtw]

I use a new installed Chrome, there's no extensions on it.And I have disabled the ufw.
But I don't know how to check if the nodejs server is working properly in the container.

[jamielsharief]

Check if there are any errors in the errors log, make sure you restart the nuber-app container at least once ,

If you can check if the server.js is running (its being managed in the background and restarts every minute, so but if you can kill it and start manually, then when you next open a terminal window, you can see the errors which are happening.

$ cd /var/www/websocket && node server.js

You can also test like so

curl -i -N -k -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: localhost" -H "Origin: http://127.0.0.1:9090" http://127.0.0.1:9090

The issue here is the websocket server, or just communicating with that, but if you have any strange setup on your lxd server (ie its not a fresh install), then that could be causing problems, example, if you have configured a firewall etc.

[Febtw]

I use google cloud VM, and I have rebuilt the whole enviroment.

for $ cd /var/www/websocket && node server.js
I get

root@nuber-app:~# cd /var/www/websocket && node server.js
Server started port:8080
{ Error: listen EADDRINUSE: address already in use :::8080
    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
    at listenInCluster (net.js:1328:12)
    at Server.listen (net.js:1415:7)
    at new WebSocketServer (/var/www/websocket/node_modules/ws/lib/websocket-server.js:90:20)
    at Object.<anonymous> (/var/www/websocket/server.js:23:16)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 8080 }

for curl -i -N -k -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: localhost" -H "Origin: http://127.0.0.1:9090" http://127.0.0.1:9090
I get

root@nuber-app:~# curl -i -N -k -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: localhost" -H "Origin: http://127.0.0.1:9090" http://127.0.0.1:9090
curl: (7) Failed to connect to 127.0.0.1 port 9090: Connection refused

[Febtw]

It seems $ cd /var/www/websocket && node server.js is OK now.

root@nuber-app:/var/www/websocket# cd /var/www/websocket && node server.js
Server started port:8080
> client connected
wss://34.125.133.35:8443/1.0/operations/feb4c736-fe49-48d1-9491-ae3ad3660bb5/websocket?secret=d8c3e54ee1c933842d63dd8c24cb142b6ef94f60ac1228cf8309fcb0447e971f

> connected to LXD
1001 closed connection
> client connected
wss://34.125.133.35:8443/1.0/operations/b34bf45d-e1a6-49c2-8f45-faf777515b3b/websocket?secret=be854631cdc520ffec277acc8dcd246b302552fcd4bf22351bd88c57153479a0

> connected to LXD
1006 closed connection

[jamielsharief]

So its all working now?

[jamielsharief]

Are there any errors in the logs /var/www/logs folder?

[Febtw]

Web Terminal still not work
There'are apache-access.log apache-error.log application.log lxd.log in /var/www/logs folder
This is /var/www/logs/apache-error.log

[Wed Jun 29 13:55:51.106318 2022] [ssl:warn] [pid 26054] AH01909: nuber-app.lxd:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jun 29 13:55:51.152975 2022] [ssl:warn] [pid 26055] AH01909: nuber-app.lxd:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jun 29 14:02:32.912189 2022] [ssl:warn] [pid 218] AH01909: nuber-app.lxd:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jun 29 14:02:33.121793 2022] [ssl:warn] [pid 254] AH01909: nuber-app.lxd:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jun 29 14:02:39.550224 2022] [proxy:error] [pid 267] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:8080 (*) failed
[Wed Jun 29 14:02:39.550319 2022] [proxy_wstunnel:error] [pid 267] [client 127.0.0.1:57710] AH02452: failed to make connection to backend: 127.0.0.1
[Wed Jun 29 14:36:40.881260 2022] [ssl:warn] [pid 231] AH01909: nuber-app.lxd:443:0 server certificate does NOT include an ID which matches the server name
[Wed Jun 29 14:36:41.248860 2022] [ssl:warn] [pid 262] AH01909: nuber-app.lxd:443:0 server certificate does NOT include an ID which matches the server name

[jamielsharief]

So basically before it could not connect to the server because it was not running, now its working? Reinstall fixed the problem?

[Febtw]

I restart nuber-app again, and the server.js works

[jamielsharief]

I did say the other day to restart the container first, incase something crashed.

[Febtw]

I re-create the VM, and I restarted nuber once after I installed it

[Febtw]

server.js get the error again

root@nuber-app:~# cd /var/www/websocket && node server.js
Server started port:8080
{ Error: listen EADDRINUSE: address already in use :::8080
    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
    at listenInCluster (net.js:1328:12)
    at Server.listen (net.js:1415:7)
    at new WebSocketServer (/var/www/websocket/node_modules/ws/lib/websocket-server.js:90:20)
    at Object.<anonymous> (/var/www/websocket/server.js:23:16)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 8080 }

[Febtw]

But the website still works, I can handle everything except the terminal

[jamielsharief]

Manually running the server is giving that error because its already running (handled by cron jobs). You can disable the cron job temporarily, then run manually, to attempt to see what is going on. Is it possible your VM provider has some firewall blocking traffic to either websockets or port 8080?