Do you have omv-extras installed?
Posts by Agricola
-
-
Using Docker containers you specify folder paths in the compose file. Look at the docker-compose listed here. In the Guides section of the forum there are plenty of [How-To] guides using docker-compose.
-
Or someone other than me can port the openvpn plugin.
-
An interesting discussion concerning security but sadly no solution yet for MarcS.
Since the Linuxserver container for OpenVPN is deprecated, what would be the preferred selection?
-
Did you create the second user in the gui?
-
by-label naming of drives was disabled about half way through omv 5, so that any disks set up after that were by-uuid. I don’t know, but the symlinks plugin might help you to simplify your naming issue.
-
Soma … the picture of patience. I don’t know how you do it
-
If everything is running smoothly I never look at them.
-
But you had to first set it up with your IP, right?
No sir. One of the first things I set up on any fresh install is go to Network --> General and set my hostname and domain.
-
<hostname>.local works for me.
Go to Network —> General to set your hostname.
-
Does your file system show up in the gui?
-
Two popular ways to deploy docker containers is by using Portainer Stacks, and by using the command line with docker-compose.
- Here is a [How-To] for Portainer/Stacks
- This [How-To] is a good example of using docker-compose in the command line.
I don't know if you have gotten this far, but below is a docker-compose file that has worked for me on an amd64 machine. Just note that both container names in each compose file need to be unique for each site.
- site 1: wordpress01, wordpressdb01
- site 2: wordpress02, wordpressdb02
- site 3: wordpress03, wordpressdb03
- etc.
Code
Display Moreversion: '3.1' services: wordpress: image: wordpress container_name: wordpress01 # To install multiple wp sites each needs unique name. ports: - 8080:80 # If 8080 is all ready in use it can be changed to an unused port. environment: WORDPRESS_DB_HOST: db WORDPRESS_DB_USER: your-user WORDPRESS_DB_PASSWORD: your-password WORDPRESS_DB_NAME: db01 #I think this name and MYSQL_DATABASE name need to be the same. volumes: - /sym/disk1/appdata/wordpress:/var/www/html # /sym/disk1/... is a symlink. restart: unless-stopped db: image: mysql:5.7 container_name: wordpressdb01 # Unique container name for each wp site here too. environment: MYSQL_DATABASE: db01 # Same as above. MYSQL_USER: your-user MYSQL_PASSWORD: your-password MYSQL_RANDOM_ROOT_PASSWORD: '1' volumes: - /sym/disk1/appdata/wordpresdb:/var/lib/mysql # Same as above. restart: unless-stopped volumes: wordpress: db: networks: default: external: true name: pwh # My custom bridge network used to allow Swag implementation of reverse proxy.
-
Five separate containers, just give them unique names.
-
Did you make a change to your config or docker-compose? I thought you were able to access your login page earlier.
-
Are you not able to reach your Nextcloud login page at nextcloud.your-subdomain.duckdns.org ?
-
If you do you will have to reconfigure your compose file and delete your config folder and rerun your swag cert. make sure you have a strong password on your nextcloud login.
-
-
Your cert looks good. Your problem probably lies somewhere in your proxy configuration. look at this [How-To] under the Configuration of Proxy section to find your .conf and config.php files. Post those in a code box - but hide your passwords, etc.
-
User Management/Users/Edit
-
As your screenshot shows 998 is the uid to your admin user which should only be used in connection with your web-gui login. You need to use a regular, unprivileged user, created by you in the Users section of the gui, the first being 1000. This is the GUID you should be using. You probably got 998 from a DBTech video.