At some point during the update did you change the port used by the OMV GUI to the default 80? That would conflict with a container that also uses that port.
At some point during the update did you change the port used by the OMV GUI to the default 80?
OMV GUI has always used port 80 and still does. Here is the container stack:
services:
### Wallabag ###
wallabag:
image: wallabag/wallabag:latest
environment:
- MYSQL_ROOT_PASSWORD=wallaroot
- SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
- SYMFONY__ENV__DATABASE_HOST=db
- SYMFONY__ENV__DATABASE_PORT=3306
- SYMFONY__ENV__DATABASE_NAME=wallabag
- SYMFONY__ENV__DATABASE_USER=wallabag
- SYMFONY__ENV__DATABASE_PASSWORD=wallapass
- SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
- SYMFONY__ENV__DATABASE_TABLE_PREFIX="wallabag_"
- SYMFONY__ENV__MAILER_HOST=127.0.0.1
- SYMFONY__ENV__MAILER_USER=~
- SYMFONY__ENV__MAILER_PASSWORD=~
- SYMFONY__ENV__FROM_EMAIL=wallabag@thebriars.net.au
- SYMFONY__ENV__DOMAIN_NAME=https://wallabag.somedomain.com.au
- SYMFONY__ENV__SERVER_NAME="My wallabag instance"
- PUID=1000
- PGID=100
- TZ=Australia/Sydney
ports:
- '6080:80'
volumes:
- /share/appdata/wallabag/images:/var/www/wallabag/web/assets/images
healthcheck:
test: ["CMD", "wget" ,"--no-verbose", "--tries=1", "--spider", "http://localhost"]
interval: 1m
timeout: 3s
hostname: wallabag.localdomain
labels:
- "diun.enable=true"
networks:
- wallabag
restart: unless-stopped
depends_on:
- db
- redis
### Mariadb ###
db:
image: mariadb:latest
volumes:
- /share/appdata/wallabag/data:/var/lib/mysql
environment:
- MYSQL_ROOT_PASSWORD=wallaroot
- PUID=1000
- PGID=100
- TZ=Australia/Sydney
healthcheck:
test: ["CMD", "mariadb-admin" ,"ping", "-h", "localhost", "--password=<wallaroot>"]
interval: 20s
timeout: 3s
networks:
- wallabag
restart: unless-stopped
### Redis ###
redis:
image: redis:alpine
environment:
- PUID=1000
- PGID=100
- TZ=Australia/Sydney
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 20s
timeout: 3s
networks:
- wallabag
restart: unless-stopped
networks:
wallabag:The container wallabag-wallabag is giving the unhealthy status.
OMV GUI has always used port 80 and still does. Here is the container stack:
Codeports: - '6080:80'
Okay. That's right.
In that case, I would check the correct functioning of the wallabag network defined so that these three containers communicate with each other.
Note: You posted the compose file without indents, I trust you have it written correctly on your system with the correct indents.
Thanks for your reply.
Note: You posted the compose file without indents, I trust you have it written correctly on your system with the correct indents.
Yes, it's a Portainer Stack so it would not work without the correct syntax. Just copied and pasted from Portainer.
I will check the communicatation between the containers.
EDIT: Fixed the indentation.
This is only failing since upgrading to OMV 7. Why??
It seems that you have changed some network settings when changing from OMV6 to OMV7 and it prevents access via domain name but allows access via IP.
I have no idea what it could be, someone else will have to contribute ideas here.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
