Leaderboard

Unless if @Mobius has another solution for your specific router (brand), you can also add 1.1.1.1 as the DNS server in your router, this way, you don't need to add a DNS server per device.

this is exactly what i would do for a tp link router.

Since the rollout of HexOS local the "hexos (ix-app)" showed up in the TrueNAS app list. Makes sense for running HexOS local software on TrueNAS. The app is showing to have available updates in the TrueNAS app list. Of course, this app doesn't show up the HexOS Deck interface. So I cannot update it from there. My question is: - What should I do with this app? - Should I update it manually? - Will HexOS update it automatically? When? - Why does it show an update but didn't update automatically yet? I understand, that the intention for HexOS is to never have to touch TrueNAS. For my use cases I do very often and just wondered about this.

There is a chance this is happening because of how your router handles dns rebinding. Disabling dns rebind protection should allow you to access local. If you can share with me the brand of router you have I can share instructions for how to disable dns rebind protection

Sorry and Thank you for the update for some reason I couldn't find anywhere else it was stated being addressed. Looks like I know what I am doing this weekend.

I just tried that and it seemed to work thank you! The truenas button is also not greyed out now so thats great. I am logged into a different computer on my network using a different browser but I will try it on my other computer as well

Another typical problem is if you use Pi-Hole together with Unbound or possibly Adguardhome.

Hi Folks, the up-dated docs for HexOS system requirements are here: https://docs.hexos.com/getting-started/overview.html

I want you to know I successfully migrated only to experience database corruption about a week later losing my instance. I have a backup of the raw data fortunately. I understand engineering resources but this is why we really need to be able to have arbitrary backup and restore per app. Please bring that engineering focus to implement backup and restore up sooner than later. I can't wait to see that functioning built into buddy back up as well! More thoughts it looks like there's others in the community that are looking forward to this future as well see TrueNas Scale needs a first party application backup and restore system

Anyone still looking for their email to be changed please email support@hexos.com with their existing email account and the one you want to change to. Thank you.

Originally the reason for making all the apps a SambaShare was because sometimes users needed access to edit or change something in the apps directory. This is not something TrueNAS does but we were trying to make it easier for normal people who wouldn't know how to get into those folders and edit a file if they needed. It's still something we discuss if it's still something we need to do or maybe we should just hide it since we're on our way to building a whole apps system.

This was solved. The machine that HexOS is installed on had a different outbound IP than the machine that I was using Deck on. Using the TrueNAS interface, running this shell command got me the correct IP to enter manually on the Deck page. curl ipinfo.io/ip

In case you haven't found the other thread: It's not completely on the HexOS interface, but the rollback workaround is close.

Try the following. Most likely this will fix your issue. If this does, TrueNAS has a fix that is in it's next update. Login to TrueNAS interface. Left side select "system". Then after screen refreshes select "shell" from the list. Paste in the following command. *Can't use normal short cuts* Will need to use Shift + Insert Key for pasting. sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it. You might need to run this after reboots. Let us know if this works. Thank you,

Hi everyone, this moring i though of a very good feature to add: gluetun + qbittorrent through a docker compose, just need to implement an interface where you select your vpn provider and fill the needed infos, you can add port forarding through the yaml install script ( for example for proton vpn) and i think i could be a very good option for the users who doesn't know how to setup a thing like this. i add below an example of a yaml docker compose file (mine): services: gluetun: cap_add: - NET_ADMIN container_name: gluetun devices: - /dev/net/tun:/dev/net/tun environment: - VPN_SERVICE_PROVIDER=custom - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=XXXXXXXXXXXXXXXXXXXXX - WIREGUARD_PUBLIC_KEY=XXXXXXXXXXXXXXXXXXXX - WIREGUARD_ADDRESSES=10.2.0.2/32 - VPN_ENDPOINT_IP=185.246.211.193 - VPN_ENDPOINT_PORT=51820 - VPN_DNS_ADDRESS=10.2.0.1 - VPN_PORT_FORWARDING=on - VPN_PORT_FORWARDING_PROVIDER=protonvpn - WIREGUARD_MTU=1420 - FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24 image: qmcgaw/gluetun:latest ports: - '8080:8080' restart: unless-stopped volumes: - /mnt/HDDs/Applications/gluetun:/gluetun - /mnt/HDDs/Applications/gluetun:/tmp/gluetun gluetun-qbittorrent-port-manager: environment: HTTP_S: http PORT_FORWARDED: /tmp/gluetun/forwarded_port QBITTORRENT_PASS: password QBITTORRENT_PORT: 8080 QBITTORRENT_SERVER: localhost QBITTORRENT_USER: admin image: snoringdragon/gluetun-qbittorrent-port-manager:latest network_mode: service:gluetun restart: unless-stopped volumes: - /mnt/HDDs/Applications/gluetun:/tmp/gluetun qbittorrent: container_name: qbittorrent depends_on: - gluetun environment: - PUID=568 - PGID=568 - TZ=Europe/Paris - WEBUI_PORTS=8080/tcp image: ghcr.io/hotio/qbittorrent:latest network_mode: service:gluetun restart: unless-stopped volumes: - /mnt/HDDs/Applications/qbittorrent_vpn/config:/config - /mnt/HDDs/Applications/qbittorrent_vpn/data:/data - /mnt/HDDs/Downloads/qbittorrent:/downloads version: '3.9'

Hello, It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following. Login to TrueNAS interface. Left side select "system". Then after screen refreshes select "shell" from the list. Paste in the following command. Can't use normal short cuts Will need to use Shift + Insert Key for pasting. sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it.