Any news on how to start the MySQL with correct permissions?
I suggest for more security, store the keyfile somewhere remote and load it at boot. I use 2 NAS in 2 different locations, the opposite keyfile for encryption lies on the other NAS.
Using this TPM or a local keyfile encrypts the device and/or the drive as long as the TPM is present. without VPN or the keyfile reachable, the NAS contains garbage.
docker exec -it nextcloud sudo -u abc php /config/www/nextcloud/occ db:add-missing-primary-keys
Alternatively open the console of your nextcloud container within Portainer. Change directory towards /config/www/nextcloud and perform
sudo -u abc php occ db:add-missing-primary-keys
Check on using an external database until this issue is fixed. Exporting and importing the database should be a piece of cake.
DB-configuration is done in
zm.default within the conf-folder. Create a backup of this configuration in advance. Files will be created after first unsuccessful run.
Edit: A new version was published today, still same issue.
According to this post, which has a similar issue, a new setup should do it. I'll try to use a custom user script do solve the DNS-issue at the first start of this container.
is owned by docker:docker
I checked with group 100 (users), no issue regarding group any more, but still unreachable ppa's.
Checking those manually shows availability, so there might be some name resolving issue. I tried setting up a different bridged network as well; specified my router and google as DNS, still the same thing.
995 is group docker and works fine for more than 20 other containers. I only have this issue with zoneminder.
Using dlandon/zoneminder docker, I run into a DNS issue. Starting this docker gives me this log:CodeW: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'archive.ubuntu.com',W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'archive.ubuntu.com',W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Temporary failure resolving 'archive.ubuntu.com',W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Temporary failure resolving 'security.ubuntu.com',W: Failed to fetch http://ppa.launchpad.net/iconnor/zoneminder-1.34/ubuntu/dists/bionic/InRelease Temporary failure resolving 'ppa.launchpad.net',W: Failed to fetch http://ppa.launchpad.net/jonathonf/ffmpeg-4/ubuntu/dists/bionic/InRelease Temporary failure resolving 'ppa.launchpad.net',W: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/bionic/InRelease Temporary failure resolving 'ppa.launchpad.net',Nov 13 21:59:54 zoneminder /etc/mysql/debian-start: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored,Nov 13 21:59:54 zoneminder /etc/mysql/debian-start: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck,Nov 13 21:59:54 zoneminder /etc/mysql/debian-start: This installation of MySQL is already upgraded to 10.1.47-MariaDB, use --force if you still need to run mysql_upgrade,Nov 13 21:59:54 zoneminder /etc/mysql/debian-start: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables,DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (13) at /usr/share/perl5/ZoneMinder/Database.pm line 110.,DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (13) at /usr/share/perl5/ZoneMinder/Database.pm line 110.,Nov 13 21:59:57 zoneminder zmdc: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (13) error val:],DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (13) at /usr/share/perl5/ZoneMinder/Database.pm line 110.,Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96.,Nov 13 21:59:57 zoneminder zmdc: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (13) error val:],Nov 13 21:59:57 zoneminder zmpkg: ERR [Unable to run "sudo -u www-data /usr/bin/zmdc.pl check", output is "", status is 255],
The container uses the bridged network without any modification. I sticked to the standard configuration recommended by the author.Code
Any suggestions how to resolve the DNS errors?
My bitwarden works like a charm, I enabled admin page and cancled registration, but exposing it gives me some worries due to possible brute force attempts. Having fail2ban would be a nice security pillow. Might be a good thing to set up on a rainy Sunday
Do you have fail2ban of your letsenctypt container (I assume its the one from LS.IO?) configured?
You should not, never, ever run as root.
Try running your nextcloud container with user-rights with PUID and PGID-settings.
Ah, awesome! Thanks. Makes sense.
Morlan: How does your reverse proxy configuration with letsencrypt look like? Did you stick to the sample provided with the letsencrypt-container?Code
But how do you login with your clients? Setting server address is obvious, but login email and master password is still required.
Does the BitwardenRS-Server work with the payed features, like multiple user? As far as I cound figure out, even with self -hosting, a Bitwarden-Account is still needed and with more than one user, a little allowance to be due.
A little Typo within your command
docker exec nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --on
docker exec nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off
works like a charm.
Next do do: Dump of database for backup purposes.
Thank you Morlan
docker exec nextclouddb /usr/bin/mysqldump -u nextcloud --password=xxx nextcloud > /srv/dev-disk-by-label-xxx/backup/nextcloud_backup.sql
Seems to work, but backup database seems a litte too small somehow. (Previous natively installed MariaDB backups of NC were >120 MB, this is only 40 MB and there was not much activity on this cloud lately)
How do I push the nextcloud instance into maintenance-mode from the host?
I tried something like this:
but did not work. My assumtions:
- user abc runs the webserver within the nextcloud container
- the path to occ must be the leative one within the container
Maybe it's power related, which plattform do you use? My setup is a Xeon 4C/8T with 32 GB of RAM.
Do you have redis in use and preview-generation active in config?Code
Is a bug on tracker related to the new photos app. Quite nasty, since in shares photos won't open at all.
It was supposed to be fixed with 19, but its still there. I wait day by day for a new release.
The bitwardenrs is my alternative. I got the official setup running in a VM right now and have a look on reverse proxy configuration, environments, volumes etc.
My goal would be to set it up with official and create a little HowTo.
Keeping all my passowords in mind bothers me quite a while, so in the process of merging OMV4->OMV5 and all native services into docker I discovered the quite charming tool bitwarden.
After a short research if figured out that many users use the bitwardenrs/server container. On the other hand there are the official containers, which separate each service part.
I use letsencrypt with reverse proxy and nextcloud (subdomain-configuration) and I might need to integrate bitwarden in the existing setup. As far as I know, the installer script of bitwarden installs a separate letsencrypt-container which I already have. So I guess I need to configurate my letsencrypt to match both services, bitwaren and nextcloud with nextcloud.domain.com and bitwarden.domain.com and therefore I can't use the installer script.
I lack the documentation (environment, ports, volumes, etc) of each of the required bitwarden containers and their connection.
Can someone show me a direction or where to start?
Is the usage of official containers the best way for me or should I stick to the RS?