Beiträge von Wek

  • SSH public key authentication failing to connect

    Hi, I was setting up my fresh installed Omv5 to have access only through SSH public key auth but no matter what I try it keeps give me authentication failing to connect.


    What I did

    • I created an user and gave him ssh permission (with password works great)
    • created ssh keys with ssh-keygen and check that the public one was matching between the user and the /var/lib/openmediavault/ssh/authorized_keys
    • disabled permit root login and password authentication

    still what I get is wek@192.168.1.2: Permission denied (publickey).


    So I went ahead and looked at the /var/log/auth.log to see what was going on:



    Not really informative, so I went inside the server and check the permission for the authorized key and seems fine:


    Finally I thought to check the /var/log/auth.log and found this:



    Now first of all I didn't pay really attention ever to the / folder on other machines, but that directory permissions look a bit strange to me, or am I missing something?

  • Omv-Extras broken package to install the repo on Omv5

    I did a fresh install of the latest Omv5 iso, I was trying to install omv-etras repos, as per instruction with wget -O - https://github.com/OpenMediaVa…ckages/raw/master/install | bash but I get this error while installing it:



    so I'm ending up with a broken Omv-Extras broken repo, I already tried install manually and even from terminal, but all gave me same error, looks like something weird with the *.deb package itself


    Anyone knows how to fix this?

  • Omv 5 is still in beta? I'm a bit confused

    Hi Guys,


    it's been a while since I posted here, being busy at work lately.
    Today I had some spare time, so I decided to have a sneak peak here and see how things are going, with the chance to see if I need to upgrade any of my servers (they run omv 4).


    I got stuck though and a bit confused by the omv site, so here is my question:


    Does Omv 5.0 still to be considered in Beta? or is it ready to use in production?
    it's a long time since I remember that it was already in beta, omv homepage get me even more confused, as I click on download and redirect me to sourceforge I saw 5.0.5 folder and 5.0 beta folder...other than that the blog report some images of a new version in the progress OMV 6 (?!?!).


    So what is going on here? :D
    Can someone help me out to understand the situation right now? :)


    Anyway have a nice Xmas to everybody :)

  • Cannot access Omv after some uptime, every service is unreachable

    Anyway I just went through a run test of it, but I can't understand, I'm a bit confused by the suggestion, here's the result:


    of the command:


    Linux 4.19.0-0.bpo.5-amd64 (wai) 06/13/2019 _x86_64_ (4 CPU)



    avg-cpu: %user %nice %system %iowait %steal %idle
    1.94 2.20 1.43 5.64 0.00 88.78



    Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
    sda 105.77 1195.04 587.14 1173971 576788
    sdc 0.30 11.54 0.49 11337 486
    sde 0.35 14.40 1.03 14144 1014
    sdb 2.73 38.57 3.04 37889 2989
    sdd 34.48 283.68 189.21 278681 185870



    How an hard disk\cpu monitor should help me out to understand why after some uptime the services seems to be like "cut off" from the lan? what should I found in it? it just spits out statistics about reads\writes and cpu usage...am I missing something?

  • Cannot access Omv after some uptime, every service is unreachable

    No I'm not using flashmemory plugin, I just supposed it has been deleted because from the logs through the openmediavault webpage doesn't look anything strange everything seems to be fine, except most of the logs are deleted like syslog etc. because I had to hard reset the machine to get back to it.


    Also I looked at dmesg errors, nothing strange expect some warning about ACPI errors due to bios not really good implementation of it, but nothing strange it's been there since the beginning, also another error from the docker container of emby, saying "emby-daemon.service: Failed at step USER spawning /usr/bin/mono-sgen: No such process" again don't know why is saying that at the startup of the deamon, but everything works fine (once I rebooted of course).


    Syslog dmesg and Messages, seems pretty normal so I didn't know what to look for, I'm using the command you suggested, so let's see what happens, but I guess I have to make it as a cronjob am I rihgt? because otherwise it will be killed as soon as my shell get cut out due to the server strange behaviour.

  • Cannot access Omv after some uptime, every service is unreachable

    Hi everyone,


    Since a couple of months, I'm having some weird issues with Omv4.


    As soon as I boot up the machine everything works fine, I can reach the smb shares, ssh into it, login through the webinterface, check transmission everything's good,
    BUT as soon as the machine stays uptime for some time, it begin to be "unreachable".


    I put it on quotes, because in fact the machine is online I can ping it, and I can see it through the modem connected, but I cannot login or use any of the services in it.
    example:


    • I try to login through the webserver -> firefox doesn't complain about not reaching it (so the site weblogin "is present") but the page is blank no banner no nothing
    • I try to ssh into it, it just answer back that the server needs a passphrase to login (which it needs indeed, but is like it doesn't see my private key that I sent to it, so it doesn't let me login in)
    • samba shares complain about being not unreachable

    The only fix I found is to hard reset the machine so everything boots up again it works as it should for some time and then everything back to square 1.


    Unfortunately I cannot investigate the problem any further with logs, because doing an hard reset it basically erases any traces or at least traces I can think of.


    Did any of you experiences same issues and know how to solve it? or can give me an idea on what to look for?



    Some specs:
    OS: Omv 4.2.22-1 Arrakis
    kernel: 4.19.0-0.bpo05-amd64

  • Bitwarden and Letsencrypt Remote Access Issue

    Hi everyone I'm having a little trouble accessing bitwarden remotely through the use of duckdns and letsencrypt + reverse proxy, I hope someone can help me I'm still in the learning process.


    I developed bitwarden through docker as @TechnoDadLife explains in his tutorial

    Externer Inhalt youtu.be
    Inhalte 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.


    Unfortunately the process let you with a local access through standard port, no https, so I decided to go the route duckdns+letsencrypt+reverse proxy (everything through docker) to access it remotely via https.


    Every container worked fine on its own:


    • I have my domain let's say iloveomv.duckdns.org
    • I created my subdomain inside letsencrypt docker, let's say bitwarden.iloveomv.duckdns.org
    • I open the right ports on my router and everything works fine I can see my page remotely with https answer back and the letsencrpy ssl certificate going through.



    Now the problem happens, I can't connect my bitwarden loal docker to the subdomain https://bitwarden.iloveomv.duckdns.org without getting the error 504 from nginx when I try to connect to it.




    Sure I suspect is an error on my part, tryng to config the bitwarden docker, so I went ahead and look at the info page of the docker itself -> bitwarden docker


    Here is the first problem as you can see, on the docker infopage itself, there is no variable to set https, it seems to operate just through http.



    Reading further there is a way to activate https trough ROCKET_TLS, and use this proxy config, for letsencrypt docker.



    So I tried this:


    • created a variable environment on the bitwarden docker as ROCKET_TLS, giving it physical access to the sharedfolder where fullchain.pem and privkey.pem produced by letsencrypt are stored
    • changed the due localhost parameter with the duckdns domain on the proxy config
    • added --network mynetwork flag to the bitwarden container to let it talk to letsencrypt container

    but none of it worked out. I'm still getting error 504 when I try to connect to https://bitwarden.iloveomv.duckdns.org



    Any idea what I'm doing wrong here?! can someone point me in the right direction?!


    Thank you very much in advance

  • iptables error while creating new rules (or changing existing ones) -> Failed to execute command

    I was trying to add a firewall rule for mariadb on the port 3306 and I noticed the firewall is acting weird not letting me add or modify any rule..giving me the Failed to execute command routine as you can see from the error code down here.


    I don't think is something strictly related with iptable, but I'm getting this problem only with it at the moment.


    Any suggestion on how to solve this?


  • Windows 10 gives errors trying to connect to a omv samba share

    @donh sure here it is pretty straight forward.


    Sometime windows acts weird if you just save user password to a share through the popup window that appears once you select a new share.
    The thing is windows almost always forget the password or has confusion about how password get saved, especially on windows7 and windows10 (there is a bug never solved).


    So the right way to set a persistent share (no need to type user\pass everytime on reboot) is thorugh credential manager.


    To do that just pres windows key and type Credential Manager on the search bar and open it (the icon is the one of a safe)
    Icons\disposition of icons varies between windows versions but it's pretty simple to understad.


    At the credential manager opening you may see a list of server you saved, despite that the Persistence value is wrong, so to have a real persistent and consistent password saved on boot you just need to recreate the credential you are after:


    • Select the Share you saved if present on the credential manager expand the menu and select Remove from vault. (after that of course the user\password of the share will be deleted)
    • Click on Add a Windows credential
    • On the new page on Internet or network address just put the address of your share ex. \\ThisIsMyShare or the IP if you prefer ex. \\192.168.1.8
    • User name and password are self explanatory after that click on Ok
    • After that you will see the new entry will be created and the new entry has Persistence: Enterprise (if that is the result you did it right otherwise just restart from point 1.)
    • Enjoy your new share correctly configured in widnows

  • Windows 10 gives errors trying to connect to a omv samba share

    @donh after some tests, it seems that I've fixed the issue at least those pc didn't complain about since yesterday.


    None of the fix proposed about the error fixed it neither the netbios tcp\ip setting.
    The thing that I changed that seems to work, was a trick I used on windows 7 too and it is to go through the credential manager of window, delete all the Windows Credentials created automatically, and create a new one from scratch, giving username password and server on the respective fields.
    In this manner windows creates an enterprise persistence with them, after that the pc stops to complain and it works out of the box with the samba share on every subsequent reboot.


    Thought to share it with you, because I didn't see this fix in your thread, so maybe it's worth to know for you as well

  • omv 4?

    @Huberer thanks pal, didn't see the thread, unfortunately for me the trick to apt clean didn't work out I will wait for ryecoaaron and notice about the support email he sent.
    Until then it seems not to be too much problem so it's ok

  • Windows 10 gives errors trying to connect to a omv samba share

    I will try it, but I guess will not work I was looking for the error code and saw tons and tons of same windows error with users apparently microsoft fucked up again with samba share I will see if I can solve it through activating netbios\tcp on the lan as I saw many of them solve it like that..


    If you have any other suggestion fire away

  • Windows 10 gives errors trying to connect to a omv samba share

    I have some weird issues with omv samba share, and some windows 10 machines of a client, randomly when they try to connect to a samba share of omv, when those machine come up fresh from boot or when they connect with a username and then try to reconnect with another username or again when one user try to connect with same username and passowrd from 2 different pc at the same time.
    Of course those are all different errors, so I will try my best to enumerate them and if you know how to fix them that would be great!


    • Windows on startup seems to not find the server anymore and throws the error in the attachment, with the error code 0x80070035, sometimes after a while it works again like it should, sometime it requires a reboot to make samba work properly. (the network is not mapped the user accesses it through the network folder, I remember windows 7 had problem with networks share and you have to force save credentials through the manager, does windows10 has something similar?)
    • An user has two different pc, he tries to connect to the samba share with the same username\password at same time but it gives errors until he disconnects one of the two. (I don't use windows so I don't know if it's windows or something on omv preventing it, but on my home I have a mac and a debian system I connect both of them at the same time with same username\password and the share works like it should, am I missing something or some samba settings?! I thought it should work like that as default..I mean linux should manage them as same user connecting to the server so why one is accepted and the other refused?!)
    • If a user is connected with one username\password to a samba share and try to connect to another share on the same nas with a different user and password it works, but when the same user try to go back and connect with the previous username\password it fails with the error ...the user could not have the right permissions... (that of course has on the server)


    For what is worth all the shares has been set with admin and group with the access\write permissions and others with none but all the users accessing the nas has users\password created on the server so everything should work fine, actually it does when windows decide to not cry about anything it just random errors any ideas?!


    If you need other info please tell me I will provide them thanks.