-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web Terminal don't work #29
Comments
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. |
I use a new installed Chrome, there's no extensions on it.And I have disabled the ufw. |
Check if there are any errors in the errors log, make sure you restart the 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
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. |
I use google cloud VM, and I have rebuilt the whole enviroment. for
for
|
It seems
|
So its all working now? |
Are there any errors in the logs /var/www/logs folder? |
Web Terminal still not work
|
So basically before it could not connect to the server because it was not running, now its working? Reinstall fixed the problem? |
I restart nuber-app again, and the server.js works |
I did say the other day to restart the container first, incase something crashed. |
I re-create the VM, and I restarted nuber once after I installed it |
server.js get the error again
|
But the website still works, I can handle everything except the terminal |
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? |
I reinstalled nuber in a new VM yesterday, and got into another error. I studied issue #26, but I was unable to run bin/console db:setup, and couldn't find config/install.json.
|
The reason you are getting the 500 is because you are not following the installation instructions. |
for example, install.json is not there because you did not install it. You are trying to do it some other way. I setup a VM last month and full tested this and it was working out of the box. Please follow the installation instructions. |
It looks like you were correct a change to composer (dependency manager) blocked plugins which prevented installation from working properly. |
$ lxc operation list
|
find and kill node process to debug, disabled task to restart
|
TODO: this is weird error message, last time websocket was fixed by reinstalling. Since installation failed and i fixed this manually, perhaps a reinstall would work. Come back to this. |
Thanks, the installation is OK now. Its back to the web terminal issue |
You were correct it was a change by the dependency manager which messed up the install process. I need to figure out, why nodejs is having the cert problem all of the sudden. You can try installing an older version of node to see if that fixes it, but I cant look it right now , I already done what I can for today |
I think If I log in https://127.0.0.1:3000 under the desktop environment, I don't need to consider the problem "Is it possible your VM provider has some firewall blocking traffic to either websockets or port 8080". If possible, I can give you the account and password of the VM so that you can test it at any time. You can login with ssh or vnc |
No need, I did a new installation and got the same issue , the errors are above. I am thinking it's a problem with a newer version of nodejs. Since that is what causing the problem |
OK, I understand, I’ll try the old version of nodejs |
It is possible the EPROTO error is caused by one of the dependency versions which needed to be updated. This is still being investigated. |
I have been investigating this all morning, trying to find out what is going on, something has changed somewhere. I have found that LXD have made some changes to the websocket, but i am not sure this is the cause since its a different error. |
I want to apologise , i was testing with an older verison of LXD, LXD 5 now uses TLS 1.3 by default, this is also not supported in older versions of nodejs. I am hoping to repackage now. To fix I had to change the Apache server settings to accept TLS v1.3 and change the NodeJS installation to use v14. You want to try reinstalling? |
hi, long time no see.
I want to install this linux panel. It takes a few minutes, so cannot be completed. I tried the commands above on the local terminal, and they runned well. |
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
The text was updated successfully, but these errors were encountered: