Beiträge von numsi

I have huge files that I need to copy over from my NAS to my PC (when working on projects), so I'm planning on building 10 gigabit LAN network and I need to squeeze as much read bandwidth as I can.

Thank you for your reply.

I have a very fast cpu. Is there any downside to OMV having setup for only software raid? I mean in the sense of not being as fast as a hardware RAID?

I'm planning on having two drives in raid 1.

Hi,

I've read that if you have raid 1, the read speed should be faster than if you only use rsync to simulate raid 1 functionality.

Is this true? Is there any advantage to using raid 1, instead of manually setting up realtime backup from one drive to another?

Zitat von mi-hol

not possible ATM, only implemented for security updates starting with version 5.6.3

There is an open issue for this feature in github that you may want to support via a reaction

Alright, but can't I just use some standard cron job to update debian like `apt-get update && apt-get upgrade`?

What is the implication of that vs using the webUI's approach?

Hi,

How can I setup automatic updates in OMV?

I'd like to be able to schedule the installation of all the packages (once per month) that are shown in the `Update Management` section in the webUI.

Thanks

Zitat von ryecoaaron

Mine came from ebay.

A review on Amazon says it worked with Debian without any extra work. I don't have one so I can't confirm. If you want to send me one, I will test it

Haha I like your sense of humor :). Anyway I am grateful for the info you provided

Zitat von ryecoaaron

Out of the box. I don't remember the last time I compiled a driver for hardware.

Thank you for the info. Since I cannot get my hands on Mellanox, do you have any info on the Intel NICs, more specifically X550-T1 intel? Would that work right off the bat? I am looking into Base-T connection.

thanks for the info. Will these cards work right out of the box, or do I need to do some manual installing of drivers or such to be recognized?

Zitat von Adoby

I have no idea if that 10 GbE card will work with OMV. But you should be able to find out yourself.

OMV is built on top of Debian. Various versions of Debian for various versions of OMV.

Don't try to figure out if the card will work with OMV, instead figure out if the card will work with Debian. That should be easy to do with some googling. There are even Debian compability lists. If the card is not there, then you could use another card that is there.

Best is if the card is directly and fully supported, that is if the Linux kernel used in Debian will detect and use the card to the fullest without any extra hoops to jump. Typically that is only possible if the card use a chipset from some manufacturer that contributes to the Linux kernel. Or if the card is old enough to be in common use.

If you find sites detailing how to make the card work with Debian, that can be a very bad sign. That sort of information should not be necessary. It should just work. Plug it in. Install OMV(=Debian). Done. I did a quick search and seemed to find some of that kind of site for this card, but I didn't check closer. A bit worrying...

If the card will work properly with Debian, chances are better than good that it will work just fine with OMV.

Alles anzeigen

Yes I guess you are right. So what is the most commonly used 10GBe NIC for debian?

Can someone shed some light on how to install and use this card in OMV? I am thinking of buying one, but I don't know if it will work

Zitat von Giancky79

Code

map $http_upgrade $connection_upgrade {
    ''                      'close';
    default                 'upgrade';
}


server {
    listen 443 ssl;
    server_name _;
    add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
    ssl on;
    ssl_certificate  /etc/letsencrypt/live/nome-scelto-server/fullchain.pem;
    ssl_certificate_key  /etc/letsencrypt/live/nome-scelto-server/privkey.pem;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:!aNULL:!eNULL:!EXP$
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 5m;
    proxy_buffering off;
    location / {
        rewrite /(.*) /$1 break;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_pass http://ip:port/;
        proxy_set_header Host $host;
        proxy_redirect http://ip:port/ /;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
     	proxy_connect_timeout  3600s;
        proxy_read_timeout  3600s;
        proxy_send_timeout  3600s;
        send_timeout  3600s;
    }
    location /destination-name/ {
        rewrite /destination-name/(.*) /$1 break;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade
        proxy_pass http://ip:port/;
        proxy_set_header Host $host;
        proxy_redirect http://ip:port/ /;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
     	proxy_connect_timeout  3600s;
        proxy_read_timeout  3600s;
        proxy_send_timeout  3600s;
        send_timeout  3600s;
    }
}

