Beiträge von ohiskyy

Zitat von auanasgheps

0.13, which works

macom what about you?

Zitat von auanasgheps

Install fatrace

After installing via app-get install fatrace it gives me Cannot initialize fanotify: Invalid argument

I've found out this might be related with the fact that debian repo has 0.13 version and the latetest one is 0.15

However, I'm unable to install it from tar.

Have you faced the same issues?

Hi,

I'm running OMV 5.5 on Transformer NAS (rockchip 64)

As I remember it, ever since the install my disk had issues with spin down. As a result, I practically cannot use my system due to constant ups and downs. (Note, previously I had OMV4 and it didn't have such problem)

I've tried installing autoshutdown from extras and also the newest hd-idle script from auanasgheps thread but none worked

Pls help!

Hi,

I've got popcorn hour tranformer (ROCK64) running .... some Android image. I decided to convert it to OMV 5 NAS, so basically I followed this guide and everything worked flawlessly, I was able to flash OMV and login to GUI...with system booting from SD-card.

Now I want to flash it to eMMC and enjoy the further setup And then I realised there's nothing in that guide about burning to eMMC.

So, is there any other tutorial or set of commands to do this?

I've found this topic with nand-sata-install. But I don't want to brick anything so asking in advance!

Besides, does it really aplly to my case as the hard drive is detached?

This guide about nand-sata-install seems to describe a different scenario..

Zitat von KM0201

Are you comfortable with Docker-Compose?

No, not exactly. Guided mode only

Zitat von Morlan

So the issue is host likely in the .conf files or your nextcloud config.php

Any suggestions where to look?

Zitat von KM0201

Have you tried just following the old guide?

Which exactly?
I tried to follow technodad's guide bilion of years ago, never succeeded

Hi,
Here is the full lof of letsenc logs attached

The next step in the guide is opening up the link, but it chrome gives connection refused error
What to do next?

* Popcorn Hour Transformer, which is rock64 as I guess

However, still can't get it working:
Nextcloud created, but I cannot access it, crome gives "connection refused error:(

Port-forwarding for 443 and 80 is set for BOTH and enabled

@Morlan the solution was to change DHLEVEL in GUI for 1024
for some reason, setting/commenting this line in config didn't work

Zitat von pug_ster

/srv/dev-disk-by-label-disk1/appdata/letsencrypt/nginx/proxy-confs

Thanks!
Made an edit, now it looks like this

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_nextcloud nextcloud;
        proxy_max_temp_file_size 1024m;
        proxy_pass https://$upstream_nextcloud:443;
    }
}

Still getting the same error, even after full restart

@Morlan @pug_ster
I don't seem to have nextcloud.subfolder.conf created...?
(All steps done in accordance with the guide though)

Also, I noticed this time I tried to follow the guide from the beginning once again, it gives me waaay fewer parametres in GUI

And this is the content of

/srv/dev-disk-by-label-disk1/appdata/nextcloud/config/www/nextcloud/config/config.php

'trusted_proxies' =>
  array (
    0 => 'letsencrypt',
  ),
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://ohiskyy.duckdns.org/nextcloud',
  'trusted_domains' =>
  array (
    0 => 'ohiskyy.duckdns.org:443',
  ),


  ),

Trying to set up Popcorn hour transformer on OMV4 (rock64)

Keep getting

"proxy_max_temp_file_size" directive invalid value in /config/nginx/proxy-confs/nextcloud.subfolder.conf:33

What am I doing wrong?

My config:

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Moscow  #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
#    ports: # uncomment this and the next line if you want to bypass the proxy
#      - 450:443
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=mariadbpassword_TRY  #change password
      - TZ=Europe/Moscow #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Moscow # change Time Zone if needed
      - URL=ohiskyy.duckdns.org  #insert your domain name - yourdomain.url
      - SUBDOMAINS=www,
      - VALIDATION=http
      - EMAIL=ohiskyy@gmail.com # define email; required to renew certificate
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/letsencrypt:/config  #/srv/dev-disk-by-label-disk1 needs to be adjusted
    ports:
      - 444:443
      - 81:80
    restart: unless-stopped

I was setting up my NAS under instructions in gorgeous @TechnoDadLife channel, but faced problems while trying to set up docker containers. Namely, the output for

docker logs -f letsencrypt

was

standard_init_linux.go:207: exec user process caused "exec format error"

I had the same story when trying to setup nextcloud...

Google showed that this error has something to do with wrong docker image:
Indeed, my popcorn hour build is aarch64, but omv docker installs as linux/arm

As I understand, there is a way to install docker for aarch64 and get it running ARM64 , but docker-gui package doesn't support aarch64..?

Any ideas/instruction how to get things working?