Beiträge von madoasp

Hey together,

i've just installed wireguard on my omv machine (omv version 5.5.20-1) by myself, without any suggested script here.

"Ip a" show three network devices

• lo
• enp2s0
• wg0

Everything went smoothly and the wireguard connection between my omv server and my clients works flawless.

My intention in doing this was to create a nfs-share which is accessible from the wireguard ip-range.

I created the share, but unfortunately it isn't visible for my clients. Running

• showmount #IP_of_my_OMV_Server_enp2s0-Interface#

or

• showmount #IP_of_my_OMV_Server_wg0-Interface#

works for both IPs, but only show my normal nfs shares created for the ipramge of the enp2s0 interface, but not those i created for the wireguard IPs.

I think maybe it is because my wireguard connection isn't known by openmediavault. If i go in the omv web configuration System\Network\Interfaces there is only my enp2s0 interface listed. I see no option to add my new wg0 interface here :/...

Do you think the missing interface is causing my not visible nfs share? Or is this another problem? Does anyone knows how i can achieve nfs shares restricted for my wireguard connections?

Thanks in advance and kind regards!

Thanks for your help, creating the symlink with the command line works smoothly!

I only need three symlinks, so everythink ok, i'm just using the command line option on this install

Have a nice evening!

Here are two Screenshots. The same error as i mentioned above.

Because of the errormessage the normal "Add symlink" Window doesn't close and i'm to click the save button multiple time (in this example i clicked it twice...) which adds multiple entries in the activated symlink-list...

But:

ls -l /mnt/symlinks/Data_Rsnapshots/ says: "total 0"

Hello together,

i'm just setting up a new installtion using OMV 5.3.8-1.

Everything was fine, i've set up nearly everything i need including two Symlinks which worked smooth.

Now I've tried to add a third symlink and getting an error. From everythings regarding symlinks seems to be brocken, i'm not able to edit existings or create new entries :/...

The errormessage i get is:

Fehler #0:

OMV\Exception: Failed to create symbolic link at /mnt/symlinks/Data_Rsnapshots in /usr/share/openmediavault/engined/rpc/symlinks.inc:91

Stack trace:

#0 [internal function]: OMVRpcServiceSymlinks->setSymlink(Array, Array)

#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

#2 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setSymlink', Array, Array)

#3 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Symlinks', 'setSymlink', Array, Array, 1)

#4 {main}

Any advice :/? Already tried un-/reinstalling the extension, reboot, browser without any stored cookies... Nothing helps .

After i tried to create a new symlink the entry is visible in the webinterface, but the created symlink doesn't work on the destination folder...

Thanks in advance!

Hi together,

I'm running in the same problem, but unfortunately I dont't have any start-stop-daemon.REAL in my sbin directory

root@xxxx:/sbin# ls start-stop-daemon
start-stop-daemon
root@xxxx:/sbin#

Any advice :/...? Or would someone be so kind to upload the file for me?
Thanks in advance!

hey @sehnix

i just found this thread while searching for a solution for myself..
I absolutly do like your philosophy ("like to have my data on my servers ") and want to achieve the same. Or at least i want to try it to see if i am pleased enough to cut off my cloud-connection for sync contacts and calendar (and if possible bookmarks likewise).
So i would like to hear how satisfied you are with your test environment? Was it good enough for your needs and are you using it in your prod-system (or planning to do so)?

No matter @ryecoaaron, I think you help here in the forum more than enough, really awesome!
Thanks for replieng @subzero79!

I tried what you mentioned, and it is really a step forward.
I changed the remote server field as you said to refer to the /media/UUID-Path of my disk of the omvx-system.
And: the rsync script works, thanks!!

But: In best case I would like to avoid referencing the share via the qualified UUID-Path of my harddisk.. Using a Share configured within the webinterface and a rsync module seems the more attractive way for me... Isn't there a chance to achieve this?

Hi,

unfortunately I still haven't get my rsync-job working over a ssh connection.
To understand what to do without messing up my production system I've installed two virtual machines, both running OMV 3.0.59.

Like i said, I didn't find a guide which helped me to get this working, but one forum guide (see [GUIDE] Enable SSH with Public Key Authentication (Securing remote webUI access to OMV) for this)
helped me a lot and i will referencing on this post in the next steps.

I've named my virtual machines OMV1 and OMV2.
OmvX (Ip: 10.20.20.10) is going to be my server with a running rsync module (share name is DATA).
OmvY (Ip: 10.20.20.11) is going to be my remote system, which should pull all data from the DATA-share from omv1 over a ssh secured rsync connection.

