whoopsie!!
i don't knowing this
https://pve.proxmox.com/wiki/Disk_Health_Monitoring
Beiträge von Giancky79
-
-
Code
Alles anzeigenmap $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; } }
this one in case you have one address with multiple under address
-
Code
Alles anzeigenupstream 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; } }
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?
-
I don't know your hardware or use case. I run OMV as a vm under proxmox. This way keeps OMV stock.
If you want to use zfs do it under proxmox and assign what you need to OMV. I have had no problems with zfs under proxmox yet.
You will also have more options for running vm's. One disadvantage is proxmox does not do docker. But you can always run a vm for that.
strange, i use docker inside lxc without problem. For vm in proxmox, OMV and passtrough hdd, i have problem with S.M.A.R.T., any test not working for check.
-
no problem with portainer and cokpit in the same machine?
-
Hi, with OMV 5, i don't found anything for VM, which future for virtualization?
-
hi, why you don't enter with https?, anyway
Code
Alles anzeigenserver { 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; } }
-
i have the latest update 4.1.22-1 (arrakis) with proxmox kernel, no other update
-
Error: "Failed to read file '/tmp/bgstatusfs2WVj' (size=0)."
@ryecoaaron can you help me or the solution is not install virtualbox?
-
permission folder is not the solution, very sorry for twice message, OMV is a very good solution for NAS
-
yes is the last update, but i have found a fix ( i think is my inexperience with a permission folder), i put privilege in group and not working, if i put privilege for single working, is correct? nope, not working
Code
Alles anzeigenErrore #0: OMV\Exception: Failed to read file '/tmp/bgstatus85zHjq' (size=0). in /usr/share/php/openmediavault/json/file.inc:207 Stack trace: #0 /usr/share/php/openmediavault/json/file.inc(223): OMV\Json\File->getContents() #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(340): OMV\Json\File->read() #2 /usr/share/openmediavault/engined/rpc/docker.inc(262): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatus85...', '', Object(OMV\Exception)) #3 [internal function]: OMVRpcServiceDocker->pullImage(Array, Array) #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('pullImage', Array, Array) #6 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'pullImage', Array, Array, 1) #7 {main}
ok i found where is the problem, or i hope is this the problem, when install virtualbox, inside tmp directory i found a file <.vbox-vbox-ipc> with permission root, after reboot permission changed in 997, after that, the error tmp appear.
deleted virtualbox and reboot, the problem not appear -
sorry for twice post, but the first one is an error because the post is under tag 3.x of openmediavault, i think to post another message with 4.x tag, true sorry
-
after update to pve 4.15.18, on new installation, after install plugin from omv-extra, with docker and casual installation from other plugin, i have this error. The error appear on docker after reboot, and after deleted copy of docker and fresh installation, when reboot appear
-
maybe the problem is fixed, but i have same problem with docker or after install plugin from omv-extra. With new version of openmediavault change something or we found same problem? version pve-kernel (4.15.18)
-
after all i have found a solution, acl permission is the answer
-
running but is not working, i need to configure the node red docker
-
tell me what other info you need
-
Hi, i try install Node-red docker, i'm searching on internet and i have found only this
Externer Inhalt www.youtube.comInhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.
After put PUID and PGID, port and folder /node-red(omv):/data(path), save, node red doesn't work. Can help me someone for this docker? -
after all command you have reboot?
-
you have problem with acl on folder you use for Virtualbox. Serching on ACL permission vbox and give him a RW permission