You have not run the omv-salt command, right. Check https://docs.openmediavault.or…l#environmental-variables for more information.
https://github.com/openmediavault/openmediavault/issues/1898
Is this the fix for this issue?
You have not run the omv-salt command, right. Check https://docs.openmediavault.or…l#environmental-variables for more information.
https://github.com/openmediavault/openmediavault/issues/1898
Is this the fix for this issue?
You have not run the omv-salt command, right. Check https://docs.openmediavault.or…l#environmental-variables for more information.
No I have run all of them after I changed the ENV variable
Because the port is configured via UI and stored in the database. Therefore it is not necessary to have an env variable.
Okay, but do you happen to know answers to the other question? You can see in the logs monit still tries to connect to 127.0.0.1 even when the env is set to another address.
Since apparently it tries to connect to 127.0.0.1, it is not possible to bind to another address without making it constantly restart because it refuses connection in some kind of check to the localhost address...
QuoteDisplay MoreNov 18 01:55:57 openmediavault monit[1549]: 'nginx' failed protocol test [HTTP] at [127.0.0.1]:443 [TCP/IP TLS] -- Connection refused
Nov 18 01:55:57 openmediavault monit[1549]: 'nginx' trying to restart
Nov 18 01:55:57 openmediavault monit[1549]: 'nginx' stop: '/bin/systemctl stop nginx'
Nov 18 01:55:57 openmediavault systemd[1]: Stopping nginx.service - A high performance web server and a reverse proxy server...
Nov 18 01:55:57 openmediavault systemd[1]: nginx.service: Deactivated successfully.
Nov 18 01:55:57 openmediavault systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server.
Nov 18 01:55:57 openmediavault monit[1549]: 'nginx' start: '/bin/systemctl start nginx'
Nov 18 01:55:57 openmediavault systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
Nov 18 01:55:57 openmediavault systemd[1]: Started nginx.service - A high performance web server and a reverse proxy server.
Nov 18 01:56:57 openmediavault monit[1549]: 'nginx' failed protocol test [HTTP] at [127.0.0.1]:443 [TCP/IP TLS] -- Connection refused
Nov 18 01:56:57 openmediavault monit[1549]: 'nginx' trying to restart
Nov 18 01:56:57 openmediavault monit[1549]: 'nginx' stop: '/bin/systemctl stop nginx'
Nov 18 01:56:57 openmediavault systemd[1]: Stopping nginx.service - A high performance web server and a reverse proxy server...
Nov 18 01:56:58 openmediavault systemd[1]: nginx.service: Deactivated successfully.
Nov 18 01:56:58 openmediavault systemd[1]: Stopped nginx.service - A high performance web server and a reverse proxy server.
Nov 18 01:56:58 openmediavault monit[1549]: 'nginx' start: '/bin/systemctl start nginx'
Nov 18 01:56:58 openmediavault systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
Nov 18 01:56:58 openmediavault systemd[1]: Started nginx.service - A high performance web server and a reverse proxy server.
Nov 18 01:57:58 openmediavault monit[1549]: 'nginx' failed protocol test [HTTP] at [127.0.0.1]:443 [TCP/IP TLS] -- Connection refused
Nov 18 01:57:58 openmediavault monit[1549]: 'nginx' trying to restart
Nov 18 01:57:58 openmediavault monit[1549]: 'nginx' stop: '/bin/systemctl stop nginx'
Either this address should be changed aswell to the interface address when changing the ENV variable to for example:
or it should be possible to set multiple listen addresses. Or am I wrong with something?
Also I wish there would also be a variable to set for the port. Why is that not possible to set via env but only via GUI? I didnt find a port variable for webui in the env variables atleast
In my case it would be actually great to be able to set interfaces on which it does NOT listen, so I can set up other things on those on port 443.
Of course I didnt mean that you have to remember. I just specified that there is a post already which should show how to set up those notifications. I didn't know that config files is bad for the compose-plugin. alright .
All in all I didnt want to attack you or anyone here, just stated some more info about it.
Read the rest of the messages here and wanted to chime in again for a second.
As already said in my post, the configs can be adjusted to whatever notification service you have and want to use. This is all already documented within apprise / mailrise and does not need to be specifically mentioned imo, apart from linking to the two, which I already did.
There is also no need to add more containers or anything ,as the apprise syntax can do that already. See
Signal notification
Telegram notification
all possible notification services are listed here:
All possible ones
So all of the additional containers (signal api, telegram...) is not necessary as far as I understand and complicates the process.
Care to share more details? Seems like a good example compose file for the compose plugin.
I also already made a post here that shows how to set up things with an easy example (no VM and other things needed) which you approved already ryecoaaron. So what is missing there?
Tutorial Thread
I already posted this as an answer on another thread and since I searched for a solution to get notifications to my gotify instance for a while now. I did not find a well documented solution. Here is my way of getting notified via gotify (but any other notification service is possible. Apprise supports multiple notification services.
1) Create a mailrise docker container on the OMV server with docker compose:
services:
mailrise:
image: yoryan/mailrise
container_name: mailrise
restart: unless-stopped
ports:
- 8025:8025
volumes:
- ./mailrise.conf:/etc/mailrise.conf:ro
the mailrise.conf has to be set. I am using a config for receiving notifications via gotify which is shown below, but this can be configured using any apprise url structure.
The URL is from apprise and can be seen in the apprise gotify notify docs :
configs:
# You can send to this config with "gotify@mailrise.xyz".
#
gotify: urls: - gotifys://URL/API
Then set the OMV notification settings accordingly:
SMTP-server: 192.168.1.2 (change this to your OMV instance local IP-adress.)
SMTP-port: 8025
Encryption: None
Sender email: any@any.com
recipient email gotify@mailrise.xyz (change according to the mailrise.conf)
This forwards mail received to my gotify instance and notifies me.
What works really good and what I am using now is following:
1) Create a mailrise docker container on the OMV server with docker compose:
services:
mailrise:
image: yoryan/mailrise
container_name: mailrise
restart: unless-stopped
ports:
- 8025:8025
volumes:
- ./mailrise.conf:/etc/mailrise.conf:ro
the mailrise.conf has to be set, e.g. for notifications to gotify like this, but can be configured using any apprise url structure. A sample mailrise.conf is here:
I did following simple config for gotify:
configs:
# You can send to this config with "gotify@mailrise.xyz".
#
gotify:
urls:
- gotifys://URL/API
Then set the OMV notification settings accordingly:
SMTP-server: 192.168.1.2 (change this to your OMV instance local IP-adress.)
SMTP-port: 8025
Encryption: None
Sender email: any@any.com
recipient email gotify@mailrise.xyz (change according to the mailrise.conf)
This forwards mail received to my gotify instance and notifies me.
Display MoreWhy not using the tools which are available and work well on OMV? I haven´t reconfigure postfix and have notifications on pushover.
1. Docker with mailcatcher
2. Configure OMV to send via mailcatcher (host = IP of OMV, post = post from mailcatcher config)
3. Add third party notification tools as described in OMV Documentation
I´m using pushover and this configuration didn´t break after upgrading to OMV7
Not everyone knows all the tools available for this kind of things. Btw your link for OMV documentation also goes to mailcatcher docker
I seriously think this should be implemented. Unfortunately I am not capable of doing these kind of things. But it would be great if Email can be fetched locally (and not be sent out to an smtp server" and then from there on all notification stuff continues. In the UI when Mail notification is enabled, then the fetched Mail from the userland apps are forwarded just like now, and if not enabled, notifications could still be used to trigger functions anyone can do..
I am not sure how I would have to add a sink in sink.d for it to work? Is any script in that folder just executed when a notification is send? Can I test it with the "send test notification" button in the WebUI ?
Ah right. Now it makes sense why my attempts have been failing. Do you have any specific recommendation on what to change in which file? I would just google the generic way of doing it on Debian but I am asking to make sure I don't mess anything up with OMV. Or do it in a way in which OMV overwrites my change at some point in the futures (system updates?). Is it fine to just create e.g. 98disable-apticron-report with this content?
let me know how you did it if you find out how....
Quote from oopenmediavaultWhat is the reasoning behind not allowing users to simply turn those off in the GUI?
So? Any update?
There were very specific and legitimate questions asked by quarks, who followed the procedure of the docs and votdev, yet it does not work as intended.
I'm not sure why all the help provided until now was mostly indirect and we are left to guess how to do it more or less, while the reasoning for removing the GUI option is not explained.
I want to receive nall mails except the mails showing, what I can upgrade...
What is the reasoning bwhind not allowing users to simply turn those off in the GUI?
In order to clone you need to shut down the server usually, so you can just use clonezilla, which is not on windows.
Not sure how to describe the problem than showing the dmesg log right now... Here it is:
whats going on there?
So, I have an intel NUC running on OMV on which I attached
- 2 HDDs with an external power connection via USB each
- 1 SSD per USB
- 1 NVME via USB
. I used the NVME only for Swap storage.
Now yesterday the NVME suddenly was missing in the devices and the server obviously wasnt responding very well to swap missing, so it got stuck etc.. I rebooted, but swap didnt come back.
I checked if the disk was found, but I could not find it even with blkid, lsblk etc. So I unplugged the NVME and plugged it into my laptop.
In the Laptop it is recognized without a problem.
I then plugged another USB stick into the problem usb port on the Intel NUC , which didnt get recognized too. (And no DMESG messages).
When I plug in a keyboard it works flawlessly though. I can type and I see stuff in dmesg about USB plugged in or out when I unplug it, compared to the disk or the usb stick where nothing shows.
I then checked by booting into a live os if it is recognized there (gparted live), but also there it didnt recognize the disk on the USB port. Whats going on?
Is the USB port broken?
Maybe your OS distro has done that. According to other issues you reported there are going on some strange things on your system that are not done by OMV.
I use no custom OS distro. But okay - if this behaviour is unusual I will try to get to know what is going on.
https://docs.openmediavault.or…/various/fs_env_vars.html
this link would be helpful for others maybe.