I to use the Binhex qbittorent container, and looked on the binhex forums, and the answer is to comment out the dns line in your wg0.conf file.
I use Windscribe and it worked, and on the forum a number of other VPN providers worked.
You could also try below to roll back.
binhex/arch-qbittorrentvpn:5.1.1-1-01 Plus I believe that binhex has/is rolling out a new image that should contain a fix
To create a new user was also my idea now. To which groups should this user belong and to which folders should it have access rights?
This is my settings for user trythat.
_ssh, adm, audio, cdrom, cterm, dip, docker, floppy, kvm, netdev, openmediavault-admin, plugdev, sudo, trythat, users, videoBut I did this a while ago, I realize some of these are not needed. Default OMV groups is 'users', but this is a minimum I would think.
If using ssh - _ssh
if using docker - docker
if using kvm - kvm
if using sudo - sudo
username - username
if using cterm - cterm
default group - users
The following are my linux laptop user groups, as default,
uid=1000(trythat) gid=1000(trythat) groups=1000(trythat),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),106(netdev),110(lpadmin),115(bluetooth),123(scanner)So I suppose this might be a starting point until someone comes up with a better answer.
Did you see the container term dashboard widget? It lists the containers with a link the terminal in a dashboard widget.
Yes, I could of worded that a little better, what I meant to get over was, that whatever you're working on whether in the docker or lxc tab, or just the host shell, you can use which ever you prefer, plus I like being able to jump straight into the container of choice when using compose or kvm.
I think it's very good, Personally I'd like to have the choice to auto login, but I understand why you've gone down the login route you have. As I use Bitwarden I prefer the login popup rather than the way WeTTY things. (Yes, as others have pointed out to me, I can auto login from WeTTY in a docker container, but I believe WeTTY on the Dashboard uses Podman, and I've not really looked to see where the config files are stored, if there are any config files.)
Personally I don't expect to use ssh that much going forward, unless the cli you've used can't do something that the debian cli can do.
A very nice addition to OMV all round!!
For users who were using the 'exec terminal' function in the compose plugin, I've just checked. Now to use compose and kvm plugin 'exec terminal' function, you only need to have 'cterm' group added to your user, the same as in the main 'CTerm' plugin.
You can remove the 'dockerterm' from your groups if you wish.
Like the name, and a very nice way of doing it. I do like how you can now access the shell from compose, kvm and the main interface both of all situations.
Because it was easy to add without duplicating a ton of code.
That's what I thought and I don't blame you for doing it that way.
It would need to be broken out into a separate plugin for that. I still haven't decided if I want to do that or not. I probably will but even then, there will be links to lxc container terminal from the kvm plugin and already is links to the docker container terminal from the compose plugin. Please just be patient. I have ideas in my head and want to develop them as I have time. I will let people know when I am open to ideas on this.
That's more than a fair answer, in fact that would be the best of all worlds.
TBH I always feel a little guilty when asking for something extra, but to me, most developers do think the same ideas as I might, but I've always thought if no-one asks, then it shows no one really cares and yes sometimes the program is just right as it is.
I never assume anything I ask for will be done, I'm just grateful that developers put the time and effort in, if my suggestion gets added it's a bonus for me and hopefully for other users.
Going forward I'll wait to see if you or other developers ask for suggestions.
Thanks again though.
I've just seen that Exec function has lxc added to the container list, which is nice.
I probably have a rough answer to what I'm asking, but why is lxc accessed from within the compose plugin? I assume because that's where the exec function is already working.
But would it not be better to have it as separate one line button on the side service tab, like 'WeTTY', something like 'Exec', or 'Exec Container', then accessing both docker and lxc from the same container menu seems to me make better sense to me?
As the thread the 'Adding a terminal (cli) to OMV in general' has been locked and ryecoaaron has just said 'it was relatively easy to add a host shell to the compose plugin's exec terminal' and allowed access to the host OS from the container list..
I'd like to thank him for his effort!!!
It works well, I really hope ryecoaaron might consider adding this option as I've outlined in the opening message. But as I received some quite negative comments, I don't blame him leaving it where it is.
Thanks ryecoaaron.
I do use ssh with keys, but that wasn't the point.
Any way I've started another thread about using WeTTY, where I did a bit more thinking on the matter first. But it does look as though I'm in the minority about wanting shell access from the main menu of OMV like other NAS and Hypervisors - unfortunately.
But thats how it goes, you have an idea, and sometimes you're the only one who likes it.
The problem is you can go to the wetty interface without even logging into the omv web interface. That is one reason why it has a separate login.
I understand that. That could stay the same, you would only be able to auto login when using the button from within OMV.
you could just bookmark the wetty url.
I know, but it's still not within the OMV Eco system, I'd prefer and think its' a better solution to use a button from the main interface.
But if no-one else agrees, then its fine.I'll just carry on as I do now. It's not something that will stop me from using OMV.
As WeTTY is available as an OMV plugin, which is handy, and also we now have cli/exec access in the Compose plugin.
I've wanted for some time a better way of accessing a shell, now I know just because other NAS and Hypervisors have certain feature doesn't mean that OMV always needs them. But the more I see Truenas, Unraid, Proxmox etc have a 1 click access to a shell, which logs in as the currant user.
So I'd like to suggest, that the WeTTY/Open UI button be added to the side menu below the Dashboard button AND/OR the main notification/power menu bar(my preference, as not everyone has the menu displayed). It could be renamed, perhaps to 'Terminal' or 'CLI' or just a icon of a terminal.
I would also like to see more options in the WeTTY settings page -
Add A checkbox option to login automatically (as I now know about, as I was lectured about recently), so user and password input would be saved.
Add A checkbox option to login automatically as currant user. (My preferred option)
I know people will say that login automatically is insecure, but someone already has access to the OMV dashboard, you're already in trouble.
Unfortunately I severely lack programming skills, but to me, it doesn't look as though much would need to be added - A button and a couple more settings in the WeTTY settings, if users didn't install WeTTY then nothing would change.
This is just a suggestion, if no OMV user agrees or the developers don't think this is worth it, then I'm fine with that, but I really do think it would be a useful and great addition to getting shell access to OMV.
That's why.
Meaning what? Because I'd like an easier way of accessing a shell from within OMV. I'm having another look at this going forward.
The point of wetty is to get a console to your host without a vpn or some port forwarding. You simply connect to it via http, which is already exposed to the internet.
And passwords are there for a reason. Nonetheless wetty **is** able to auto-login.
I don't expose to the internet.
But I suppose what it comes down to, is that I don't like wetty, so don't use it. If everyone else is happy using it, great, carry on, there is very rarely just one way of doing something with computing.
I'm ok with using ssh, it was just an idea. Not sure why people are getting so up tight about it.
The exec function of the compose plugin doesn't auto login either. And while the code could be adapted to the system, it would just be recreating wetty and not as good as wetty. I created the exec terminal for the compose plugin because nothing really existed that would work with the plugin.
Fair enough, I'll stick to ssh then.
Display Moreyou can configure wetty docker to autologon.
example:
CodeDisplay Moreservices: wetty: image: wettyoss/wetty:latest container_name: wetty cap_add: - NET_ADMIN environment: - SSHHOST=$SSHHOST - SSHPORT=$SSHPORT - SSHUSER=root - BASE=/ ports: - 3000:3000 restart: unless-stoppedmore config:
Nice and thanks, didn't realise that. But you can't do that from the wetty plugin, so would need a container rather than a button where I'd like a button added, so sshing with keys would still be easier.
But thanks again.
It's already possible. Use wetty plugin or install a wetty docker from examples.
Next time check the forum first.
I know wetty is available!
But it doesn't do what I was hoping for. In fact it's just as quick to use ssh, because of the number of clicks you need to access wetty, you still have to enter username and password, I would like a separate button as I said, and to be auto logged in. I don't see how you can auto login with wetty unless you know better?
If ryecoaaron say's he doesn't want to or it can't be done then so be it, but I put it out there, to see if anyone else thought the same as me. I don't mind either way, but for me OMV works best when I can do most things from within OMV, such compose and now being able to exec into a container.
As the exec function is a new addition to the compose plugin and seems a big advantage over using wetty or ssh, then I thought I ask.
If you're happy with wetty, then fine carry on using it.
Now we have a cli allowing exec into docker containers.
Would it be possible to add the cli to use in OMV instead of having to ssh in?
If so, it would be nice if it was available at all times, so it could be placed in the same group as the user settings and power etc section.
I would assume it would use the currant user, and either enter at the home folder if there is one, or straight into /. It would be nice if it logged into the cli automatically as current user so no need to login as we do with compose plugin cli, also unlike how the compose plugin cli works, it would pop out a window.
To me, it looks as though the hard work has been done, but I'm not a developer, so I could and probably am talking rubbish, but if you don't ask you don't get.
dozzle must not have sh or bash available. I guess I could add another shell but that is very strange that it doesn't have sh. I guess it might not have it in the PATH and I could call /bin/sh instead. When you exec into the container normally, what do you use?
Just tested dozzle via ssh and you are correct, it doesn't seem to work with bash or sh, whether it's preceded by bin.
ryecoaaron I've looked at the compose files and made some changes, how can I get the zip file to you? I have sent files to you before, but I can't remember how 
If you don't want them, thats fine, but I was surprised at how many of them had changed.
I was running the last test version and updated this more with no errors.