Alles anzeigen

this one in case you have one address with multiple under address

This still doesn't work for me...

Zitat von Giancky79

Code

upstream proxmox {
    server "FQDN HOSTNAME";
}
server {
    listen 80 default_server;
    rewrite ^(.*) https://$host$1 permanent;
}
server {
    listen 443;
    server_name _;
    ssl on;
    ssl_certificate /etc/pve/local/pve-ssl.pem;
    ssl_certificate_key /etc/pve/local/pve-ssl.key;
    proxy_redirect off;
    location / {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade"; 
        proxy_pass https://localhost:8006;
	proxy_buffering off;
	client_max_body_size 0;
	proxy_connect_timeout  3600s;
        proxy_read_timeout  3600s;
        proxy_send_timeout  3600s;
        send_timeout  3600s;
    }
}

Alles anzeigen

This is my configuration for nginx and proxmox, but i use https, inside nginx you use letsencrypt certificate? and on router you open the port 80 and 443 with ip port of your OMV machine?

Yes I use letsencrypt certificate and yes I have both ports 80 and 443 open. I have nginx working properly for sonarr and radarr so I know that the issue is with wiki.js.

Zitat von Giancky79

hi, why you don't enter with https?, anyway

Code

server {
    listen 80;
    server_name _;
    proxy_redirect off;
    location / {
        rewrite /(.*) /$1 break;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_pass http://ip:port/;
        proxy_set_header Host $host;
        proxy_redirect http://ip:port/ /;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Alles anzeigen

I tried it just now, and it doesn't seem to work.
So what I'd like the path to be is mydomain.com/wiki.

Hi,
I'm having troubles setting up nginx config for wiki.js. I am running the beta (version 2.0.0-beta.275) on a docker container. So far I've tried to use the official documentation on nginx - but it won't work. Maybe it is because the documentation is for the previous version (version 1.0.117)

This is from the official doc:

server {    
  listen 80;    
  listen [::]:80;    
  server_name  wiki.example.com;
  location / {        
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_pass http://127.0.0.1:3001;
    proxy_http_version 1.1; 
    proxy_set_header Upgrade $http_upgrade; 
    proxy_set_header Connection "upgrade"; 
    proxy_next_upstream error timeout http_502 http_503 http_504;
  }
}

Has anyone had experience with setting it up?

Zitat von Morlan

maybe this helps:
https://forums.sonarr.tv/t/ngi…oxy-sonar-ver-issue/17506

Otherwise you could set up letsencrypt including a nginx reverse proxy in docker with the linuxserver/letsencrypt image. An up to date guide is also provided:
https://blog.linuxserver.io/20…rypt-nginx-starter-guide/

I've fixed it - I made a simple mistake and forgot to reboot sonarr :). After that everything worked fine. Thanks for the links I will check them out

I have followed this tutorial: https://daan.dev/how-to/revers…darr-sonarr-transmission/

I’ve successfully installed the certificate, and installed sonarr as docker image – and configured ngnix. The problem is that i get the following
web page when I try to load mydomain.com/sonarr (this image shows my internal IP, but the same thing happens if I use my domain):

I’ve port forwarded port 80 and 443 in my router to my OMV server. Also the OMV server has ports 80 and 443 setup in general settings > web administration.
What am I missing for the reverse proxy to work?
Thanks.

Zitat von ryecoaaron

You setup your port forward wrong then. Opening two incoming ports shouldn't affect anything outgoing. While docker is hitting https on port 443, that doesn't mean the return port to the client is 443 (and most likely not).

I've fixed the issue. The problem was that I had opened UDP ports as well as TCP.
The only thing that was needed was TCP ports 80 and 443.

Hi,
My OMV has the following private IP 192.168.10.107. In order to implement LetsEncript cert I had to port forward ports 80 and 443 from my router (as you can see on the image)
forum.openmediavault.org/wsc/index.php?attachment/13063/

And that is all well and good, the certificate works. But the problem is Docker. When I have these ports forwarded, then when I try to pull image from Docker Hub, a timeout happens. That means that the docker hub cannot communicate back to the OMV. What do I need to change so I can have Let's Encrypt and docker working?

Thanks