What I've tried until now:
On OmvY:
- I've created a ssh-certificate ("sshCertCreatedOnOmvY")
- I've exported the public key to a local file ("sshremote.pub") and changed the the public key file format to RFC4716
-> ssh-keygen -e -f ~/.ssh/sshremote.pub

On OmvX:
With the output of the ssh-keygen command i open the omvX webinterface and create a new user:
-> name: "certTest"
-> password: "123" (I had to put something in here...)
-> Shell: "/bin/rbash/"
-> Groups: "user" & "ssh"
-> Paste of the generated Public-Key a step above.

After this, i configure a rsync Server Module on OmvX to run as the user certTest (see pic1_rsyncModulOmvx.png & pic2_rsyncModulOmvx.png)
Now, in the webinterface of OmvY i create a new rsync job as displayed in pic3_rsyncJobOmvy.png

If i'm starting this job, every time this message is displayed to me:
Please wait, syncing <rsync://10.20.20.10/DATA> to </media/e3f92e85-17b7-4afc-b544-85da677b9810> ...

Identity added: /etc/ssh/openmediavault-a4b3dbf2-5a6a-4083-a9ab-6fcbd10b8eb9 (rsa w/o comment)
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
rsync: did not see server greeting
rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.1]

pic4_sshOmvx.png shows my ssh-configuration.

Unfortunately I don't know how to proceed from this point.. If i would have to guess I think I somehow have to authorize the created key to establish a connection... But I'm not sure how to do this :/...

Oh, sorry, I've just noticed I told nonsense...
Next to the Unlock button is the Lock-Button, this one is always grayed out in my OMV 3 installation...
I thought it was possible in a OMV 2.x version, but i just noticed it isn't.

So => Everything is fine for me

Thanks for your work @ryecoaaron !!
Seems fine for me now, no error-message about missing fsname attribute.

The only thing I still notice is, that I'm not able to encrypt my drive again when it is unlocked.. But for me, thats not a feature i will ever need.

Thanks!

Zitat von marcolino

Thanks for your help.

You still have the "missing attribute 'fsname'" error?

yes

Hi and sorry for the late reply,

I'm not using any raid.
I can confirm, that after i unlock the disk it is called "/dev/dm-0" in the File System.
But in contrast to marcolino it haven't any trouble to use it in the dropdown field as a drive of a shared folder. As soon as the drive gets unlocked i can select it there!

Hi ,

I’m having some issues setting up a remote rsync job correctly. I’ve searched the forum (for example:http://forum.openmediavault.or…-public-keys-do-not-work/) and the web, but still I wasn’t able yet to configure my setup as I want it (because I would like rsync to run over a ssh-connection).

What I’ve got working right now is:

My first Openmediavault installation, let’s call it “omv1” runs version 2.2.13 . This is my main server with one share, let’s call it “omv1_share1”, which I want to have backed up remotely every night.

My remote-Openmediavault installation, let’s call it “omv2”, runs version 3.0.59.

At the moment, I’ve configured omv1 to have running a rsync server module which shares the omv1_share1 folder. I’ve configured a user+password access in this share.
Every night, omv2 runs a rsync job and pulls the omv1_share1 (using the configured user+pw configured on the omv1 rsync-module) to his local disk. This works fine!
But – if I’ve understood it correctly – I have to switch from the user+password authentication to public Key authentication (which is selectable inside the rsync windows of omv2) to have this rsync- Job using a ssh connection, is this right?

Is this possible with this setup? Or is it necessary that my omv1-machine also runs Openmediavault 3.XX?
It’s unfortunately not clear for me right now how I would have to setup the public key authentication :/… can this be done using the web gui or do I have to switch to terminal to configure the authorized_keys file?

If someone could give me a tip or a useful link where everything is already explained I would be very grateful
Thanks in advance!

One thing i've notized: After i restarted my installation, every time i try to unlock my disk i become a error about the missing attribute 'fsname' (screen1.jpg).
This messages repeates every time i click the OK Button, but however the disk is unlocked successfully. Everything works fine after that, except I'm not able to lock the disk again. The Button is grayed out and inactive, just as the unlocked Button (screen2.jpg).

The Luks-Plugin is one of my most loved plugin in omv for me.
I'm already very thankful to Luxflow & ryecoaaron for investing time to porting it to omv 3.

I've just set up an rpi 2 running omv 3.0.59 and will testing it a few days/weeks with the ported Luks encryption plugin.
For now (having it running for 1 day) everything seems to work like a charm, I haven't noticed anything until now.

Using this setup right now in combination with the Remote Mount+Rsnapshot Plugin's to achieve a remote Backup of my primary OMV installation.
I will leave this as it is for a few days and test then, if the encrypted drive can be decrypted on another computer without problems etc... If so, than this will stay as my offside remote Backup .

I will let you know if anything new happens