murkus
Members
-
Joined
-
the container environment variable for the container port number seems to be PORT.
-
I would like to change the container(!) port number for the server web UI (note that I do not want to change the host port number, I know that the docker port mapping can be used for that!). Is there an environment variable that I can use, or a config file that I need to change?
-
NOVNC_PORT seems to be the correct variable, can you confirm?
-
hmm that was premature.. RFB_PORT does not seem to work (RFB_PORT: 8283): WebSocket server settings: - Listen on :8080 - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - Backgrounding (daemon) ---Ensuring UID: 99 matches user--- ---Ensuring GID: 100 matches user--- ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Configuring Locales to: en_US.UTF-8 UTF-8--- Generating locales (this might take a while)... en_US.UTF-8... done en_US.UTF-8... done Generation complete. ---Checking configuration for noVNC--- Nothing to do, noVNC resizing set to default Nothing to do, noVNC qaulity set to default Nothing to do, noVNC compression set to default ---Taking ownership of data...--- ---Starting...--- ---Preparing Server--- ---Checking for old logfiles--- ---Checking for old lock files--- ---Starting dbus service--- ---dbus service started--- ---Starting TurboVNC server--- ---Starting noVNC server--- ---Starting Desktop---
-
Thanks it worked out.
-
Debian-Bookworm container: is there a environment variable that we can use to change the container port number for the VNC server? (I know that I can change the host port. however, I use this with the network of another container, where there is another container already using port 8080...)
-
Thanks, note that this doesn't help with the missing NICs.
-
I found how to fix this. The reason that the container does not see the host interfaces is that the container runs in network bridge mode. I don't know whether that is the default for this container as it comes from @VRx, I may have switched to from network host mode to network bridge mode myself at some point. If the container runs in network host mode it does see all interfaces (the actual interface name filtering can be changed in the LLD macros). @VRx Just in case the container does not come set to host network mode by edfault, this may be a welcome change for the next release.
-
my unraid also is using br0 for the IP address, and it does not show up in Zabbix. It seems I am facing the same challenge. Were you able to solve it in the meanwhile? How?
-
This seems to be a problem of object limits with minIO or the aws cli tool used by the Amazon cloud driver. I was able to solve this by setting reasonable limits for the cloud device resource: MaximumPartSize = 1000000000 MaximumFileSize = 1000000000 This will create volume folders in cache and S3 of size 10GB containing 13 parts with max 1GB size.
-
I had used a disk share for the XO backup remote. remote encryption does NOT work with disk shares, but it does work with user shares. Time will tell whether the "stale file handle" problem also appears with user shares, more testing is required on my end.
-
You might find that XCP-ng suits your needs better than Proxmox, but it depends on your requirements.
-
Yes, I have it working for ISO SRs and backup remotes. (Not for VDI SRs)
-
I had the same problems, I found no solution. So I use TrueNAS for SRs.
-
NFS3 clients go through portmapper to access nfsd. Up to unraid 6.12.10 nfsd and lockd were registered with portmapper, so nfs3 clients worked. Starting with 6.12.11 nfsd and lockmanager are not registered with portmapper, so nfs3 clients fail to mount shares from unraid nfsd. NFS4 clients to not go through portmapper to access nfsd, this is why nfs4 clients still work with 6.12.11. To be correct: after rebooting unraid 6.12.11 all necessary rpc daemons are registered with portmapper as long as the array has not been started. After starting the array, nfsd and lockmgr are gone from portmapper (see rpcinfo on the console). Also, with KODI using NFS 4 seems to be no universal solution. It works for video files but it doesn't work for many music files (NFS4: READ (path (null)) failed with NFS4ERR_OLD_STATEID(-5), NFS4: CLOSE (path (null)) failed with NFS4ERR_BAD_STATEID(-22)). This does NOT seem to be a result from lockmgr missing from portmapper, as when using NFS3 with Kodi and unraid 6.12.10 this just works fine. I would gues sit is an implementation problem in the Kodi NFS4 client. Bottom line: I had to downgrade from 6.12.11 to 6.12.10 to be able to use Kodi using NFS3 and unraid. It is one main use case for me. (I do not want to switch to SMB)