Glad it worked out for you, specially since I believe you didn't made a backup of the OS prior to upgrade, correct?
Sadly, you are correct.
I'll be more careful in the future. Thanks for the reminder.
Glad it worked out for you, specially since I believe you didn't made a backup of the OS prior to upgrade, correct?
Sadly, you are correct.
I'll be more careful in the future. Thanks for the reminder.
How? And why?
Was it not ready yet?
I saw someone posted it on reddit and I tried it right away. Thought it is ready already.
Maybe I read too fast lol.
OMV6 uses it.
OMV7 uses php8
If your upgrade was ok, it should be correct.
It was okay, except for nvidia, but I solved the nvidia part.
After finished upgrading, I can see nginx config still using php7.4 instead of php8.2.
Luckily simply running omv-salt stage run deploy fixed the issue for me.
Problem solved.
I ran this command to fix it.
omv-salt stage run deploy
After running it, I can see the nginx config is now correct and I can now login.
Hi. I just upgraded to OMV7 and I cannot login. When trying to submit the login form, it gave 502 error code right away.
I guess it is PHP problem. I see that OMV is using php7.4 in the nginx config, but php7.4 does not exist in OMV7.
Is it just me with this problem?
ZitatAlles anzeigen# systemctl status php7.4-fpm.service
○ php7.4-fpm.service
Loaded: masked (Reason: Unit php7.4-fpm.service is masked.)
Active: inactive (dead)
# systemctl start php7.4-fpm.service
Failed to start php7.4-fpm.service: Unit php7.4-fpm.service is masked.
# apt install php7.4-fpm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package php7.4-fpm is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'php7.4-fpm' has no installation candidate
$ cat /etc/nginx/sites-enabled/openmediavault-webgui
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
server {
server_name openmediavault-webgui;
root /var/www/openmediavault;
index index.html;
autoindex off;
server_tokens off;
sendfile on;
large_client_header_buffers 4 32k;
client_max_body_size 25M;
error_log /var/log/nginx/openmediavault-webgui_error.log error;
access_log /var/log/nginx/openmediavault-webgui_access.log combined;
error_page 404 = $scheme://$host:$server_port/#/404;
location / {
try_files $uri $uri/ =404;
}
location ~* /index.html|\.json$ {
add_header Cache-Control "no-cache, must-revalidate";
add_header Pragma "no-cache";
expires 0;
}
location ~* \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/run/php/php7.4-fpm-openmediavault-webgui.sock;
fastcgi_index index.php;
fastcgi_read_timeout 60s;
include fastcgi.conf;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
listen *:80 default_server;
listen [::]:80 default_server;
include /etc/nginx/openmediavault-webgui.d/*.conf;
}
Alles anzeigen
Thank you. Got it working
Hi. I am quite new to OMV, and now I want to install docker.
After searching the internet, I found these 2 official guides:
- Guide: Using the new docker plugin
- https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv
Although they are official, but they are different. So, which one do I follow?
The forum post ask me to create just containers folder, but the wiki said docker, appdata and data.
Also the wiki said I ned to create appuser user, but the other one just use root. root is not a good way to run docker right?
Can someone clarify? I have no dea which guide is the correct one and which do I follow.
Thank you.