Posts by draddy

    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 :)

    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

    WTF! ...


    here we go:


    after that and a lot of google i looked into:

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


    and found

    Code
    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

    Code
    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 ^^

    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




    need help plz to get it working again.

    thx all

    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 ...


    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


    Code
    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!

    hm hm

    if i try to connect

    Code
    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.