Posts by uaytac

Quote from macom

sudo mkdir -p /var/log/nginx

sudo omv-salt deploy run nginx

Now works. Thank you.

After restart, I cannot access WEB UI.

I run omv-firstaid for network interface then get below error.

any recommendation for the below issue?

Quote from chente

That configuration has been working on my server for two years. And I know that other forum users have the same configuration.

This shouldn't be that difficult. Modem port forwarding and Docker configuration files (DuckDNS, Nextcloud AIO, and Nginx Proxy Manager).

There's no guide on YouTube or forums using these three Docker configuration. There are no similar examples online. So there are a dozen people like me who can't get this to work. Those who have lost hope are suggesting using Traffic instead of Nginx proxy manager.

Could you share those three Docker configuration files with your port forwarding info?

I don't think anyone has created a successful and working system using DuckDNS, Nextcloud AIO, and Nginx Proxy Manager with Docker. Despite countless attempts over two days, I couldn't get it to work. It seems no one else on the forum has done this setup either.

Please share your NPM and docker config settings if your settings work.

Not working.

And...

root@omv:~# sudo docker logs -f nextcloud-aio-mastercontainer

Trying to fix docker.sock permissions internally...

Creating docker group internally with id 989

Initial startup of Nextcloud All-in-One complete!

You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!

E.g. https://internal.ip.of.this.server:8080

⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:

https://your-domain-that-points-to-this-server.tld:8443

{"level":"info","ts":1745431886.5385532,"msg":"using config from file","file":"/Caddyfile"}

{"level":"info","ts":1745431886.5401673,"msg":"adapted config to JSON","adapter":"caddyfile"}

[23-Apr-2025 18:11:26] NOTICE: fpm is running, pid 156

[23-Apr-2025 18:11:26] NOTICE: ready to handle connections

[Wed Apr 23 18:11:26.563936 2025] [mpm_event:notice] [pid 151:tid 151] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured -- resuming normal operations

[Wed Apr 23 18:11:26.564211 2025] [core:notice] [pid 151:tid 151] AH00094: Command line: 'httpd -D FOREGROUND'

NOTICE: PHP message: The response of the connection attempt to "https://nextcloud.xxxx.duckdns.org:443" was:

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was: TLS connect error: error:0A000458:SSL routines::tlsv1 unrecognized name

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

NOTICE: PHP message: The response of the connection attempt to "https://nextcloud.xxxx.duckdns.org:443" was:

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was: TLS connect error: error:0A000458:SSL routines::tlsv1 unrecognized name

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

Initial startup of Nextcloud All-in-One complete!

You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!

E.g. https://internal.ip.of.this.server:8080

⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:

https://your-domain-that-points-to-this-server.tld:8443

[Wed Apr 23 18:15:33.527464 2025] [mpm_event:notice] [pid 142:tid 142] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured -- resuming normal operations

[Wed Apr 23 18:15:33.527739 2025] [core:notice] [pid 142:tid 142] AH00094: Command line: 'httpd -D FOREGROUND'

[23-Apr-2025 18:15:33] NOTICE: fpm is running, pid 147

[23-Apr-2025 18:15:33] NOTICE: ready to handle connections

{"level":"info","ts":1745432133.5554967,"msg":"using config from file","file":"/Caddyfile"}

{"level":"info","ts":1745432133.556658,"msg":"adapted config to JSON","adapter":"caddyfile"}

NOTICE: PHP message: The response of the connection attempt to "https://nextcloud.xxxx.duckdns.org:443" was:

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was: TLS connect error: error:0A000458:SSL routines::tlsv1 unrecognized name

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

Deleting duplicate sessions

NOTICE: PHP message: The response of the connection attempt to "https://nextcloud.xxxx.duckdns.org:443" was:

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was: TLS connect error: error:0A000458:SSL routines::tlsv1 unrecognized name

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

</html>nter>openresty</center>1></center>d>nnection attempt to "https://nextcloud.xxxx.duckdns.org:443" was: <html>

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was:

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

Initial startup of Nextcloud All-in-One complete!

You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!

E.g. https://internal.ip.of.this.server:8080

⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:

https://your-domain-that-points-to-this-server.tld:8443

{"level":"info","ts":1745433783.2866724,"msg":"using config from file","file":"/Caddyfile"}

{"level":"info","ts":1745433783.5668075,"msg":"adapted config to JSON","adapter":"caddyfile"}

