Jump to content

ken-ji

Members
  • Content Count

    1074
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by ken-ji

  1. Sorry. I give up. You are the first to have this error, and I have no obvious clues or ideas as to why the client is stalling. Maybe Dropbox can provide support, but the headless client seems to have the absolute minimum of support (at least for free users)
  2. I can only guess, but the dropboxd process probably crashed or something without showing anything in the logs. Well restarting the container would restart the process, but as for the runningand syncing for 24h, I have no idea what happened there...
  3. hmm. really odd. If you now open a shell in the container and su to your user, does dropbox.py status say its running? If it is, then there should be no problem (and I'm out of clues or ideas) If it isn't, I'm actually stumped as to why the dropboxd binary is stopping for you.
  4. Can you restart the Dropbox container and attach the log? Probably starting from the last dropbox: initializing line
  5. I think you've misconfigured the container somehow... can you should me the docker configuration again?
  6. The dropbox process is running as the nobody user. So when you go in, you'll need to switch to the nobody user: sh-4.3# su - nobody nobody@dropbox:~$ cd Dropbox nobody@dropbox:~/Dropbox$ dropbox.py filestatus .dropbox: unwatched .dropbox.cache: unwatched 2019-03-07 13.57.05.pdf: up to date 3D Stuff: up to date nobody@dropbox:~/Dropbox$
  7. I have no idea what could be wrong here... are you still at 3 or less devices signed in vs the Free tier of the Dropbox account (you can check on the web site under security)? or are you paying for it monthly? You might need to go in via a shell and run the dropbox.py command to inspect your files.
  8. Its been a while, but I think the docker settings page limits which network interfaces it will display. You need to enable "Preserve user defined networks" in the Docker Settings, then in the command line run something like # docker network create \ -o parent=vibr1 \ --driver macvlan \ --subnet 192.168.1.0/24 \ --ip-range 192.168.1.128/25 \ --gateway 192.168.1.1 \ labnet Adjust the IPs to your needs. Unfortunately, docker won't let you create a network without a gateway defined and imposes a few other annoying constraints on docker networks.
  9. You need to tell docker about the new bridge by going to the Settings | Docker Menu. Stopping the docker engine will then let you edit the networks and allow you to define the IP and gateways for the internal network.
  10. This is because you now have two routers/gateways on 192.168.30.0/24 network. and only 192.168.30.1 (is this the Unifi) can talk to 192.168.1.0/24 In situations like this, ideally the VPN VM should also be a gateway to the other networks, but that will probably cause you grief if your Unifi router can't run the VPN client you want, it might be possible to create another VLAN (say 31) 192.168.31.0/24, put the VM there as 192.168.31.254 and make the Unifi route all traffic from 192.168.30.0/0 thru the VPN 192.168.31.254 instead of whatever your ISP gateway is. Not running a Unifi router, so I have no idea how you do this though.
  11. Hmm. your diagnostics show that you have a netdata container that is not properly reaping the finished processes 201 15538 0.2 0.0 33416 22352 ? SNl 03:01 2:23 | | \_ /usr/bin/python /usr/libexec/netdata/plugins.d/python.d.plugin 1 201 300 0.0 0.0 0 0 ? ZNs 05:34 0:00 | | \_ [timeout] <defunct> 201 301 0.0 0.0 0 0 ? ZNs 06:28 0:00 | | \_ [timeout] <defunct> 201 302 0.0 0.0 0 0 ? ZNs 04:32 0:00 | | \_ [timeout] <defunct> ... snip ... 201 32766 0.0 0.0 0 0 ? ZNs 09:32 0:00 | | \_ [timeout] <defunct> 201 32767 0.0 0.0 0 0 ? ZNs 08:54 0:00 | | \_ [timeout] <defunct> So your server is running out of process ids to run new processes. You should check with the support thread for the netdata container you are running
  12. ken-ji

    What UPS

    AFAIK under 19" deep racks are mainly meant for networking/telecom switches and patch panels, and use either lighter and non-rack mount UPS; or POE to power.
  13. You tried to start the dropbox service as the root user. This made your dropbox sync to /root/Dropbox (inside the container) which is in docker.img because of some limitations, the container drops you into a root shell, not the user running the dropbox service. so you actually need to run su - nobody before interacting with the dropbox service inside the container. From within my container: sh-4.3# su - nobody -c 'dropbox.py status' Up to date I have to say you are the first to encounter a bunch of issues... Most of the people using this container have been able to configure without much difficulty, barring the crap Dropbox created with the filesystem limits and the recent dropbox builds now needing graphical libraries to run headless. If your docker logs says just that then there should be nothing wrong. Mine is like this. The killed line at the end indicates dropbox service restarting it self. You can run the status command above or the ls command 'dropbox.py ls /dropbox/Dropbox' to check the sync status. dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-bUcbWA dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/dropbox' dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/apex._apex.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-crogcX dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/dropbox' dropbox: setting python path '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465:/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/apex._apex.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-y31su9 dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/dropbox' dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/apex._apex.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-iKKsTy dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/dropbox' dropbox: setting python path '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150:/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/apex._apex.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' dropbox: locating interpreter dropbox: logging to /tmp/dropbox-antifreeze-TyX1Rm dropbox: initializing dropbox: initializing python 3.7.5 dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/dropbox' dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/python-packages.zip' dropbox: python initialized dropbox: running dropbox dropbox: setting args dropbox: applying overrides dropbox: running main script dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/apex._apex.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/tornado.speedups.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so' dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so' /usr/local/bin/dockerinit.sh: line 19: 19 Killed su -l ${DROPBOX_USER} -c "/dropbox/.dropbox-dist/dropboxd"
  14. Right, I guess I wasn't clear, but you need to to use a specific disk for the Dropbox share since you don't have a cache drive. Since you already have a Dropbox user share, it probably is on disk1, and you can confirm from the Web UI Shares Tab, Click on Compute for the Dropbox share and it will return where the share is currently saved to. Edit the docker to change /mnt/user/Dropbox to whichever disk is used for it ie /mnt/disk1/Dropbox for disk1 Some caveats with this configuration. If you create/edit files over Samba to the Dropbox share, there is the possibility that files might end up on the other disks and would then be not seen by the Dropbox container. You should edit the Dropbox share to limit it to only one disk.
  15. its the exec line. exec stops the current process and replaces it whatever you exec'd - so in this script. once it exec's the zsh, then the entire script stops and a zsh process runs and exits. Reading the script indicates exec'ing zsh is point less. why are you trying to reload zsh? its not even running as the #! of the script is bash.
  16. Stop the container. Very important. A running container will probably delete all your Dropbox files. Open the terminal to Unraid >_ on the upper right of your screen. run root@tower:~# rm -r /mnt/user/appdata/dropbox /mnt/user/Dropbox this will nuke Dropbox share (which will be regenerated when the container is started up) and the appdata for the Dropbox container When you restart the container, it will run from scratch, so you will need to link it again. Warning, this might cause you to go over the 3 devices limit for Free accounts, so make sure to go your Dropbox account and unlink the previous container. It will be a linux client with a hexadecimal name like abc12458efd
  17. Would just like to add my 2bits here: There are two ways you can configure dockers and IPv6. The first and foremost way is to configure Docker network with either a default ipv6 pool - same as the one assigned to the interface or statically assign one to it. This makes the whole assignment of IPv6 by Docker work like IPv4 - sequentially in order of the container starting up. Docker will keep track of the IPv6 addresses assigned to the containers. The 2nd way which I am using, is to simply disable IPv6 at the Unraid network configuration level. Then all my containers have the "--sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.eth0.use_tempaddr=2" extra parameters set. This make Docker not bother at all with IPv6 assignments, does not do anything to the container routing tables, and does not add extra dns settings to the ipv4 settings. What happens then is that the network stack in the container will attempt to configure IPv6 via SLAAC and attempt to discover the router by router-advertisements over the wire, assigning a privacy address is desired. This mechanism works really well on my network running Mikrotik router (which does not have DHCPv6, so every thing is SLAAC using the dynamic /56 provided by my ISP. The whole thing works very well, particularly since the dynamic /56 has no gurantee of being the same across reboots, and with the absence of DHCPv6, my Unraid docker networks would not be configurable anyway. Also, I wanted to restrict which network interface and IP Unraid was able to use to host the SMB/SSH/HTTP services.
  18. Because Dropbox did a very dick move sometime back and artificially (as far as it seems on the user end) limited the client to run on only the Ext4 FS. This has been slightly amended to include "Mainstream" ones like as I listed previously. So the client refuses to run on a shfs mount ie the /mnt/user location. /mnt/user contains all the disks in your array plus the optional cache drive. So, in your case /mnt/user/appdata/dropbox would probably fall under /mnt/disk1/appdata/dropbox unless some of the disk allocation rules come into effect. I'm thinking your app data folder is partially corrupt, since the error mentions some missing files from the application zip archive, so you can try removing both the appdata and Dropbox mount points in Unraid (so that you really start afresh).
  19. So, since there seems to be a problem with shfs, please change the location of the mounts to /mnt/cache/appdata/dropbox and /mnt/cache/Dropbox (and keep that Dropbox share cache only) - This is the new default as pointed out by the other Community maintainers. I assume the cinereus user name is a user you created in the Unraid Users settings. I also assume this user has access to the Dropbox share? Otherwise I don't see what the problem is. This is my setup, with the Config folder stored in a Unassigned Cache SSD
  20. Could you post a screenshot of your dropbox container mount mappings?
  21. Not picking a fight, but it is discussed on post #2, page #1 of this support thread.
  22. Because at the right most column of the Docker tab/page says LOG, and in basic its a picture of a log file I don't know what you meant by this, since accdg to Docker: https://help.dropbox.com/installs-integrations/desktop/system-requirements#desktop A Dropbox folder on a hard drive or partition formatted with one the following file system types: ext4 zfs (on 64-bit systems only) eCryptFS (back by ext4) xfs (on 64-bit systems only) btrfs What is not supported is the shfs (User Share filesystem) exclusive to Unraid, so you can no longer run the Dropbox container on a user share (/mnt/user/*), but needs to be on either the cache drive (/mnt/cache) , a physical array drive (/mnt/diskX) or an Unassigned Drive (/mnt/disks). As I've discussed above, placing the Dropbox sync folder on a user share was never a good idea due to mover moving files between the cache and the array, effectively making the files disappear from Dropbox's point of view, causing files to be deleted and reuploaded/downloaded
  23. Some thoughts to accomplish what you want. First I'd rather use an actual domain, and get DNS records for it. This way I am able to use Let's Encrypt using the DNS challenge to sign a domain wildcard cert *.domain. Admittedly in my case I'm using a VPS to run acme.sh as my LE client. This cert I'll feed the nignx reverse proxy for all my LAN services. Then my router (which is a mikrotik) contains the DNS mapping for all the apps to the nginx proxy. Alternatively, like the builtin unraid TLS mode, you could disable domain rebinding protection, and publish the local ips on the global DNS. Maybe pi-hole could work here too. If you don't want to spend on a domain, your next alternative is to create your own wildcard cert for your personal domain name. But then you'd need to install the self-signed CA into all your clients, which might not work as easily as you might think, particularly adding certs to dockers can be a real challenge.
  24. Please attach the whole diagnostics ZIP file You can get it under the Tools Menu at the top
  25. quick questions. how is your linux VM connected to your pfsense router VM? over the vibr0 bridge? if so, you are running two DHCP servers (KVM has its own on vibr0, while pfsense has another if you enabled it.) and it will be a toss up of which gets picked. what you should do is define a guest only bridge. I haven't used this in a while, so not sure if I'm missing some steps. Create a file /tmp/gbr.xml <network> <name>guest-bridge</name> <bridge name="vmbr0" /> </network> Run the commands virsh net-create /tmp/gbr.xml virsh net-autostart guest-bridge You should then be able to link your VMs to this guest bridge and use the pfsense as the router (dhcp and gateway). (However, the gui for VMs will not show the new bridge unless a physical network port is added.) See here too: