Posts by annunaki

Bottom line for my issue:
I created a salt file as a suggested workaround to create a second hosts file in the path. It never worked and I ultimately neglected to delete the file. Fast forward to today, the file broke the IPV6 reported state in the OMV network gui. I removed the added file, switched IPV6 to DHCP in the OMV gui and all is well with my settings now.

Thank you all for helping me figure out when and where I tripped over myself and caused my own failures, lol. You all rock!

This jogged my memory. A long while back I recall learning and dealing with some issues pertaining to the inability to edit /etc/hosts in OMV as it is controlled by OMV. I ran across this blog where a user claimed to have crafted a workaround. Apparently it didn't work or no longer works or something. I was a little careless on this and didn't document what I did for future me to know what the heck past me did.

OpenMediaVault : Maintain entries in /etc/hosts

Interesting. I investigated the entry in this file and noted that it is trying to append some custom hosts in a second hosts file in /etc. The /etc/hosts2 file exists but is empty. I removed the 20domains.sls file and tried once more to enable DHCP for IPV6 in the OMV dashboard. This time it succeeded! Though I wonder where this came from.

The contents of the 20domains.sls file:

{% set hosts = salt['cmd.shell']('cat /etc/hosts2') %} append_custom_hosts: file.append: - name:
"/etc/hosts"
- text: "{{ hosts }}"

Output of ls -al /srv/salt/omv/deploy/hosts/

root@microverse:/srv/salt/omv/deploy/hosts# ls -al /srv/salt/omv/deploy/hosts/
total 24K
drwxr-xr-x  2 root root 4.0K May 25 09:47 .
drwxr-xr-x 46 root root 4.0K May 18 11:29 ..
-rw-r--r--  1 root root 3.2K Apr 25 12:03 10default.sls
-rw-r--r--  1 root root  133 Apr 21 22:10 20domains.sls
-rw-r--r--  1 root root 1.1K Feb 24 05:54 default.sls
-rw-r--r--  1 root root  909 Feb 24 05:54 init.sls
-rw-r--r--  1 root root 1.1K Feb 24 05:54 default.sls
-rw-r--r--  1 root root  909 Feb 24 05:54 init.sls

I don't know at all what 20domains is. My main issue is that I was getting IPV6 related connection issues. The OMV network page showing IPV6 disabled turned out to be a bit of a red herring. It turns out that I failed to create an AAAA IPV6 entry in my host record for my domains pointing to my local server. I created the records last night for all domains and it tested perfect this morning.

However, attempting to enable IPV6 in the OMV gui still results in the error. My server is working with IPV6 now. Guess I'll ignore the error.

¯\_(ツ)_/¯

I'm running into a similar issue. I cannot enable IPv6. When I attempt to switch and apply, I get the following error message and I am forced to undo the action. IPV6 is supported by my ISP. Maybe I'm missing something super obvious.

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color hosts 2>&1' with exit code '1': debian:
Data failed to compile:
----------
Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context
[CRITICAL] Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context


OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color hosts 2>&1' with exit code '1': debian:
Data failed to compile:
----------
Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context
[CRITICAL] Rendering SLS 'base:omv.deploy.hosts.20domains' failed: mapping values are not allowed in this context in /usr/share/php/openmediavault/system/process.inc:220
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(174): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusnh...', '/tmp/bgoutputhY...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(195): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

As the subject states, after upgrading to OMV6 and applying the fixes recommended by others, I still cannot access OMV WebUI, port 80, and port 443. All my Docker ports work fine with one weird caveat -- they are sometimes inaccessible and I have to delete my Chrome history to be able to access them.

Additionally, before I upgraded, I installed Cloudpanel, but swiftly uninstalled it and routed everything back the way it should be, or so I thought. I'm not 100% certain what broke the ability for the WebUI and port 80/443. I swear I've updated and reviewed so many configs in nginx and other things via extensive research on others who have seen similar in this forum and reddit. My router is still set to forward appropriately. I've even re-installed OMV and nginx, then reviewed the configs. I don't really want to do a fresh install if there's a simple fix here.

I DO have a backup of the entire OMV file system but I don't know if I have a drive large enough to host the backup, then flash it.

Any thoughts? Is there something simple that I might be missing here?

Precisely the fix needed for my machine. I have docker configs on an external FAT drive. This saved me the headache of having to reload the dockers in Portainer after every reboot.

Thank you!