Beiträge von Havoc

    If anyone else is having these problems, try running the command


    Bash
    export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

    It may fix stuff. If it does, just add it to the "bashrc" file. Otherwise, good luck.

    So, I recently re-installed Debian on my server and installed OMV on top.


    Today, I saw that a few packages needed upgrading but, OMV didn't want to do it (some error, I forgot what). So, I boot up the SSH connection and run `apt upgrade`. And then everything broke.


    I tried logging into the control panel, to no avail. I figured I screwed something up during the upgrade so I tried omv-firstaid. And it didn't exist.


    It's at this point I thought I should reinstall OMV. Which, hasn't worked at all.


    Any help would be appreciated.


    Output of `dpkg -l | grep openmediavault` (apparently this is useful)


    Bash
    root@olympus# dpkg -l | grep openmediavault
    ii  openmediavault                   4.1.17-1                     all          openmediavault - The open network attached storage solution
    ii  openmediavault-keyring           1.0                          all          GnuPG archive keys of the OpenMediaVault archive
    ic  openmediavault-letsencrypt       3.4.5                        all          Generate free and valid SSL certificates for OMV
    ic  openmediavault-minidlna          3.3.11                       all          OpenMediaVault miniDLNA (DLNA server) plugin
    ic  openmediavault-nginx             4.0.3                        all          Nginx plugin for OpenMediaVault.
    ic  openmediavault-omvextrasorg      4.1.15                       all          OMV-Extras.org Package Repositories for OpenMediaVault
    ic  openmediavault-transmissionbt    4.0                          all          OpenMediaVault Transmission (BitTorrent client) plugin.

    So it wasn't necessary to change the policy setting, as outlined at the bottom? -> Update 11/26/18 - SMB Guest access


    Just the items at the top?


    (This is just for clarification, for other forum/Win10 users.)

    That is correct. I followed the instructions "Set Private Network" (it was previously set as part of a business network), restarted my PC and authenticated access to SMB was working again.


    Personally the workgroup and the advance network sharing options were already in line with the "Set WORKGROUP name" and "Advanced Sharing Settings" parts of the guide so, I didn't have to fiddle with them (others may though).


    And yes, I can still access shares marked as "Only Guests" without following the "Update 11/26/18 - SMB Guest access" part of the guide.

    Ah ha!


    I did originally find that post but, assumed it was only for guest access to the server (and since I was having issues with authenticating, thought it didn't apply here). After changing the network settings, as suggested at the top, I can now connect via SMB again! Woo!


    Thank you very much for the help :D

    I dont want all request to be sent to nextcloud, only the one using hostname nextcloud.domain.local

    If you use the "name-based" host type, NGinx should only respond to requests for that domain (now, you would have to have the domain pointed to the server's IP which, it sounds like you do).



    I may be doing something wrong : but: may you clarify wich options i should use in nginx plugins?


    I hope this screenshot helps you:


    As you can see the "Server Name" should be the domain name you want NGinx to respond to. Then, putting the code I sent previously inside this server would send all requests to "nextcloud.domain.local" to the nextcloud server.



    also this " proxy_pass 127.0.0.1:8095;" seems strange cause i want to use https

    Yes, NGinx handles the SSL stuff. This just shows NGinx where it can send the data to. Since NGinx and your nextcloud server are on the same machine (assumption) you are OK to have an insecure connection here.

    Couldn't you achieve this with the name-based listening option on NGinx with the reverse proxy listening on the default route?


    Adding something like the code below to the "extra options" field should be enough to route all requests to the NGinx server to your nextcloud server:


    Bash
    location / {
        proxy_headers_hash_max_size 512;
        proxy_headers_hash_bucket_size 64;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        add_header Front-End-Https on;
        proxy_pass http://127.0.0.1:8095;
    }


    Then you would have to set up nextcloud config: https://docs.nextcloud.com/ser…_proxy_configuration.html

    So, I've had this server running with OMV for a couple of months now with no problem at all. It's been working nicely, and I had everything set up as I wanted (it hosts a basic website and stores a bunch of video files which were accessible over SMB shares).


    However, the other day I noticed I couldn't access the SMB shares that require authentication anymore. I did a bit of research and came to the conclusion that it's Microsoft's fault (could be an incorrect assumption) with their newest Windows update. I thought I'd write it off as a loss and set up NFS shares. I didn't have much success with that either but, I could still access my files over SCP so I gave up.


    Then I thought of setting up FTP. And no. Didn't work. I thought maybe it was my password, so I changed it. Still wouldn't log me in (the error message was saying the creds were wrong but, I know they weren't).


    The problem isn't with the protocols themselves, I can still access my files whilst allowing Anonymous connections. But, I don't want Anonymous connections (I don't want my family members to be able to modify the website files, only view the videos). I've even checked the "permit root" login on the FTP service but, I couldn't even authenticate then!


    So, I'm thinking there's a problem with the authentication that these services use somehow. But, even then, there should be a problem with SSH, no?


    I'm honestly at a loss here. I can't think of what the problem could be or why the issues are suddenly a thing (I only noticed it a couple of days ago).