hi all,

1st, system is online!

i just try to clone that HDD with HDClone - the tool called some errors on 6 Sectors and i decide to just ignore that.

after change the old to the new HDD the nas starts as normal, all data in place, all services work - i think i will see if somethink wrong with it the next few days, but all in all it looks consistent.

so again, thx all

hi,

first, THX will try later.

1 question, my damaged HDD got Lable NAS1 - so i just put in the new one, copy all data to the new one, shutdown, plug off the old on, restart and follow your instructions, right?

hi,

can you give me some more details Soma

the new device should arrive today.

may you can offer a small step by step how-to to me?

so i'm hope you will not the only one who read this

the data will not be that big problem, have backups of important things.

i discovered it when nextcloud stop working (nextcloud data are saved on that disk) - so a copy job would also ok for me.

how can i manage that lable part? i can't just build in the new disk and name it NAS1 i think

on windows i would just add the new one, copy all data, disconnet the old one and set drive letter of the new disk to that from the old one^^

hi all,

need some tipps plz.

my main Datadisk is going down (today some services dosen't work, and then the shock: sdb is going down - could reup it as sdd but, its time for a new disk ...)

what is the best practice to do?

cloning the disk by using a other system and tools like hdd clone?

build the new one in and copy everything?

whats about the lable? most of my services connect to the disk by the lable name "disk-by-lable-nas1" so the new disk need the same lable.

thx and regards

draddy

hey,

maybe that will help you DB Backup & Restore

in the last post you will find the scripts - was designed for backups so it should work.

if it dosn't automatically renew: watch this add in the how-to.

hi,

have anyone run zoneminder in omv5 as a docker?

maybe a "ready to use" composer file?

thx all

oh now, that will sometimes appear but in my case it stuck at some point and lost config file for nginx / omv ... that was just the default one and broke down with the other system config i think, but don't know, maybe the boss can just work with that infos.

what ever, maybe my nas got a sniff or something like this

the config worked all day now and for many updates - so maybe it was just monday on thursday - i don't know

WTF! ...

here we go:

after that and a lot of google i looked into:

nano /etc/nginx/sites-enabled/openmediavault-webgui

and found

    listen [::]:80 default_server ipv6only=off;
    listen [::]:443 default_server ipv6only=off ssl deferred;
    ssl_certificate /etc/ssl/certs/openmediavault-.crt;
    ssl_certificate_key /etc/ssl/private/openmediavault-.key;
    include /etc/nginx/openmediavault-webgui.d/*.conf;

compare with the version macom give to me and uncommend to

    listen [::]:80 default_server ipv6only=off;
#    listen [::]:443 default_server ipv6only=off ssl deferred;
#    ssl_certificate /etc/ssl/certs/openmediavault-.crt;
#    ssl_certificate_key /etc/ssl/private/openmediavault-.key;
    include /etc/nginx/openmediavault-webgui.d/*.conf;

new try with apt-get install --> error --> deeper look now tell me a bind error (sure, :80 will be used by my letsencrypt docker ... )

docker stop letsencrypt

again apt-get install

its done ... try to connect web gui --> nope --> ok, i tried with MY port 8080 ... so lets try port 80 --> welcome back OMV - change ports twice --> error occure ... ok reload site: not found (bad? NO its good) try again with port 8080 --- here we go!

docker start letsencrypt

looks like everything is back in place

should it only be happend cause i have not activate SSL and changed http port??

noone else changed the omv port away from 80?

plz check that to prevent other from getting trouble.

i'm out

thx!

will try it - if my omv is working again -.-

€dit: works

hi,

just see updates in the house - so i just do like normal in omv interface - updates - check the all box click install.

ERROR ERROR ERROR ... - close - reload - omv not reachable ...

SSH: apt-get update --> apt-get upgrade

Setting up nginx-full (1.14.2-2+deb10u3) ...
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-08-27 10:03:48 CEST; 13ms ago
     Docs: man:nginx(8)
  Process: 24003 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Aug 27 10:03:48 greeNAS.GREEN systemd[1]: Starting A high performance web server and a reverse proxy server...
Aug 27 10:03:48 greeNAS.GREEN nginx[24003]: nginx: [emerg] BIO_new_file("/etc/ssl/certs/openmediavault-.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/certs/openmediavault-.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Aug 27 10:03:48 greeNAS.GREEN nginx[24003]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 27 10:03:48 greeNAS.GREEN systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Aug 27 10:03:48 greeNAS.GREEN systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 27 10:03:48 greeNAS.GREEN systemd[1]: Failed to start A high performance web server and a reverse proxy server.
dpkg: error processing package nginx-full (--configure):
 installed nginx-full package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nginx:
 nginx depends on nginx-full (<< 1.14.2-2+deb10u3.1~) | nginx-light (<< 1.14.2-2+deb10u3.1~) | nginx-extras (<< 1.14.2-2+deb10u3.1~); however:
  Package nginx-full is not configured yet.
  Package nginx-light is not installed.
  Package nginx-extras is not installed.
 nginx depends on nginx-full (>= 1.14.2-2+deb10u3) | nginx-light (>= 1.14.2-2+deb10u3) | nginx-extras (>= 1.14.2-2+deb10u3); however:
  Package nginx-full is not configured yet.
  Package nginx-light is not installed.
  Package nginx-extras is not installed.

dpkg: error processing package nginx (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openmediavault:
 openmediavault depends on nginx; however:
  Package nginx is not configured yet.
  Package nginx-full which provides nginx is not configured yet.

dpkg: error processing package openmediavault (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nginx-full
 nginx
 openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)

need help plz to get it working again.

thx all

hi folks,

just updated my Nextcloud to 18.0.8 and do a routine check in Settings to check its all right ... but what i see: Nextcloud 19.0.2 available

anyone have done it? - some little how to about it? - something critical to know?

thx

hi,

situation in short:

OMV 5 NAS is running with nginx / Letsencrypt Proxy - work well with Nextcloud and all the stuff.

2nd maschin in my Network is used for testing stuff and / or sometime dedicated gameplay servers (Minecraft, Factorio what ever)

atm this 2nd is running a Minecraftserver - to control the server (start, stop, backup and stuf like this) is use crafty controller. crafty is running its own tornado server, i can access in the local network with https://IpOfHost:8000 - now a friend would like to have the ability to restart the server if it hangs. "Yeah, sure, i will just forward the port for you" ... and - he can only access the crafty page with Microsoft edge, all other browsers say bad Certificate and don't let you access ...

ok - np - i just redirect it with my nginx proxy ...

location /crafty {
    return 301 $scheme://$host/crafty/;
}

location ^~ /crafty/ {

    # enable the next two lines for http auth
    #auth_basic "Restricted";
    #auth_basic_user_file /config/nginx/.htpasswd;


    include /config/nginx/proxy.conf;
    resolver 127.0.0.11 valid=30s;
    set $upstream_crafty crafty;
    rewrite /crafty(.*) $1 break;
    proxy_pass https://192.168.177.13:8000/;
    
}

all right, little test, all right i get the login page of crafty control, easy.

"i see the login, but after login i only get a 405 ..." was my friend crying .. lets try, yeah, he's right, no way to login ...

405 Not Allowed

nginx/1.16.1

soo, now you are on; some ideas? what is to change?

if i local access the crafty server, the url will change to https://IpOfHost:8000/admin/dashboard where "admin" is the username - if i try to login with mydomain.tld/crafty - it change zu mydomain.tld after klicking login.

hopefully someone have an idea what to change to get it working.

thx

jens

hi,

in addition to my how-to upgrade nextcloud i just thought a little script could do the job as well

echo "upgrade Nextcloud ..."

docker exec -it nextcloud sudo -u abc php /config/www/nextcloud/updater/updater.phar

docker exec -it nextcloud sudo -u abc php /config/www/nextcloud/occ upgrade

docker exec -it nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off

echo "... upgrade done"

that will work, but i still have to interact

the first command will 1st ask "will you start update" so just y and enter to run ...

after that it will ask to run occ upgrade (that don't work) so just n and enter

the other commands just run

so my question: can i add the answers for the two questions to the script?

thx!

hi folks

@Kritta left me a commend what say onlyoffice will not run on ARM systems, thats right, and i never told that - sorry that you waste time on this.

hope this can prevent others, for more details plz visit the docs of onlyoffice it self.

hm hm

if i try to connect

cseb.is-gone.com

i can get your OMV so i just wondering, cause, your omv will listen to port 80 for http if you haven't change it, and your config say you forward port 80 extern to port 81 in your network - and on 81 in your network is the letsencrypt listen container listen to - so: if i try to connect i have to reach your letsencrypt proxy OR have to get an error like page not available.

don't know your router, but dobblecheck the settings, maybe reboot it and recheck the settings - for me it looks like that letsencrypt can't do the needed checks on http and https to verify your domain and sign your certificate.

hi,

the error happens right after run the compos file?

have you port forward 443 and 80 to your RPI2?