Welcome Guest. Please Login or Register  


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : noVNC encountered an error



Threaded Mode | Print  

 noVNC encountered an error, noVNC encountered an error (2 Replies, Read 7669 times)
medv_mobile
Group: Member
Post Group: Newbie
Posts: 15
Status:

There is some problem with error logging in the service. I get an error when trying to open the virtual machine viewer window and the message "noVNC encountered an error". This could be sorted out, but the event LOG is needed, and it is not there: no messages are written to the file /var/virtualizor/log/novnc as expected and as would be logical. How can I enable detailed error logging? It is impossible to configure without error logging. Axiom.
IP: --   

noVNC encountered an error
impalascubic
Group: Member
Post Group: Newbie
Posts: 2
Status:
If your `/var/virtualizor/log/novnc` log file is empty or not populated, it may be because the log is disabled or misconfigured. Fix it with the following steps:
- Check Virtualizor's noVNC Service Configuration
- Set Appropriate Permissions
- Manually Redirect noVNC Output
- Enable debug mode in Virtualizor
- Restart noVNC or Virtualizor
IP: --   

noVNC encountered an error
shieam
Group: Member
Post Group: Newbie
Posts: 1
Status:
Quote From : medv_mobile March 16, 2025, 2:48 pm

There is some problem with error logging in the service. I get an error when trying to open the virtual machine viewer window and the message "noVNC encountered an error". This could be sorted out, but the event LOG is needed, and it is not there: no messages are written to the file /var/virtualizor/log/novnc as expected and as would be logical. How can I enable detailed error logging? It is impossible to configure without error logging. Axiom.


To enable detailed error logging for noVNC, you can modify the configuration file to increase the log level. Check the noVNC settings in your virtual machine configuration and ensure that logging is set to a more verbose level, such as "debug." Additionally, verify the permissions of the log directory to ensure that the service can write to /var/virtualizor/log/novnc. Restart the service after making these changes, and you should start seeing error messages in the log file that can help diagnose the issue.
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is May 5, 2025, 8:19 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 10  |  Page Created In:0.049