Posts by Frepke

Did you use the correct tag?

Quote from votdev

Hmmm, i expected that the response is a 401. When exactly does this error occur? Can i easily reproduce the issue on my test installation? What do i have to do then?

It happens all the time. When I import an existing symlink and cancel that operation, the problem is gone.

When I open a new tab and go to OMV, scrolling isn't possible again (symlinks).

Quote from votdev

The Workbench page was only an example how to get the information from the browser dev tools. You should do the same thing as before to create the error and then post the data displayed in the dev tools.

Oops...

Then the Payload is:

{service: "FolderBrowser", method: "get",…}
method: "get"
options: null
params: {uuid: "79684322-3eac-11ea-a974-63a080abab18", type: "mntent", path: "/"}
service: "FolderBrowser"

and the Response is:

{"response":["lib32","sys","dev","sbin","export","usr","etc","hdd","hdd2","libx32","bin","proc","dc","lib","opt","tmp","boot","root","lost+found","run","ssd","var","media","dockercfg","mnt","lib64","home","srv"],"error":null}

Quote from votdev

Something like this:

The Payload gives me this:

{service: "WebGui", method: "getSettings", params: null, options: null}
method: "getSettings"
options: null
params: null
service: "WebGui"

The response gives:

{"response":{"port":81,"enablessl":false,"sslport":443,"forcesslonly":false,"sslcertificateref":"","timeout":60},"error":null}

I hope this helps.

kr.,

Frepke

Quote from votdev

Without haviong more information i can only say that the RPC can not be executed because of invalid privileges.

Having more information about the RPC would be helpful; running browser dev tools and enabling network analysis would give the required information.

What information do you need from the dev tools, maybe this?

{"response":null,"error":{"code":0,"message":"Failed to get the RPC parameters.","trace":"OMV\\Rpc\\Proxy\\Exception: Failed to get the RPC parameters. in \/usr\/share\/php\/openmediavault\/rpc\/proxy\/json.inc:47\nStack trace:\n#0 \/var\/www\/openmediavault\/rpc.php(45): OMV\\Rpc\\Proxy\\Json->handle()\n#1 {main}"}}

Quote from gderf

I think some voodoo might be needed

Also, whatever triggers it here seems to involve only leaving OMV for a while and coming back. And the fix is also reliable, so far it has worked every time.

When the problem occurs, I've got an error in my console:

When I press import and then cancel, the problem is also gone.

Quote from gderf

Thanks you for this suggestion. It worked!

Edit:

Coming back to it a bit later it no longer works - no scrolling. So what I did was to reimport an already imported link. This threw up an error but brought back the scrolling capability.

Tried it on my system, and scrolling is still working. Tried it in a new tab and scrolling is broken again , the reimport of an already imported link let it scroll again.

After upgrading to omv-extras 6.0.5 my rootdrive was missing in the File System Status on the dashboard.
I uninstalled and re-installed the plugin openmediavault-sharerootfs 6.0-2 and my root drive was visible again in the dashboard.

Now my symlink plugin gave me an error. Uninstalled and reinstalled the symlink-plugin, imported existing symlinks and tried to make a new link. Now all is scrollable again as it should

Maybe this can help you

kr.,

Frepke

Quote from gderf

Well, sure I run browser extensions. I guess I'll have to shut them off a few at a time to see which one is causing it.

Edit:

I disabled all extensions in Chrome and it still will not work. I also tried with Firefox and Safari on my iPad. No joy there either.

Same problem for me

Just info

I did the omv-release-upgrade myself, reinstalled docker and omv-extras.

No problems whatsoever.

Quote from noiro

Upgraded 5 to 6

uninstalled and installed the omv-extras with the command

Code

https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install

in 2 out of my 3 systems I still still see omv-extras 5....

Cleared cache (many times) tried with 3 different browsers but the same.

any ideas?

Display More

Try: wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

You can set login credentials in cloudcommander, just press F10

Quote from Zoki

If you do not have the command line you started the transmission with you can go to the cli and

docker inspect transmission-openvpn

If you are only interested in the volumes (for backup) use

docker transmission-openvpn | jq ".[0].Mounts"

Display More

2nd command should be docker inspect transmission-openvpn | jq ".[0].Mounts"

I believe this settings are stored in cookies, so maybe you've to accept cookies in your browser.

Quote from raulfg3

I use crlt-F5 to clear cache and still do not show the same as yours.

I use Chrome, what explorer do you use?

I use Edge at the moment, but I did a quick test with Firefox, Chrome on a Windows machine and Safari on a Macbook and iPhone.

All with the same result.

Quote from raulfg3

kernell plugin do not work as expected, , once installed, I can use the install proxmox kernel, ok, but is not selected as default kernell, I reboot and always use 5.14 ( actual kernell), not 5.11.22 (avtual proxmox kernell) if go to kernel tab, not possible to select desired kernel to use, see screen capture:

And one suggest, once the proxmox kernell are installed using his button on proxmox tab, perhaps is good to show some type of info on this tab , eg: the version of kernell instlled, I say it because no info is show and you can still use the install button ( none hapens on that case because on cli show that the kernell is installed and no packages are selected to install, but can be avoid if you see in tab that proxmox is installed.

PD: And same for other tabs, is good to see in tab that ISOs are downloaded and rady to use.

Display More

Hi raulfg3,

My comment doesn't help you but is just for information.

For me the plugin works as expected, all the available kernels are selectable and possible set as default and also used after reboot.

Quote from liv

No Stacks tab contains an empty list.

Sorry, I can't help you with recovering a backup

The easiest way for me should be to setup the Stacks in Portainer from scratch (hope you have a backup from the settings) or setup everything with .yml files (those textfiles are easy to duplicate for a backup).

Maybe (and I hope) someone else can help you recovering you lost containers.

Quote from liv

The problem is that I have restored folders, but containers don't appear in the list on Portainer and I cannot start them.

Right now I'm looking for a way to update the list in Portainer to reflect the containers in the filesystem...

Aren't they visible in the Stacks tab in Portainer?

Quote from liv

I used Portainer to setup and run them.

Then you can run them again from within Portainer.

Quote from liv

I've lost containers and volumes. Browsing on the backup repository I identified and copied back volumes and containers from mirrored /var/lib/docker, so files are back again. But I still cannot find them in Portainer GUI, so I'm still looking for a way to rescan objects from there.

Using "docker-compose up -d /var/lib/docker/containers/xxx" will relink them again to docker?

Using docker-compose up -d should link to the location where you stored your .yml files.

But how do you setup/run your containers , through Portainer or CLI or ...?