I don't know, sorry.
So yes it was the cause of alot of my problems, i rebuilt OMV and all containers including Nextcloud (incl shared folder) are working perfectly.
Thank you for your help
I don't know, sorry.
So yes it was the cause of alot of my problems, i rebuilt OMV and all containers including Nextcloud (incl shared folder) are working perfectly.
Thank you for your help
To add insult to injury, i think the builds i did last night were fine, i only say that as im logged in to my PI now and can go to the OMV log in page fine, did the same on my phone but for some reason my Chrome browser would not let me go to it. Cleared my history/site settings and chace.....guess what everything perfectly now ........im going back to sleep
Thank you both for your help, no it's not hard running a script. I'm just very impatient
Start here for the pi eeprom
Ah so it appears since I re-did the flash it would have put the firmware back to factory default? I think.
I'm in and installing OMV again see how this works. I miss being able to use the prebuilt (iso) of OMV found it so much easier.
Display MoreIf you can still get into your pi now then grab the mac address for the network adaptor you are using (wifi, ethernet).
Then set the static dhcp reservation in your dhcp server. If you do the reservation in your dhcp server there's no need to set it on the pi itself.
Once the pi is able to pull the static IP from the dhcp server there should be no issue installing omv via ssh. If you are more comfortable with a keyboard and monitor there's nothing wrong with that either.
I have updated all my pi4s with eeprom code and boot config options that shutdown the pi to a low power state but it still requires me to power cycle for a reboot. If yours is hanging like that I would suggest checking your firmware before proceeding with anything else.
How do I check the Firmware, I've only ever done the normal update/upgrades haven't tried the SSD boot which I know evolve change something in the firmware
Display MoreI would suggest setting a static IP to your raspberry pi based on its MAC address. If you can do this through your router or whatever is your dhcp server that would be the best route.
Then redo the installation.
I found the easiest way to install omv5 onto a pi4 is to install debian first as an sdcard flashed image (or usb or whatever boot media you choose) and then run the omv install script.
With a static IP address when the ssh session times out just restart it (ssh session) after 20 seconds or so and it should be done.
I would still do the whole raspi-config steps before actuallly installing omv5.
Also noticed this last night my PI hangs like this
I have to physically unplug it and then plug it back in
Display MoreI would suggest setting a static IP to your raspberry pi based on its MAC address. If you can do this through your router or whatever is your dhcp server that would be the best route.
Then redo the installation.
I found the easiest way to install omv5 onto a pi4 is to install debian first as an sdcard flashed image (or usb or whatever boot media you choose) and then run the omv install script.
With a static IP address when the ssh session times out just restart it (ssh session) after 20 seconds or so and it should be done.
I would still do the whole raspi-config steps before actuallly installing omv5.
Hi,
Thank you for your reply, so how does this sound
Freash install of Raspbian os once set up then set a static IP inside Raspbian and also onmy router, instead of installing OMV via SSH i will connect up the PI to a monitor and keyoboard and then install the code you gave?
Hi,
So i have tried building OMV5 on raspberry PI 4 2GB twice now, once using a Tech Dad install video and then using a DB tech video both instances it will reach the DHCP reset line and just hang for ages (i waited about 30 mintues) but no message of disconnection or completation. I then open a new SSH window and reboot but when i try and go to the OMV page to log in it says it cannot connect and when i check the install of omv i get this
im assuming this mean the install of OMV was not done correctly?
Please could someone advised installation that will work.
It does not matter which client you use. This is about Linux permissions.
The files written by your Nextcloud container will be owned by the user you specified with the PUID and PGID. And this user needs write permissions on the folders where your Nextcloud files are stored.
Ah OK that makes sense now, just out of curiosity not sure why but recently my OMV has been plagued with quota errors while either mounting, unmounting, formating drives even though I never turned on quotas and even if I turn them off using th sudo command they come back on with in 5-10 minutes. Could this mean my OMV install is faulty and causing permission issue amoungest other things?
If you used the puid and pgid is the pi Idee its best To habe the files owned by pi
The PGID and PUID is for the PI user, I'm trying to upload files from my phone (Android OS
Then you have to check if the user who is running in the container (specified by PUID/PGID) has write access to your external storage.
When I was doing the docker compose I was logged into ssh using PI and used the PI's PUID/PGID. How would I check which user is running the container?
Oh sorry yes from linuxserver
Which Nextcloud image are you using now?
My next version is Nextcloud 19.0.3, also while checking this It came up with this
Shiuld I be worried?
Yes. And in Nextcloud you just use the path /Test
Perfect Thank you I have the folder now mounted in Next cloud.
It won't let me upload any files to it though. Is permission level 750 the correct one?
You need to add the external folder as a volume (bind mount) to your docker container
Like this?
Ah sorry didnt read his post properly
Hi, So after far to long i have manged to get Nextcloud installed on docker (OMV5/Raspbeery PI) and i think its working here is a screen grab of the WebGUI (just incase im wrong)
i have noticed the circule at the top keeps spining but nothing happens, anyway my main issue is im trying to mount and external drive so i do the following
Enable "External Storages" from App
Then using SSH i run these commands
sudo chown -R www-data:www-data /srv/dev-disk-by-label-Test
sudo chmod -R 0750 /srv/dev-disk-by-label-Test
Then back in next cloud i go to settings>external storage (bottom option)
as the folder details
click on the tick and then go back to main Nextcloud page, the mounted drive is not here?
i clic on External stroages (left side) and the drive/folder is there
but when i click on it takes me back to the main page
What am i doing wrong? Can someone help please?
I would advise you start over and use this guide [How-To] Nextcloud with Letsencrypt using OMV and docker-compose
Thank you for your help i have got it up and running now (i think) i need to create a new post as a new issue has come up with external storage. there has to be an easier alternative to nextcloud. All i want a is to be able to securely sync photos from my phone (like dropbox and Onecloud)
Those logs all look fine!
The error message means, that the swag container does not correctly forward your request to the Nextcloud container. Can you show your nextcloud.subdomain.conf ?
So i made a back up of the ncloud78.duckdns.org and modded a few lines removed the "#" and added in the DNS but now im getting this error
but line 15 doesnt not have trusted_proxies
Should i add it and how? or just restore the back up?
Those logs all look fine!
The error message means, that the swag container does not correctly forward your request to the Nextcloud container. Can you show your nextcloud.subdomain.conf ?
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "swag", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['swag'],
# 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
# 'overwritehost' => 'nextcloud.your-domain.com',
# 'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'nextcloud.your-domain.com',
# ),
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name nextcloud.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app nextcloud;
set $upstream_port 443;
set $upstream_proto https;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
proxy_max_temp_file_size 1024m;
}
}