Yes I have ssh over port 55 accessible.
The container has a port opening on 8222 and is accessible over browser and RDP to windows connection also works but why the ssh connection not.
sshd is running and it will connect to any pc in the network but not to my guacamole container. I have checked username password, everything is correct. I mean my server is also in the network so I should not have to open ssh over a remote connection.
I have set up a guacamole container and want to connect via ssh to a raspberry pi 4 with adguard on it. It doesn't work and when I try to understand why I get other problems.
So my guacamole container is reachable by my host server (I can ping the container) and everything on my server. My server can reach other devices over the network and ping works.
When I try to ping my Pi with adguard my Pi is reachable.
When I now try to ping my guacamole container on the server from my Pi with adguard in my network via the container ip 172.18.0.2 or via the server IP with port 192.168.xxx.xx:8222 it is not reachable (100% packet loss). I can reach the guacamole container over 192.168.xxx.xx:8222 in browser but I cannot ping the container and ssh also won't connect.
I have looked into the firewall rules, but I haven't changed anything from the default. How am I able to reach my guacamole container? I have searched many tutorials, guides and posts, but I haven't got any idea on why it is not working.
any ideas?
Hello all,
does someone have experience with custom locations in Reverse Proxy Manager?
Reason being that I want to secure my wordpress container and I defined a custom location on the UI like this:
forum.openmediavault.org/wsc/index.php?attachment/33010/
I want to change the URL to something else to hide the login page. The problem is that it does not work and denies all IPs but I don't know why. It should work like this, or am I wrong?
Can someone guide me or has some experience?
Results may vary based on the NIC driver. Turn off WOL and see if that helps. If it does, then you know it's WOL and you need a software work around. FWIW, your shutdown plugin doesn't seem to be doing anything wrong, it *should* be working right now... but isn't :-/. Turn off WOL
Sorry for the late update, but I tested a few things up until now.
The plugin now works, I tuned a few settings what kept my machine awake and I have played with WOL. Something in my network seems to keep waking up my machine. Does someone know a way of how to determine what in my network keeps waking up my machine?
It is a bit annoying that I cannot use WOL otherwise.
The autoshutdown plugin shuts down and wakes up my machine at my set times but when I for some reason want to restart or shutdown and restart my machine I cannot do it because I cannot use WOL on my router
Do you have Wake-On-LAN enabled (WOL)? I used WOL a couple years ago and it would randomly wake the computer based on whatever the router was doing.
Do you have something connected to the PSU_ON/Power switch? I use small MCU's to boot a couple computers and without a pullup it will be left floating and boot the computer at random.
Is the system really shutting down or is it hibernating?
Observations are that it appears intermittently off for durations of 4:51 minutes, 4:59 minutes and 13:41 minutes. These 3 happen within ~32 minutes of each other, with the first "Shutdown issued" at 01:54:28 and the last at 02:16:39. There's also a gap of nearly 9 hours that starts at 02:37:11 and lasts until 11:29:59.
Yes, I am using WOL. Why would something wake the NAS up. Is there a way to prevent this?
The system "should" really shut down, but last night it didn't. After I noticed the system is not shutting down as I want, I manually shut it down and pulled out the power plug.
The 9h gap is because I pulled out the plug.
Is there a way of adjusting the settings that the NAS is shutdown after 23:00 (except for certain activity at my cloud port) and an automatic wake up at 9:00?
I have looked in the log, and it says before I turned of the IP range and just look for sockets, there were IPs still online but before last night I tried to turn the IP range of and just let it look for sockets but the NAS still turned on.
I also didn't really find a reason it stood wake. Based on the log it did shut down, but it also woke up again, but I didn't really see the server was off last night. It was still on, so why it says it did shut down.
Since I tried to configure the autoshutdown plugin in OMV, my NAS won't shut down and also randomly starts um again after I manually shut down the NAS.
For the shutdown thing, I probably didn't configure the plugin properly but why the NAS is randomly starting up after sutdown and not only on my forced wake up time?
Thanks, I will try that 
Thanks for your reply. I mean to use the graphics card by for example jellyfin for hardware accleration or other docker containers like kasm or guacamole.
I am able to add the device to the docker, but I don't know if the container is really using the card.
Hello guys,
I finally upgraded my hardware with an old PC with an AMD HD6750 graphics card in it. Do I need to setup the graphic cards drivers or does apt-get upgrade automatically fetch hardware drivers? Because based of the instructions on AMD it seems to be a pain to install those drivers.
What is it? An extra pool? The pool doesn't mount?
I mean the before mentioned behaviour, that the old PoolA still sometimes shows up after boot and then PoolB is not mounting of course.
No. A parity drive from snapraid is just a normal filesystem with a parity file on it.
Okay that is good, so one possibility less
I think then I can only watch over that behaviour. If it occurs the next time after boot, what logs or data should I check or save to analyse the reason behind it? I guess omv syslog anything else or special?
you could have a leftover entry in the mntent section of the database or less likely, a leftover mount file in /etc/systemd/system/. If you are only uninstalling the plugin for fresh installs, neither of these should be a problem.
mhm.. I looked a both locations but there was nothing I could find. No leftover entry, and i also only found my PoolB entry in the sytemd location you mentioned.
Is there a possibility an old parity drive could mix up OMV?
Because when I removed the snapraid configuration I left the old parity drive not mounted bit still connected to the system. I didn't had the time to clean it.
you could have a leftover entry in the mntent section of the database or less likely, a leftover mount file in /etc/systemd/system/. If you are only uninstalling the plugin for fresh installs, neither of these should be a problem.
Maybe yeah. I will try that tomorrow and check if there is any leftover data, because there has to be a reason if PoolA still sometimes appears.
sudo omv-showkey mergerfs But if there was "leftover" settings, then the pool would show up in the plugin. The plugin shows everything in the database not just things mounted.
I would highly recommend to stop uninstalling the plugin to "fix" things. I don't ever test this and don't want to.
Ah okey. Interestingly as you said only the PoolB is configured.
I want to mention that i only ever reinstalled mergerfs after a fresh new OMV installaton. The only exception was one time by accident when reconfiguring my NAS from snapraid mergerfs combi to just mergerfs. That's when I created PoolB because I had to create a new pool.
sudo omv-showkey mergerfsonly showed me the new PoolB. Is there any other way to check how mergerfs still sometimes creates the old pool?
Does someone know where the mergerfs plugin in OMV stores its configuration data?
Reason being is, that I want to check a behavior. I previously when my server was messed up with snapraid and mergerfs plugin I mentioned in this and previous topics, created a pool named for example PoolA. Then when I removed the snapraid configuration and just used mergerfs, until I build a new NAS, I named the new pool PoolB. But in between, I also uninstalled and reinstalled the mergerfs plugin. Sometimes I noticed when I restart OMV that the pool is not mounted and of course I manually mount it then. But sometimes it won't mount and throws errors. When I look into the "/srv/mergerfs/" there should be only PoolB but there still is PoolA from the previous config. Even tough I deleted it, and it is fine for a while, but sometimes mergerfs still shows the old PoolA folder and I have to delete it. Maybe this is also contributing to some drive missing issues.
Any ideas on how I can check, if mergerfs still has some old settings stored somewhere and I then how can remove them?
The docker-compose plugin.. it basically lets you run docker-compose from the OMV webUI.. but in additiona to that, it saves your compose files in a specified folder.
Ah so it is like docker-compose on portainer but with a additional save in another folder
interesting, i have to try that
Interesting, so if i understand it correctly, if i use the omv compose plugin it saves the data in the docker root folder? Or am i able to save the config data somewhere else like when i use compose in portainer and i set the config and container files to be in whatever directory i choose.
For example i create a docker compose for jellyfin and i put the path for the config at my prefered place but the rest of the container files are in the docker root folder.
What is the difference when i use the compose plugin?
Display MoreGreat.
Can you now access Portainer as if it was new?You'll need to create a user and password again.
If you want to test it, just click "install" on OMV GUI.It should come up clean.
When there's an update to Portainer, all it takes is to click "Install" and it will update over the previous version.
I can confirm it works now. After successful installation, it took me to the web ui as if it was a total fresh install. I tested to upload my backup and it worked.
My docker containers work now, finally...thank god
I previously did it exactly as you said. I just updated portainer over the "install" button on extras. I did update it always that way but seems like at the last update something went wrong.
Luckily you were there to fix it 🙈
I already could see my server to be rebuild from scratch...
Okey lessons learned. If someday in the future a update kills portainer then i uninstall it over extras, remove the data over extras and create the portainer_data folder manually with root permission.
Thanks again🙏🏻
s the docker folder living on a merged pool??? Or is it only on the root of the OS?
It is 100% on the boot drive aka SD-card as it always was
mkdir /var/lib/docker/volumes/portainer_data #This will make the folder owned by root
ok i created the folder now this way
ls -al /var/lib/docker/volumes To list the folders again to check if it need changes to owner:users
root@meinnas:~# ls -al /var/lib/docker/volumes
total 80
drwx-----x 12 root root 4096 Dec 21 17:32 .
drwx--x--- 13 root root 4096 Dec 21 15:36 ..
drwx-----x 3 root root 4096 Apr 19 2022 07a52b2096960f4f3e88c4908c0a9f1bac0884ea72f713fb6ece6b111bf5d1e6
drwx-----x 3 root root 4096 Sep 22 00:57 2214dac2c6eaa5cdddaf1161bfab9f97e3ccb8bc95dc5df0a5311aacb9338f62
drwx-----x 3 root root 4096 Dec 21 09:49 480a8ca7aa2fc0922b1ec81bd0bc933498eddc3d2d694c79be6441caa39fb78d
brw------- 1 root root 179, 2 Dec 21 15:37 backingFsBlockDev
drwx-----x 3 root root 4096 Nov 2 12:17 compose_opdata
drwx-----x 3 root root 4096 Nov 2 12:17 compose_pgdata
drwx-----x 3 root root 4096 Sep 22 00:53 kasm_db_1.11.0
-rw------- 1 root root 65536 Dec 21 15:37 metadata.db
drwx-----x 3 root root 4096 Nov 3 15:30 openproject-ce_pg-data
drwx-----x 3 root root 4096 Nov 3 15:57 openproject_raspi_pg-data
drwxr-xr-x 2 root root 4096 Dec 21 17:32 portainer_data
drwx-----x 3 root root 4096 Apr 19 2022 synapse-dataIt is definitely root now.
It faild again but now i wanted to make sure extras can remove data, so i removed the data over extras again and confirmed that omv can delete the folder.
Now i reinstalled again and it worked, i can get to the web ui now. But i am still checking for errors
Docker storage :: /var/lib/docker
Agent port:: 8000
Web port:: 9000
Yacht port:: 8001
ee:: 0
image:: portainer/portainer-ce
Enable TLS:: 0
arch :: arm64
option :: portainer
state :: install
extras :: 6.1.1
DNS OK.
No portainer containers or images to remove.
Creating portainer volume ...
portainer_data
Pulling portainer/portainer-ce ...
Using default tag: latest
latest: Pulling from portainer/portainer-ce
772227786281: Pulling fs layer
96fd13befc87: Pulling fs layer
9feedfe952b7: Pulling fs layer
2b0b05213b47: Pulling fs layer
2b0b05213b47: Waiting
96fd13befc87: Verifying Checksum
96fd13befc87: Download complete
772227786281: Verifying Checksum
772227786281: Download complete
772227786281: Pull complete
2b0b05213b47: Verifying Checksum
2b0b05213b47: Download complete
96fd13befc87: Pull complete
9feedfe952b7: Verifying Checksum
9feedfe952b7: Download complete
9feedfe952b7: Pull complete
2b0b05213b47: Pull complete
Digest: sha256:f7607310051ee21f58f99d7b7f7878a6a49d4850422d88a31f8c61c248bbc3a4
Status: Downloaded newer image for portainer/portainer-ce:latest
docker.io/portainer/portainer-ce:latest
Starting portainer/portainer-ce ...
198eb9d30c2c5e0a7612366017fe22dccbdd228cd671ec3775a623b761058567
END OF LINE