[23-Apr-2025 18:43:05] NOTICE: fpm is running, pid 155

[23-Apr-2025 18:43:05] NOTICE: ready to handle connections

[Wed Apr 23 18:43:05.684081 2025] [mpm_event:notice] [pid 150:tid 150] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured -- resuming normal operations

[Wed Apr 23 18:43:05.684813 2025] [core:notice] [pid 150:tid 150] AH00094: Command line: 'httpd -D FOREGROUND'

</html>nter>openresty</center>1></center>d>nnection attempt to "https://nextcloud.xxxx.duckdns.org:443" was: <html>

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was:

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

</html>nter>openresty</center>1></center>d>nnection attempt to "https://nextcloud.xxxx.duckdns.org:443" was: <html>

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was:

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

Initial startup of Nextcloud All-in-One complete!

You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!

E.g. https://internal.ip.of.this.server:8080

⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:

https://your-domain-that-points-to-this-server.tld:8443

{"level":"info","ts":1745436978.2726269,"msg":"using config from file","file":"/Caddyfile"}

{"level":"info","ts":1745436978.2878294,"msg":"adapted config to JSON","adapter":"caddyfile"}

[23-Apr-2025 19:36:20] NOTICE: fpm is running, pid 152

[23-Apr-2025 19:36:20] NOTICE: ready to handle connections

[Wed Apr 23 19:36:20.781227 2025] [mpm_event:notice] [pid 147:tid 147] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.3 configured -- resuming normal operations

[Wed Apr 23 19:36:20.781314 2025] [core:notice] [pid 147:tid 147] AH00094: Command line: 'httpd -D FOREGROUND'

</html>nter>openresty</center>1></center>d>nnection attempt to "https://nextcloud.xxxx.duckdns.org:443" was: <html>

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was:

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

</html>nter>openresty</center>1></center>d>nnection attempt to "https://nextcloud.xxxx.duckdns.org:443" was: <html>

NOTICE: PHP message: Expected was: 0522b8bbabfba166e793e2c47a3b2458ec8aa47ca5ba0f11

NOTICE: PHP message: The error message was:

NOTICE: PHP message: Please follow https://github.com/nextcloud/a….md#6-how-to-debug-things in order to debug things!

Hello,

I have just installed NPM and Nextcloud AIO.

I can not jump to next step of installation of Nextcloud AIO.

NPM setting:

version: '3.8'

services:

app:

image: 'jc21/nginx-proxy-manager:latest'

restart: unless-stopped

ports:

- '80:80'

- '443:443'

- '81:81'

environment:

PUID: 1000

PGID: 100

X_FRAME_OPTIONS: "sameorigin"

volumes:

- /srv/dev-disk-by-uuid-5fc4aba3-caa4-4e05-9ec0-d976236fa6eb/appdata/proxymanager:/data

- /srv/dev-disk-by-uuid-5fc4aba3-caa4-4e05-9ec0-d976236fa6eb/appdata/proxymanager/letsencrypt:/etc/letsencrypt

Nextcloud AIO:

services:

nextcloud-aio-mastercontainer:

image: nextcloud/all-in-one:latest

restart: always

container_name: nextcloud-aio-mastercontainer

volumes:

- nextcloud_aio_mastercontainer:/mnt/docker-aio-config

- /var/run/docker.sock:/var/run/docker.sock:ro

ports:

- 8080:8080

environment:

- APACHE_PORT=11000

- APACHE_IP_BINDING=127.0.0.1

- NEXTCLOUD_UPLOAD_LIMIT=5G

- NEXTCLOUD_MAX_TIME=3600

- NEXTCLOUD_DATADIR=/srv/dev-disk-by-uuid-5fc4aba3-caa4-4e05-9ec0-d976236fa6eb/appdata/nextcloud

- NEXTCLOUD_MOUNT=/srv/dev-disk-by-uuid-5fc4aba3-caa4-4e05-9ec0-d976236fa6eb/MyServerFiles

volumes:

nextcloud_aio_mastercontainer:

name: nextcloud_aio_mastercontainer

networks:

nextcloud-aio:

external: true

Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. ('sudo docker logs -f nextcloud-aio-mastercontainer')

When I submit my domain, I receive message below.

"Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. ('sudo docker logs -f nextcloud-aio-mastercontainer')"

So, any recommendation/solution?

The way I did worked was...

1- From snapshot : delete..

2- Delete command was enabled and I have used delete command..

Now it is gone..

Thank you

Quote from ryecoaaron

