Hi,
Usually, in Debian installation, if you don't give a pass for root user, you can create another user and issue root cmds with sudo. When installing OMV, I give a pass to root user, but want to delete it, for security reasons. It is possible? And how to create another user which will have root privileges with sudo only?
Beiträge von gett
-
-
-
Another problem
I add calibre-web to my older nextcloud-mariadb-letsencrypt yml file and receive errorsCodeERROR: for letsencrypt Cannot create container for service letsencrypt: Conflict. The container name "/letsencrypt" is already in use by container "9c62da18f85 82c75b404076fa0a96c5e9e396e95a1e60fb27ac3be79dc15b4d9". You have to remove (or rename) that container to be able to reuse that name. ERROR: for mariadb Cannot create container for service mariadb: Conflict. The container name "/nextclouddb" is already in use by container "762a3e86610d2c8bb8d 4145fd4aed8fd678b4b7cebf935f985b88e3b1a14e0c7". You have to remove (or rename) that container to be able to reuse that name. ERROR: Encountered errors while bringing up the project.
-
In the docker-compose.yml you add
This. Thank you!
-
why don't you just add calibre to your existing docker-compose.yml? Then it's automatically joined in the network.
Thank you for answer.That is OK for images from linuxserver.io. But I docker-compose.yml from developer (seafile) which is not from linuxserver and want to add to my letsencrypt network.
Code
Alles anzeigenversion: '2.0' services: db: image: mariadb:10.1 container_name: seafile-mysql environment: - MYSQL_ROOT_PASSWORD=pass # Requested, set the root's password of MySQL service. - MYSQL_LOG_CONSOLE=true volumes: - /srv/dev-disk-by-label-omvdisk1/appdata/seafiledb:/var/lib/mysql # Requested, specifies the path to MySQL data persistent store. networks: - seafile-net memcached: image: memcached:1.5.6 container_name: seafile-memcached entrypoint: memcached -m 256 networks: - seafile-net seafile: image: seafileltd/seafile-mc:latest container_name: seafile ports: - "80:80" - "443:443" # If https is enabled, cancel the comment. volumes: - /srv/dev-disk-by-label-a/seafile/shared:/shared # Requested, specifies the path to Seafile data persistent store. environment: - DB_HOST=db - DB_ROOT_PASSWD=pass # Requested, the value shuold be root's password of MySQL service. - TIME_ZONE=Europe/Berlin # Optional, default is UTC. Should be uncomment and set to your local time zone. - SEAFILE_ADMIN_EMAIL=email # Specifies Seafile admin user, default is 'me@example.com'. - SEAFILE_ADMIN_PASSWORD=pass # Specifies Seafile admin password, default is 'asecret'. - SEAFILE_SERVER_LETSENCRYPT=true # Whether to use https or not. - SEAFILE_SERVER_HOSTNAME=url # Specifies your host name if https is enabled. depends_on: - db - memcached networks: - seafile-net networks: seafile-net:
-
After a generous help of this community I managed to install letsencrypt and working nextcloud and airsonic containers. I'm using docker compose for it. For future installs, what line I have to include in yml file to join new containers to letsencrypt network? For example, if letsencrypt network ID is "23b23jb23j4v2hj34vhj2v3hjv23hj421jh44j23" what line I have to insert in calibre web docker-compose.yml:
Code
Alles anzeigen--- version: "2" services: calibre-web: image: linuxserver/calibre-web container_name: calibre-web environment: - PUID=1000 - PGID=1000 - TZ=Europe/London - DOCKER_MODS=linuxserver/calibre-web:calibre volumes: - path to data:/config - path to calibre library:/books ports: - 8083:8083 restart: unless-stopped
-
join airsonic in the network of the docker container an try this conf
It's working! Thank you!EDIT 19. 01. 2020
I am on OMV 5 now, and this don't work anymore.
I am landed on nginx wellcome page
-
I install airsonic in docker. Receiving 502 Bad Gateway error. I am trying to use reverse proxy and letsencrypt to access airsonic from internet. Any help, please?
This is my airsonic.subfolder.conf, which, I'm sure, is wrong
Code
Alles anzeigen# set the CONTEXT_PATH variable to /airsonic in airsonic container. location ^~ /airsonic { proxy_pass https://my url/airsonic; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth, also customize and enable ldap.c$ #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_airsonic airsonic; proxy_pass http://$upstream_airsonic:4040;
And my docker configuration -
For the backup of my clients (Laptops) to OMV I use UrBackup
UrBackup look nice, thanks.
USB-backup plugin (uses rsync)
I considered it, too.
-
What is your opinion about backup strategies and software? I like idea of 3-2-1 backup. (Thanks macom for the link) I have one 4 TB fixed drive, one 4 TB USB drive for save backups and lot of free space on OneDrive for Business. About software, I think about Duplicati, but I read some bad thing about it. Other options is rsync. Any ideas for robust and stable backup software? Or better backup strategy?
-
Sounds like there is already another docker container with the exposed port 445. This has nothing to do with your forwards.
I think so, I try a numerous times in the past with technodad videos, but always receive errors.
-
Can you post your docker-compose file?
-
New problem:
after
sudo docker-compose up -d
I receive error
ERROR: for nextcloud Cannot start service nextcloud: driver failed programming external connectivity on endpoint nextcloud (26f5d205bceee9057b87724716c00a94a68c489fcda224810001c0046d7bad38): Error starting userland proxy: listen tcp 0.0.0.0:445: bind: address already in use
ERROR: Encountered errors while bringing up the project.Port 443 is forwarded to 445
EDIT> I try with port 443 forwarded to 444, same error
-
...
Thank you so much!
-
Are you sure about the $
Sorry, my mistake. Its $ sign from terminal. It's appdata. But my question stay: what is the line, and what to change?
-
Sorry for noob question
My appdata is in
/sharedfolders/appdata$
on disk
/dev/sdb1
disk is labeled
omvdisk1what I have to chage here:
- /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
-
duckdns.org/install.jsp
I use it on mu Raspbian (Debian 10) system, w/o OMV and it's working great. I will try to instal via CLI, thanks.
-
Is your config allright?
Well, I don't know. I follow Technodad video. In pure Debian I never have problems wih DuckDNS. Becouse of that, I want to install it from CLI, using DuckDNS own tutorial for linux cron.
-
I am sorry if this is wrong thread.
I'm trying to install DuckDNS, letsencrypt and nextcloud using technodad videos. Problem is, DuckDNS do not work reliable. Sometimes it refresh address, sometimes don't. On the other hand, on my second system, pure Debian 9 all works flawlessly. So, I am looking for a way to install DuskDNS via CLI (not docker) and connect with my docker containers. Any help, please? -
I give up setting RPi3 with 1GB NTFS drive and Transmission. If you can, I suggest to reformat drive with ext4