Thanks for the hints, this definitely helped, however it did not solve the issue.
What i did:
omv-firstaid
the omv port from 80 to 8081.ss -ltn
that this change was successful and i see the listening port 80 vanished, while this now popped up:State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 511 0.0.0.0:8081 0.0.0.0:*
curl http://mylocalip:8081/
and it works, i get the html backssh -L 8081:localhost:8081 pi@raspberrypi.local
and i did not get any errors this time. However when i open the local url in the browser i get a connection reset and my terminal shows me channel 3: open failed: administratively prohibited: open failed
. However this just says that TcPForwarding is disabled, which is fine, so that tunneling issue should not be the main problem, i assume.The jbod idea sounds good to explore further, as it tha home server and storage would be separated. However it would add an additional device to the power bill.
However i don’t need the full amount of all disks at all times. If i’d want to unplug via shell script, i’d need to plug it manually in person back in for storing things. I actually do not need it running all the time, as the home server ssd can cache most of what i need recently in access. The jbod is then more an archive.
i’m mainly looking for a way to power down the inexpensive hdd’s. I could use the raspberry pi as the jbod controller, but it does not properly support wake on lan, so thats also not an option
The issue was much more straightforward than i thought. It seems sometimes thinking of too complex issues will hinder finding the easiest cause - the local forewall on the pi was blocking it / had no explcite allow.
To check i did:
sudo ufw status verbose
There was only port 22
I added the new port as Allow Port 8081:
sudo ufw allow 8081
And it works now! Thanks for all the tipps that pointed me in the right direction!