Because you had a snapshot.

sudo virsh undefine win10

if that doesn't work,

sudo virsh destroy win10

Both command give ..

error: failed to get domain 'win10'

Quote from ryecoaaron

What error do you get when you try to use the Delete menu? I know the Delete + Storage will fail but the other should work.

Is there a reason you didn't delete it from the menu instead of finding the files? Delete + Storage would have done what you are trying to do.

Delete button is not active. I absentmindedly deleted the files

Hello,

I removed all VM files for my KVM virtual machine by mc )midnight commander).

Now, When I open KVM I see VM in list (It is just in VM tab). I cannot remove it from the list.

How Can I remove this VM from the VM tab?

It is Raspery Pi issue again.

Follow

Thread

Fresh x64 OMV7 installation with OMV-Extras

Hello,

After installation of fresh Omv7, I could not install OMV-Extras.

Below is command output.

root@omv:~# sudo wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash

Redirecting output to ‘wget-log.1’.
OMV 7
Codename :: bookworm
Downloading omv-extras.org plugin for openmediavault 7.x ...
Updating repos before installing...
Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives …

uaytac

Dec 12th 2023

Quote from ryecoaaron

Download of what? Using what service?

It was related with when I update my OMV in OMV GUI.

Quote from ramus

Hello

I will my system update (see pic) its on screen error, what i can do this update to installed. seee screen.....

I had same problem. Follow the steps then your system will work.

Thread

Fresh x64 OMV7 installation with OMV-Extras

Hello,

After installation of fresh Omv7, I could not install OMV-Extras.

Below is command output.

root@omv:~# sudo wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash

Redirecting output to ‘wget-log.1’.
OMV 7
Codename :: bookworm
Downloading omv-extras.org plugin for openmediavault 7.x ...
Updating repos before installing...
Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives …

uaytac

Dec 12th 2023

Download speed after all of above issue is about 2 - 5k. Is this another problem with OVM7 or Ovm-Extras?

Quote from ryecoaaron

yes. Just to be clear, none of this had anything to do with omv-extras. You just have to have apt in a good place to install omv-extras (or any new package).

It works now. Thank you.

Can I install Ovm-Extras?

Quote from ryecoaaron

Figures...

Try:

sudo rm /etc/initramfs/post-update.d/z50-raspi-firmware

sudo update-initramfs -u

sudo apt-get purge raspi-firmware

root@omv:~# sudo rm /etc/initramfs/post-update.d/z50-raspi-firmware

rm: cannot remove '/etc/initramfs/post-update.d/z50-raspi-firmware': No such file or directory

root@omv:~# sudo update-initramfs -u

update-initramfs: Generating /boot/initrd.img-6.1.0-13-amd64

root@omv:~# sudo apt-get purge raspi-firmware

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

The following packages will be REMOVED:

raspi-firmware*

0 upgraded, 0 newly installed, 1 to remove and 23 not upgraded.

1 not fully installed or removed.

After this operation, 0 B of additional disk space will be used.

Do you want to continue? [Y/n] y

Setting up initramfs-tools (0.142) ...

update-initramfs: deferring update (trigger activated)

(Reading database ... 34325 files and directories currently installed.)

Purging configuration files for raspi-firmware (1.20220830+ds-1) ...

Processing triggers for initramfs-tools (0.142) ...

update-initramfs: Generating /boot/initrd.img-6.1.0-13-amd64

root@omv:~#

Quote from ryecoaaron

Just because it would take less of my time, I recommend reinstalling from iso and removing the raspi-firmware package first.

After fresh installation without any update. I run sudo apt-get purge raspi-firmware

root@omv:~# sudo apt-get purge raspi-firmware

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

The following packages will be REMOVED:

raspi-firmware*

0 upgraded, 0 newly installed, 1 to remove and 23 not upgraded.

After this operation, 22.8 MB disk space will be freed.

Do you want to continue? [Y/n] y

(Reading database ... 34353 files and directories currently installed.)

Removing raspi-firmware (1.20220830+ds-1) ...

Processing triggers for initramfs-tools (0.142) ...

update-initramfs: Generating /boot/initrd.img-6.1.0-13-amd64

raspi-firmware: missing /boot/firmware, did you forget to mount it?

run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return c ode 1

dpkg: error processing package initramfs-tools (--configure):

installed initramfs-tools package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:

initramfs-tools

E: Sub-process /usr/bin/dpkg returned an error code (1)

root@omv:~#